Integration
Connect CallFire and Pinch Payments
When New call fires in CallFire, your agent runs Create or Update Scheduled Payment in Pinch Payments, or New Event in Pinch Payments to Add contact to list in CallFire. 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 CallFire 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 CallFire and Pinch Payments can do together
From CallFire to Pinch Payments
When New call in CallFire
then Create or Update Scheduled Payment in Pinch Payments
When New contact in CallFire
then Create Payment Link in Pinch Payments
From Pinch Payments to CallFire
When New Event in Pinch Payments
then Add contact to list in CallFire
When New Payer in Pinch Payments
then Add do not contact numbers in CallFire
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 CallFire and Pinch Payments
Triggers and actions 15 triggers · 36 actions
Trigger
New callPolls for completed calls. Fires for each new inbound or outbound call.
Trigger
New contactPolls for newly created contacts in the account.
Trigger
New SMS text receivedPolls for inbound SMS text messages. Fires for each newly received text.
Trigger
New text sentPolls for outbound SMS text messages. Fires for each newly sent text.
Action
Add auto replyCreates an SMS auto reply message for one of your CallFire numbers or keywords, optionally only for texts matching given text.
Action
Add call broadcastCreates a CallFire voice (call) broadcast campaign with its sounds, recipients, schedule and retry settings, optionally starting it immediately.
Action
Add contact to listAdds a contact (by contact ID) to a specified contact list.
Action
Add do not contact numbersAdds phone numbers to your CallFire Do Not Contact list, blocking outbound calls and/or texts (and optionally inbound) to them. Existing entries are updated.
Action
Add new contactCreates a new contact in CallFire and returns its ID.
Action
Add text broadcastCreates a text broadcast campaign in CallFire, optionally with recipients, a schedule, and starting it immediately.
Action
Create contact listCreates a new contact list with the given name and optional contact numbers.
Action
Delete contactDeletes a contact by its CallFire contact ID.
Action
Delete do not contact numberRemoves a phone number (or a comma-separated list of numbers) from your CallFire Do Not Contact list.
Action
Find callsSearches the calls sent or received by your CallFire account, filtered by number, broadcast, label, state, result, direction or time window.
Action
Find textsFinds text messages sent or received in your CallFire account, filtered by number, campaign, label, status, result, direction or time range.
Action
Get callReturns a single call by its id, including its numbers, state, result, contact and call records.
Action
Get contact by IDRetrieves a single contact by its CallFire contact ID.
Action
Get contact by propertyGet contact details by property name and value.
Action
Get text messageRetrieves a single sent or received text message by its ID.
Action
List contact listsReturns all contact lists in the account.
Action
Remove contact from listRemoves a contact (by contact ID) from a specified contact list.
Action
Send SMS text messageSends an SMS text message to one phone number and returns the new text's ID and state.
Action
Send voice callPlaces a text-to-speech voice call to one phone number and returns the new call's ID and state.
Action
Start call broadcastStarts a CallFire voice (call) broadcast so it begins dialing its recipients.
Action
Start text broadcastStarts sending a text broadcast that has already been created in CallFire.
Action
Stop call broadcastStops a running CallFire voice (call) broadcast so no further calls are dialed.
Action
Stop text broadcastStops a running text broadcast so no further messages are sent.
Action
Update contactUpdates an existing contact by its CallFire contact 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 CallFire
CallFire to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CallFire to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CallFire to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CallFire to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CallFire to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CallFire 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
CallFire and Pinch Payments, answered
What can start an automation from CallFire?
Any of CallFire's 4 triggers in the catalog, including New call, New contact, New SMS text received and New text sent. 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 CallFire?
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 CallFire?
Yes. When something happens in Pinch Payments, your agent can act in CallFire too. This page covers both directions: Pinch Payments's triggers and CallFire's actions are listed here as well.
Do I have to build a connector for CallFire 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 CallFire 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.