Checkout.com currently provides 2 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Payment Events
Trigger order fulfillment when payment is approved.
Dispute Events
Notify operations upon dispute opening or resolution.
Create Customer
Store a customer's details in a customer object to reuse in future payments. You can link payment instruments and set a default instrument.
Update Customer
Update existing customer or their metadata.
Create Payment Link
Create a Payment Link to accept and process payment details.
Create Payment
Process and manage payments from various sources including card payments and payouts.
Refund a Payment
Issue a refund (full or partial) for a captured payment. Supports split refunds, line items, and bank account destinations.
Get Payment Details
Check transaction amount and status before refunding.
Get Payment Actions
Build full transaction lifecycles for audit logs.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Checkout.com event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Payment Events
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Checkout.com action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Customer
Combine Checkout.com with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
Payment Events
Finishes with
Create Customer, then preserve the outcome in Coherence
The exact authentication fields depend on Checkout.com. The workflow structure stays straightforward:
Authorize the Checkout.com account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Checkout.com or provide a complementary trigger or action.
Checkout.com currently provides 2 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Checkout.com currently lists 2 triggers and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Checkout.com triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
