Automate Mollie payments, orders, refunds, customers, and invoices. Triggers on payment events and statuses.
Mollie currently provides 7 triggers that can start a workflow and 8 actions a workflow can run. Use those building blocks to keep financial events visible beside the customer, vendor, or project they affect.
New Customer
Fires when a new customer is created in Mollie
New Order
Fires when a new order is created in Mollie
New Settlement
Fires upon a new settlement event (e.g. payout)
New Invoice
Fires when a new invoice is generated
New Payment
Fires when a new payment is created/received
New Refund
Fires when a payment refund is created
New Payment Chargeback
Fires upon a payment chargeback event
Create Order
⚠️ We no longer recommend using the Orders API. Please refer to the Payments API instead. Create a new order in Mollie
Create Payment Link
Generate a new payment link targeting a customer, product, or specific amount
Create Payment
Creates a new payment in Mollie
Create Customer
Creates a new customer in Mollie
Create Payment Refund
Creates refund for payment
Search Order
⚠️ We no longer recommend using the Orders API. Please refer to the Payments API instead. Searches for orders in Mollie
Search Payment
Retrieve all payments created with the current website profile
Search Customer
Retrieve a list of all customers
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 Mollie event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Customer
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Mollie 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 Order
Combine Mollie with another integration and Coherence records to keep financial events visible beside the customer, vendor, or project they affect.
Starts with
New Customer
Finishes with
Create Order, then preserve the outcome in Coherence
The exact authentication fields depend on Mollie. The workflow structure stays straightforward:
Authorize the Mollie 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 Mollie or provide a complementary trigger or action.
Mollie currently provides 7 triggers that can start a workflow and 8 actions a workflow can run. Use those building blocks to keep financial events visible beside the customer, vendor, or project they affect.
Mollie currently lists 7 triggers and 8 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 Mollie 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.
