Integration
Connect ChargeOver and Cursor
When Contact Was Updated fires in ChargeOver, your agent runs Add Followup Instruction to Agent in Cursor, or Agent Pull Request Created in Cursor to Create a Contact in ChargeOver. 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 ChargeOver and Cursor 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)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 ChargeOver and Cursor can do together
From ChargeOver to Cursor
When Contact Was Updated in ChargeOver
then Add Followup Instruction to Agent in Cursor
When Contact Was Updated in ChargeOver
then Launch Agent in Cursor
From Cursor to ChargeOver
When Agent Pull Request Created in Cursor
then Create a Contact in ChargeOver
When New Agent in Cursor
then Create a Customer in ChargeOver
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 ChargeOver and Cursor
Triggers and actions 4 triggers ยท 31 actions
Trigger
Contact Was UpdatedTriggers when a contact is updated in ChargeOver.
Action
Add itemCreate an item (product or discount).
Action
Add noteAdd a note to a customer, invoice, etc.
Action
Add Transactionrecords a payment, refund or credit against a customer (e.g. transaction_type=pay, gateway_method=check, amount) without charging a payment gateway. Creates a transaction record.
Action
Cancel a SubscriptionCancel an existing subscription in ChargeOver.
Action
Create a ContactCreate a new contact in ChargeOver.
Action
Create a CustomerCreate a new customer in ChargeOver.
Action
Create an InvoiceCreate a new Invoice in ChargeOver.
Action
Create a SubscriptionCreate a new subscription in ChargeOver.
Action
Delete Itemdeletes an item (product/discount) by id.
Action
Find ContactFinds an existing contact by a specified field.
Action
Find CustomerFinds an existing customer by a specified field.
Action
Find Item (Product, Discount)Finds an existing item (product, discount) by a specified field.
Action
Find SubscriptionFinds an existing subscription by a specified field.
Action
List NotesLists the notes attached to a ChargeOver record (customer, invoice, subscription, contact), filtered by record type and record ID.
Action
Update a CustomerUpdate a existing customer in ChargeOver.
Action
Update contactUpdate a user/contact.
Action
Update invoiceUpdate an invoice.
Action
Update itemUpdate an item.
Action
Update subscriptionUpdate a subscription (package).
Action
Void Transactionmarks an existing transaction voided in ChargeOver (logs an externally-voided transaction; does not contact the gateway), changing its status.
Trigger
Agent Pull Request CreatedTriggers when the selected Cursor cloud agent opens a new GitHub pull request.
Trigger
Agent Status EqualsTriggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error.
Trigger
New AgentTriggered when a new Cursor cloud agent is created.
Action
Add Followup Instruction to AgentSends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered.
Action
Cancel runCancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation.
Action
Delete AgentPermanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent.
Action
Find Agent StatusLooks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link.
Action
Get runReturns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent.
Action
Launch AgentCreates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run.
Action
List agentsReturns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL.
Action
List artifactsReturns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts.
Action
List modelsReturns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants.
Action
List repositoriesReturns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation.
Action
List runsReturns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply.
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 ChargeOver
ChargeOver to CustomGPT.aiCustomGPT.ai is a no-code platform that lets you build AI chatbots using your own business content, designed...
ChargeOver to IP2LocationIP geolocation and intelligence. Look up location, network, proxy, and security data for any IP address...
ChargeOver to MemberstackSimple Auth & Payments for Webflow Developers.
ChargeOver to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
ChargeOver to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ChargeOver to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Cursor
ActiveCampaign to CursorActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CursorOrganize anything with Airtable, a modern database created for everyone.
Asana to CursorAsana is a collaborative information manager for workspace.
ClickUp to CursorClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CursorBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CursorCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
ChargeOver and Cursor, answered
What can start an automation from ChargeOver?
Any of ChargeOver's 1 trigger in the catalog, including Contact Was Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Cursor when something happens in ChargeOver?
Any of Cursor's 11 actions, including Add Followup Instruction to Agent, Find Agent Status, Get run and Launch Agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Cursor to ChargeOver?
Yes. When something happens in Cursor, your agent can act in ChargeOver too. This page covers both directions: Cursor's triggers and ChargeOver's actions are listed here as well.
Do I have to build a connector for ChargeOver or Cursor?
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 ChargeOver and Cursor 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.