Integration
Connect Áskell and Pinch Payments
When New Customer fires in Áskell, your agent runs Create or Update Scheduled Payment in Pinch Payments, or New Event in Pinch Payments to Create Customer in Áskell. 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 Áskell 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 Áskell and Pinch Payments can do together
From Áskell to Pinch Payments
When New Customer in Áskell
then Create or Update Scheduled Payment in Pinch Payments
When New Subscription in Áskell
then Add a Subscription in Pinch Payments
From Pinch Payments to Áskell
When New Event in Pinch Payments
then Create Customer in Áskell
When New Payer in Pinch Payments
then Update customer in Áskell
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 Áskell and Pinch Payments
Triggers and actions 13 triggers · 30 actions
Trigger
New CustomerTriggers when a new customer is created in Áskell.
Trigger
New SubscriptionTriggers when a new subscription is created in Áskell.
Action
Activate SubscriptionRe-activates a cancelled Áskell subscription, as long as its latest billing period has not passed.
Action
Add paymentCreates a one-off payment for an Áskell customer. The payment starts as pending and settles or fails asynchronously.
Action
Add subscriptionAdds a subscription to an existing customer on a plan, charging the first period with the customer's payment method unless the plan has a trial.
Action
Cancel SubscriptionCancels an active Áskell subscription and returns its new state.
Action
Create CustomerCreates a customer in Áskell under a reference you choose, so you can look the customer up later.
Action
Delete customerDeletes a customer from Áskell by their customer reference.
Action
Get CustomerReturns one Áskell customer, looked up by the customer reference you assigned when creating it.
Action
Get paymentReturns a single Áskell payment in detail, including its amount, state, refunded amount and transactions.
Action
Get planReturns a single Áskell plan variant by its id, including its name, price, billing interval and payment processor.
Action
Get SubscriptionReturns one Áskell subscription by its id, including its status, customer and dates.
Action
List customersReturns all customers in your Áskell account, with their contact details and payment methods.
Action
List paymentsReturns all payments in your Áskell account, with amount, state, refunds and their transactions.
Action
List plansReturns every plan variant in your Áskell account, each with its name, price, currency and billing interval.
Action
List subscriptionsReturns all subscriptions in your Áskell account, with each subscription's plan, customer and status.
Action
List transactionsReturns the transactions on your Áskell account. You can filter them by state, subscription, payment or date range.
Action
Refund paymentRefunds a settled Áskell payment, in full or for a partial amount.
Action
Update customerUpdates an existing Áskell customer's name, email or phone. Fields left blank are not changed.
Action
Update subscriptionUpdates an Áskell subscription's plan, amount, discount or internal description.
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 Áskell
Áskell to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Áskell to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Áskell to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Áskell to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Áskell to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Áskell 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
Áskell and Pinch Payments, answered
What can start an automation from Áskell?
Any of Áskell's 2 triggers in the catalog, including New Customer and New Subscription. 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 Áskell?
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 Áskell?
Yes. When something happens in Pinch Payments, your agent can act in Áskell too. This page covers both directions: Pinch Payments's triggers and Áskell's actions are listed here as well.
Do I have to build a connector for Áskell 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 Áskell 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.