Appearance
Mollie
European payment processing for online payments, subscriptions, and refunds.
| Detail | Value |
|---|---|
| Category | E-commerce |
| Base URL | https://api.mollie.com/v2 |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | mollie |
Using Mollie in a workflow
- Go to Connections and click New Connection.
- Pick Mollie from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /payments | Create a payment |
GET /payments/{id} | Get a payment |
GET /payments | List payments |
POST /payments/{id}/refunds | Create a refund |
GET /methods | List available payment methods |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /payments
Create a payment
| Detail | Value |
|---|---|
| Operation ID | ecommerce.createPayment |
| Method | POST |
| Path | /payments |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
amount | object |
description | string |
redirectUrl | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mollie connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.createPayment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mollie API reference.
GET /payments/{id}
Get a payment
| Detail | Value |
|---|---|
| Operation ID | ecommerce.getPayment |
| Method | GET |
| Path | /payments/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mollie connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.getPayment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mollie API reference.
GET /payments
List payments
| Detail | Value |
|---|---|
| Operation ID | ecommerce.listPayments |
| Method | GET |
| Path | /payments |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mollie connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.listPayments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mollie API reference.
POST /payments/{id}/refunds
Create a refund
| Detail | Value |
|---|---|
| Operation ID | ecommerce.createRefund |
| Method | POST |
| Path | /payments/{id}/refunds |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Request Body
| Field | Type |
|---|---|
amount | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mollie connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.createRefund. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mollie API reference.
GET /methods
List available payment methods
| Detail | Value |
|---|---|
| Operation ID | ecommerce.listPaymentMethods |
| Method | GET |
| Path | /methods |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
amount[value] | query | string | No |
amount[currency] | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Mollie connection from the Connection dropdown.
- In the Operation dropdown, select
ecommerce.listPaymentMethods. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Mollie API reference.