Mollie
Create and manage payments with the Mollie payment gateway. In Appbricx, your workflows and server functions call it by name once it is connected.
What you can do
8 actions, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.
- Create PaymentCreates a new payment in Mollie
create_payment - Create CustomerCreates a new customer in Mollie
create_customer - Create Order⚠️ We no longer recommend using the Orders API. Please refer to the Payments API instead. Create a new order in Mollie
create_order - Create Payment LinkGenerate a new payment link targeting a customer, product, or specific amount
create_payment_link - Create Payment RefundCreates refund for payment
create_payment_refund - Search CustomerRetrieve a list of all customers
search_customer - Search Order⚠️ We no longer recommend using the Orders API. Please refer to the Payments API instead. Searches for orders in Mollie
search_order - Search PaymentRetrieve all payments created with the current website profile
search_payment
Set it up
About two minutes, once per project or once for the whole workspace.
- Open Integrations in the builder
Backend panel, Integrations tab, then Mollie. To connect it for every project, use Workspace settings, Integrations.
- Add your credentials
An API key (or token) from your Mollie account, pasted once. It is stored encrypted and only read on the server when an action runs.
- API key From Mollie's settings
- Call an action
From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.
Workflow // .workflow.js (native ctx) export async function run(ctx) { const res = await ctx.integrations.invoke("mollie", "create_payment", { "description": "<description>", "currency": "<currency>", "amount": "<amount>", "redirectUrl": "<redirect url>" }); if (!res.success) throw new Error(res.error); ctx.log.info("Mollie answered", { output: res.output }); }
More in Finance and payments
Mollie and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.