Integration
Connect Mollie and Pipefy
When New Customer fires in Mollie, your agent runs Create Record in Pipefy, or Moved Card in Pipefy to Add customer in Mollie. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Mollie and Pipefy to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Mollie and Pipefy can do together
From Mollie to Pipefy
When New Customer in Mollie
then Create Record in Pipefy
When New Invoice in Mollie
then Update Database Record in Pipefy
From Pipefy to Mollie
When Moved Card in Pipefy
then Add customer in Mollie
When New Card in Pipefy
then Update customer in Mollie
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Mollie and Pipefy
Triggers and actions 12 triggers · 27 actions
Trigger
New CustomerTriggers when a new customer is created in your Mollie account.
Trigger
New InvoiceTriggers when Mollie issues a new invoice to your organization for its fees.
Trigger
New PaymentTriggers when a new payment is created in your Mollie account.
Trigger
New Payment ChargebackTriggers when a new chargeback is received on any of your Mollie payments.
Trigger
New RefundTriggers when a new refund is created on any payment in your Mollie account.
Trigger
New SettlementTriggers when a new settlement appears in your Mollie account.
Action
Add customerCreates a customer in Mollie, to which payments, mandates and subscriptions can later be linked.
Action
Add refundCreates a refund for a Mollie payment, returning the full or partial amount to the customer.
Action
Cancel paymentCancels an open Mollie payment and returns the canceled payment. Only payments that are still cancelable can be canceled.
Action
Create PaymentCreates a Mollie payment and returns it, including the checkout link to send your customer to.
Action
Create Payment LinkCreates a shareable Mollie payment link that customers can open to complete a payment.
Action
Delete customerDeletes a Mollie customer. All mandates and subscriptions for that customer are canceled as well.
Action
Delete subscriptionCancels a customer's subscription in Mollie and returns the canceled subscription. The customer's mandates are not affected.
Action
Find PaymentFinds payments whose description contains the text you enter, searching your most recent 250 Mollie payments.
Action
Get customerReturns a single Mollie customer by its ID, including name, email, locale and metadata.
Action
Get paymentReturns a single Mollie payment by its ID, including amount, status, method and links.
Action
List customersReturns the customers in your Mollie account, newest first by default.
Action
List paymentsReturns the payments created with your Mollie website profile, with their status, amount and details.
Action
List refundsReturns refunds across all payments in your Mollie account, up to 250 at a time.
Action
List subscriptionsReturns the subscriptions set up across all of your customers, up to 250 per run.
Action
Search CustomerSearches your Mollie customers by email address and/or name and returns the matching customers.
Action
Update customerUpdates an existing Mollie customer's name, email, language or metadata.
Trigger
Done CardTriggers when a card is done.
Trigger
Moved CardTriggers when a card is moved.
Trigger
New CardTriggers when a new card is created.
Trigger
New Database RecordTriggers when a new record is created.
Trigger
Updated Card FieldTriggers when a card field is updated.
Trigger
Updated Record FieldTriggers when a record field is updated.
Action
Create CardCreates a card in a Pipefy pipe, filling in its start form fields.
Action
Create RecordCreates a new table record.
Action
Delete CardPermanently deletes a card from its pipe.
Action
Delete Database RecordDelete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
Action
Find CardReturns the cards in a pipe whose chosen field matches the specified value.
Action
Find Database RecordsFind a database records by title.
Action
Get CardRetrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
Action
Get Database RecordFetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
Action
Move CardMoves a Pipefy card to another phase of its pipe.
Action
Update Card FieldSets a new value on one field of an existing Pipefy card.
Action
Update Database RecordUpdate a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Mollie
Mollie to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mollie to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mollie to StripeStripe is a payment processing platform for online businesses.
Mollie to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mollie to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Mollie to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Pipefy
GrowSurf to PipefyGrowSurf is referral software for B2C and B2B tech companies.
HubSpot to PipefyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PipefyGoogle Sheets
Gmail to PipefyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PipefyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Mollie and Pipefy, answered
What can start an automation from Mollie?
Any of Mollie's 6 triggers in the catalog, including New Customer, New Invoice, New Payment and New Payment Chargeback. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefy when something happens in Mollie?
Any of Pipefy's 11 actions, including Create Card, Create Record, Update Card Field and Update Database Record. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefy to Mollie?
Yes. When something happens in Pipefy, your agent can act in Mollie too. This page covers both directions: Pipefy's triggers and Mollie's actions are listed here as well.
Do I have to build a connector for Mollie or Pipefy?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Mollie and Pipefy without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.