Integration
Connect CallMaker and Pinch Payments
When Booking Created fires in CallMaker, your agent runs Create or Update Scheduled Payment in Pinch Payments, or New Event in Pinch Payments to Create Customer Card in CallMaker. 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 CallMaker and Pinch Payments 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 CallMaker and Pinch Payments can do together
From CallMaker to Pinch Payments
When Booking Created in CallMaker
then Create or Update Scheduled Payment in Pinch Payments
When Number Change Created in CallMaker
then Create Payment Link in Pinch Payments
From Pinch Payments to CallMaker
When New Event in Pinch Payments
then Create Customer Card in CallMaker
When New Payer in Pinch Payments
then Confirm Order by Order Id in CallMaker
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 CallMaker and Pinch Payments
Triggers and actions 26 triggers · 22 actions
Trigger
Booking CancelledFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled bookings.
Trigger
Booking ConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed bookings.
Trigger
Booking CreatedTriggers when a new booking is created.
Trigger
Booking RestoredFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored bookings.
Trigger
Booking UnConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed bookings.
Trigger
Meeting AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (true) to act only on accomplished meetings.
Trigger
Meeting Not AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (false) to act only on meetings that did not take place.
Trigger
Meeting Not SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (false) to act only on unsuccessful meetings.
Trigger
Meeting SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (true) to act only on successful meetings.
Trigger
Number Change CreatedTriggers when a new number change (a processed customer card) is recorded; returns its ID.
Trigger
Order CancelledFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled orders.
Trigger
Order ConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed orders.
Trigger
Order CreatedTriggers when a new order is created.
Trigger
Order RestoredFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored orders.
Trigger
Order UnConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed orders.
Action
Confirm Order by Order IdConfirms an order and returns the updated order.
Action
Create Customer CardCreates a customer card in a Callmaker project and list, with the field values you supply.
Action
Edit Customer CardUpdates field values on an existing Callmaker customer card.
Action
Edit Order Status by Order IdChanges the status of an order.
Action
Find Booking by Booking IdReturns one Callmaker booking (meeting) by its booking ID, including its customer card, user, times and confirmation state.
Action
Find Descendants Workflows by Workflow IdReturns the IDs of all workflows beneath a workflow.
Action
Find Number by Number IdReturns a number (customer record) by its ID.
Action
Find Order by Order IdReturns an order by its ID.
Action
Find Resource by Resource IdReturns a resource by its ID.
Action
Find User by User IdReturns a user by their ID.
Trigger
Bank Results EventTriggers when Pinch reports a new bank results event (direct debit outcomes such as dishonours returned by the bank).
Trigger
New EventTriggers when a new event, such as a payment, dishonour or payer change, is recorded on your Pinch account.
Trigger
New PayerTriggers when a new payer is added to your Pinch account.
Trigger
New Processed PaymentTriggers when a payment is processed (approved, dishonoured or otherwise settled).
Trigger
Payer Created EventTriggers when a new payer is created in Pinch, returning the payer-created event.
Trigger
Payer Updated EventTriggers when a payer's details are updated in Pinch.
Trigger
Realtime Payment EventTriggers when a realtime payment event occurs in Pinch, such as a card or bank payment being processed immediately.
Trigger
Scheduled Process EventTriggers when Pinch records a new scheduled-process event, which is raised when scheduled payments are processed.
Trigger
Subscription Cancelled EventTriggers when a subscription is cancelled in Pinch.
Trigger
Subscription Complete EventTriggers when a subscription completes its final scheduled payment in Pinch.
Trigger
Subscription Created EventTriggers when a new subscription is created in Pinch.
Action
Add a Source to a PayerAdds a bank account or credit card payment source to an existing payer.
Action
Add a SubscriptionSubscribes a payer to a plan, which schedules the plan's payments.
Action
Create or Update PayerCreates a payer, or updates an existing payer when a payer ID is given.
Action
Create or Update Scheduled PaymentSchedules a payment from a payer for a given date, or updates a scheduled payment when a payment ID is given.
Action
Create Payment LinkCreates a hosted payment page link that a payer can use to pay an amount.
Action
Create Realtime PaymentCharges a payer immediately and returns the resulting payment, including its status and fees.
Action
Create RefundRefunds all or part of a processed payment.
Action
Find an EventReturns an account event, such as a payment or payer change, by event ID.
Action
Find a SubscriptionReturns a subscription, its plan and status, by subscription ID.
Action
Find PayerReturns a payer, with their contact details and saved payment sources, by payer ID.
Action
Get PaymentReturns a payment, with its status, fees and payer, by payment ID.
Action
Get RefundReturns a refund and its status by refund ID.
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 CallMaker
CallMaker to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CallMaker to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CallMaker to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CallMaker to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CallMaker to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CallMaker to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pinch Payments
HubSpot to Pinch PaymentsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Pinch PaymentsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Pinch PaymentsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Pinch PaymentsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Pinch PaymentsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Pinch PaymentsMailchimp marketing automation and email platform.
Questions
CallMaker and Pinch Payments, answered
What can start an automation from CallMaker?
Any of CallMaker's 15 triggers in the catalog, including Booking Created, Number Change Created, Order Created and Booking Confirmed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pinch Payments when something happens in CallMaker?
Any of Pinch Payments's 12 actions, including Create or Update Payer, Create or Update Scheduled Payment, Create Payment Link and Create Realtime Payment. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pinch Payments to CallMaker?
Yes. When something happens in Pinch Payments, your agent can act in CallMaker too. This page covers both directions: Pinch Payments's triggers and CallMaker's actions are listed here as well.
Do I have to build a connector for CallMaker or Pinch Payments?
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 CallMaker and Pinch Payments 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.