Integration
Connect Pinch Payments and Usedesk
When New Event fires in Pinch Payments, your agent runs Add Comment to Ticket in Usedesk, or New Client in Usedesk to Create or Update Scheduled Payment in Pinch Payments. 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 Pinch Payments and Usedesk 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 Pinch Payments and Usedesk can do together
From Pinch Payments to Usedesk
When New Event in Pinch Payments
then Add Comment to Ticket in Usedesk
When New Payer in Pinch Payments
then Create Ticket in Usedesk
From Usedesk to Pinch Payments
When New Client in Usedesk
then Create or Update Scheduled Payment in Pinch Payments
When New Ticket in Usedesk
then Create Payment Link in Pinch Payments
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 Pinch Payments and Usedesk
Triggers and actions 13 triggers · 24 actions
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.
Trigger
New ClientTriggers when a new client is added in Usedesk.
Trigger
New TicketTriggers when a new ticket is created in Usedesk.
Action
Add Comment to TicketAdds a public reply or private note to a Usedesk ticket.
Action
Create ClientCreates a client in Usedesk.
Action
Create TicketCreates a Usedesk ticket with a first message, optionally creating or linking the client.
Action
Find ClientsSearches Usedesk clients by name, email or phone and returns up to 100 matches.
Action
Get ClientReturns one Usedesk client with emails, phones and ticket IDs.
Action
Get TicketReturns one Usedesk ticket by ID, with its comments and tags.
Action
List Agent GroupsReturns Usedesk agent groups and the agents in each.
Action
List AgentsReturns Usedesk agents with their groups, filtered by role, group or search text.
Action
List TagsReturns Usedesk ticket tags with how many tickets carry each.
Action
List TicketsReturns up to 100 Usedesk tickets matching status, channel, group, type, priority, tag, search or date filters.
Action
Update ClientUpdates a Usedesk client's name, contacts, position, note or address.
Action
Update TicketUpdates a Usedesk ticket's subject, status, priority, type, tags, client or assignee.
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 Pinch Payments
Pinch Payments to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pinch Payments to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pinch Payments to StripeStripe is a payment processing platform for online businesses.
Pinch Payments to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pinch Payments to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pinch Payments to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Usedesk
HubSpot to UsedeskHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to UsedeskSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to UsedeskSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to UsedeskGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to UsedeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to UsedeskGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pinch Payments and Usedesk, answered
What can start an automation from Pinch Payments?
Any of Pinch Payments's 11 triggers in the catalog, including New Event, New Payer, New Processed Payment and Payer Created Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Usedesk when something happens in Pinch Payments?
Any of Usedesk's 12 actions, including Create Client, Create Ticket, Update Client and Update Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Usedesk to Pinch Payments?
Yes. When something happens in Usedesk, your agent can act in Pinch Payments too. This page covers both directions: Usedesk's triggers and Pinch Payments's actions are listed here as well.
Do I have to build a connector for Pinch Payments or Usedesk?
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 Pinch Payments and Usedesk 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.