Integration
Connect ChargeOver to Code::Stats
When Contact Was Updated fires in ChargeOver, your agent runs Get user in Code::Stats. 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 Code::Stats to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 can start in Code::Stats
When Contact Was Updated in ChargeOver
then Get user in Code::Stats
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 Code::Stats
Triggers and actions 1 trigger · 21 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.
Action
Get userRetrieve a public user's profile (total XP, new XP in last 12h, per-machine, per-language and per-date XP).
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 Code::Stats
HubSpot to Code::StatsHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Code::StatsSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Code::StatsSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Code::StatsGoogle Sheets
Gmail to Code::StatsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Code::StatsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ChargeOver and Code::Stats, 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 Code::Stats when something happens in ChargeOver?
Any of Code::Stats's 1 action, including Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Code::Stats to ChargeOver?
Code::Stats has no triggers in the catalog today, so automations start in ChargeOver. If you need the other direction, ask: your agent reads Code::Stats's API documentation and adds it.
Do I have to build a connector for ChargeOver or Code::Stats?
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.
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.