Integration
Connect Stax to Customer.io
When List Payment fires in Stax, your agent runs Send transactional email in Customer.io. 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 Stax and Customer.io 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 Stax can start in Customer.io
When List Payment in Stax
then Send transactional email in Customer.io
When List Payment in Stax
then Create Anonymous Event in Customer.io
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 Stax and Customer.io
Triggers and actions 1 trigger · 27 actions
Trigger
List PaymentTriggers when a new payment transaction is recorded in Stax.
Action
Capture paymentCaptures funds from a pre-authorized Stax transaction, turning the pre-authorization into a completed charge. Returns the updated transaction.
Action
Create CustomerCreates a customer record on the Stax merchant account and returns the new customer.
Action
Create ItemCreates an item in the merchant's Stax catalog and returns the new catalog item.
Action
Create Scheduled InvoiceCreates a scheduled invoice that automatically generates invoices for a customer on a one-time or recurring schedule, with optional autopay. Returns the new schedule.
Action
Delete Catalog ItemDeletes a catalog item from Stax.
Action
Delete payment methodDeletes a customer's saved payment method in Stax and returns the deleted payment method.
Action
Delete Scheduled InvoiceDeletes a recurring invoice schedule so it stops generating invoices.
Action
Find CustomersSearches your Stax customers by name, email, company, phone, address or other details and returns the matching customers.
Action
Find InvoicesReturns the invoices on the Stax merchant account that match the search criteria you supply, such as keywords, customer name, company, email, price, schedule or payment method.
Action
Find ItemsSearches the merchant's catalog for items matching a name, code, price or other criteria and returns the matching items.
Action
Find Payment MethodsReturns all saved payment methods (cards and bank accounts) for a Stax customer.
Action
Find PaymentsReturns the payments and other transactions on the merchant account that match the search criteria, such as keywords, customer, date range, amount, type or status.
Action
Make a PaymentCharges a customer's saved payment method for the amount you specify, or places a pre-authorization to capture later. Returns the resulting transaction.
Action
Refund paymentRefunds all or part of a settled Stax payment transaction back to the customer.
Action
Update customerUpdates an existing customer's contact details, address, notes and options in Stax, and returns the updated customer.
Action
Update invoiceUpdates an existing unpaid invoice's customer, amounts, line items, memos and payment options, and returns the updated invoice. Fully paid invoices cannot be edited.
Action
Void paymentVoids a payment transaction in Stax before it settles, cancelling the charge.
Action
Create Anonymous EventRecords an event that isn't tied to a known person yet, such as a page view or an action by a visitor. Include an anonymous id to link the event to a person later.
Action
Create EventRecords an event for a person in Customer.io, which can trigger campaigns or update segments.
Action
Delete personDeletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.
Action
Get personLook up a customer's attributes by customer_id.
Action
List segmentsList all manual and data-driven segments in the workspace.
Action
Merge peopleMerges a duplicate person into a primary person. The secondary person's attributes and activity move to the primary person, and the secondary person is deleted.
Action
Remove people from segmentRemoves people from a manual segment in Customer.io. Data-driven segments can't be changed this way.
Action
Send API-triggered broadcastTrigger an API-triggered broadcast campaign to send immediately.
Action
Send transactional emailSend a one-off transactional email via a transactional message template.
Action
Suppress personDeletes a person from your Customer.io workspace and suppresses their identifiers so nobody can be added again with the same id, email or phone. Activity attributed to them is redacted.
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 Stax
Stax to StripeStripe is a payment processing platform for online businesses.
Stax to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Stax to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Stax to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Stax to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Stax to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
More into Customer.io
HubSpot to Customer.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Wistia to Customer.ioWistia makes it easy to host, track, and measure video engagement online.
Salesforce to Customer.ioSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Customer.ioSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Customer.ioGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Customer.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Stax and Customer.io, answered
What can start an automation from Stax?
Any of Stax's 1 trigger in the catalog, including List Payment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Customer.io when something happens in Stax?
Any of Customer.io's 10 actions, including Create Anonymous Event, Create Event, Send API-triggered broadcast and Send transactional email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Customer.io to Stax?
Customer.io has no triggers in the catalog today, so automations start in Stax. If you need the other direction, ask: your agent reads Customer.io's API documentation and adds it.
Do I have to build a connector for Stax or Customer.io?
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 Stax and Customer.io 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.