Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Mollie

Automate Mollie payments, orders, refunds, customers, and invoices. Triggers on payment events and statuses.

CategoryPayment Processing
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Mollie with Flows360

Automate Mollie payments, orders, refunds, customers, and invoices. Triggers on payment events and statuses.

Use the Mollie connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 7 triggers.

Available actions

  • Create Order
  • Create Payment Link
  • Create Payment
  • Create Customer
  • Create Payment Refund
  • Search Order
  • Search Payment
  • Search Customer

Available triggers

  • New Customer
  • New Order
  • New Settlement
  • New Invoice
  • New Payment
  • New Refund
  • Plus 1 additional declared trigger.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Mollie
  • Package: @activepieces/piece-mollie@0.1.6
  • Exact artifact digest: sha256:d659e1630a47e2e4a0ebff750f9038483b9a27edd929c6f747533be8d67267da
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Order (create_order), ⚠️ We no longer recommend using the Orders API. Please refer to the Payments API instead.

Create a new order in Mollie Classification: read.

  • Create Payment Link (create_payment_link), Generate a new payment link targeting a customer, product, or specific amount Classification: read.
  • Create Payment (create_payment), Creates a new payment in Mollie Classification: read.
  • Create Customer (create_customer), Creates a new customer in Mollie Classification: read.
  • Create Payment Refund (create_payment_refund), Creates refund for payment Classification: read.
  • Search Order (search_order), ⚠️ We no longer recommend using the Orders API. Please refer to the Payments API instead.

Searches for orders in Mollie Classification: read.

  • Search Payment (search_payment), Retrieve all payments created with the current website profile Classification: read.
  • Search Customer (search_customer), Retrieve a list of all customers Classification: read.

Trigger contracts

  • New Customer, polling.
  • New Order, polling.
  • New Settlement, polling.
  • New Invoice, webhook.
  • New Payment, polling.
  • New Refund, polling.
  • New Payment Chargeback, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actionsNot published
Triggers7

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Order Yes No u26a0ufe0f We no longer recommend using the Orders API. Please refer to the Payments API instead.nnCreate a new order in Mollie
Create Payment Link Yes No Generate a new payment link targeting a customer, product, or specific amount
Create Payment Yes No Creates a new payment in Mollie
Create Customer Yes No Creates a new customer in Mollie
Create Payment Refund Yes No Creates refund for payment
Search Order Yes No u26a0ufe0f We no longer recommend using the Orders API. Please refer to the Payments API instead.nnSearches for orders in Mollie
Search Payment Yes No Retrieve all payments created with the current website profile
Search Customer Yes No Retrieve a list of all customers
New Customer Yes No polling trigger declared by the pinned package.
New Order Yes No polling trigger declared by the pinned package.
New Settlement Yes No polling trigger declared by the pinned package.
New Invoice Yes No webhook trigger declared by the pinned package.
New Payment Yes No polling trigger declared by the pinned package.
New Refund Yes No polling trigger declared by the pinned package.
New Payment Chargeback Yes No polling trigger declared by the pinned package.

Triggers

New Customer · Poll

Fires when a new customer is created in Mollie

New Order · Poll

Fires when a new order is created in Mollie

New Settlement · Poll

Fires upon a new settlement event (e.g. payout)

New Invoice · Webhook

Fires when a new invoice is generated

New Payment · Poll

Fires when a new payment is created/received

New Refund · Poll

Fires when a payment refund is created

Inputs

  • paymentId · string
New Payment Chargeback · Poll

Fires upon a payment chargeback event

Inputs

  • paymentId · string

Setup

Setup

  1. Add the Mollie connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-mollie@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 7 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Mollie connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-mollie@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com