Integration
Connect Mollie to Browserbase
When New Customer fires in Mollie, your agent runs Fetch page in Browserbase. 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 Browserbase 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 can start in Browserbase
When New Customer in Mollie
then Fetch page in Browserbase
When New Invoice in Mollie
then Add context in Browserbase
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 Browserbase
Triggers and actions 6 triggers · 28 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.
Action
Add contextCreates a new browser Context that persists cookies and storage across Browserbase sessions.
Action
Add sessionCreates a new Browserbase browser session and returns its id along with the URLs used to connect to it.
Action
Delete contextDeletes a browser context (saved cookies and browser state) from your Browserbase project.
Action
Fetch pageFetches a web page through Browserbase and returns its content (raw, markdown, or schema-extracted JSON), status code and headers.
Action
Get contextReturns a Browserbase context (saved browser state) by its id, including its name, project and timestamps.
Action
Get runReturns the current status and details of an agent run, including its result and the browser session it used.
Action
Get sessionReturns a Browserbase browser session, including its status, region, timestamps and connection URLs.
Action
List downloadsReturns the files downloaded during a Browserbase session, optionally filtered by filename, MIME type, size or creation time.
Action
List sessionsReturns the browser sessions in your Browserbase project, optionally filtered by status or by user metadata.
Action
Run agentStarts a Browserbase browser agent run that completes a natural-language task using web search and browser tools. Returns the new run, which starts in a pending state.
Action
Search webRuns a web search through Browserbase and returns the matching pages with their titles and URLs.
Action
Update sessionUpdates a Browserbase session, such as requesting that it be released before its timeout to stop further charges.
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 Browserbase
HubSpot to BrowserbaseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to BrowserbaseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to BrowserbaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to BrowserbaseGoogle Sheets
Gmail to BrowserbaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BrowserbaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Mollie and Browserbase, 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 Browserbase when something happens in Mollie?
Any of Browserbase's 12 actions, including Update session, Add context, Add session and Fetch page. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Browserbase to Mollie?
Browserbase has no triggers in the catalog today, so automations start in Mollie. If you need the other direction, ask: your agent reads Browserbase's API documentation and adds it.
Do I have to build a connector for Mollie or Browserbase?
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 Browserbase 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.