Integration
Connect Pinch Payments to Neon Postgres
When New Event fires in Pinch Payments, your agent runs Add project in Neon Postgres. 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 Neon Postgres 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 can start in Neon Postgres
When New Event in Pinch Payments
then Add project in Neon Postgres
When New Payer in Pinch Payments
then Add branch in Neon Postgres
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 Neon Postgres
Triggers and actions 11 triggers · 41 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.
Action
Add branchCreate a new branch in a Neon project.
Action
Add compute endpointCreates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.
Action
Add databaseCreates a new Postgres database in a Neon project branch, owned by an existing role.
Action
Add projectCreates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.
Action
Add roleCreates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.
Action
Delete branchDelete a branch by project_id and branch_id.
Action
Delete compute endpointDeletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.
Action
Delete databaseDeletes the specified database from a branch of a Neon project.
Action
Delete projectDeletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.
Action
Delete roleDeletes the specified Postgres role from a Neon branch.
Action
Get branchRetrieves details of a branch in a Neon project.
Action
Get compute endpointRetrieve details about a compute endpoint.
Action
Get connection URIRetrieve a Postgres connection URI for a database/role/branch/endpoint combination.
Action
Get databaseRetrieves details of a database on a Neon project branch.
Action
Get projectRetrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.
Action
Get roleRetrieves details about a Postgres role (user) on a Neon branch.
Action
Get role passwordRetrieves the password for a Postgres role on a Neon branch.
Action
List branchesRetrieve a list of branches for a Neon project.
Action
List compute endpointsLists the compute endpoints (Neon compute instances) in a project.
Action
List databasesLists the databases on a branch of a Neon project.
Action
List operationsLists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.
Action
List projectsLists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.
Action
List rolesLists the Postgres roles on a Neon project branch.
Action
Start compute endpointStart (resume) a suspended compute endpoint.
Action
Suspend compute endpointSuspends the specified Neon compute endpoint (scales it to zero).
Action
Update branchUpdate a branch's properties (e.g. name, protected) by project_id and branch_id.
Action
Update compute endpointUpdates an existing compute endpoint in a Neon project by ID.
Action
Update databaseUpdates the name or owner of a database on a Neon project branch.
Action
Update projectUpdate settings for a Neon project by project_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 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 Neon Postgres
Vimeo OTT to Neon PostgresVimeo OTT (formerly VHX) is an over-the-top video monetization platform for launching subscription and...
HubSpot to Neon PostgresHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Neon PostgresSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Neon PostgresSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Neon PostgresGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Neon PostgresGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Pinch Payments and Neon Postgres, 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 Neon Postgres when something happens in Pinch Payments?
Any of Neon Postgres's 29 actions, including Update branch, Update compute endpoint, Update database and Update project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Neon Postgres to Pinch Payments?
Neon Postgres has no triggers in the catalog today, so automations start in Pinch Payments. If you need the other direction, ask: your agent reads Neon Postgres's API documentation and adds it.
Do I have to build a connector for Pinch Payments or Neon Postgres?
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 Neon Postgres 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.