Integration
Connect DocumentPro to Customer.io
When New Document fires in DocumentPro, 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 DocumentPro 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 DocumentPro can start in Customer.io
When New Document in DocumentPro
then Send transactional email 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 DocumentPro and Customer.io
Triggers and actions 1 trigger · 24 actions
- New Document
Triggers when a document is uploaded.
- Add classifier
create a new Classifier.
- Add workflow
create a new Workflow (extraction template).
- Classify document
classify a document inline without a saved Classifier.
- Delete classifier
delete a Classifier.
- Delete workflow
delete a Workflow.
- Get classifier
fetch a single Classifier by id.
- Get document
fetch a single document by id.
- Get workflow
fetch a single Workflow by id.
- List classifiers
list saved Classifiers.
- Run classifier against document
run a saved Classifier against a document.
- Run workflow against document
Start an extraction Workflow against a document. The run is asynchronous: it returns a request_id immediately and the extracted data arrives once the job completes.
- Update classifier
update an existing Classifier.
- Update workflow
update an existing Workflow.
- Upload Document
Upload a document (PDF, JPEG, PNG or TIFF) up to 6MB so it can be classified or parsed by a workflow.
- Create Anonymous Event
Records 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.
- Create Event
Records an event for a person in Customer.io, which can trigger campaigns or update segments.
- Delete person
Deletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.
- Get person
Look up a customer's attributes by customer_id.
- List segments
List all manual and data-driven segments in the workspace.
- Merge people
Merges 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.
- Remove people from segment
Removes people from a manual segment in Customer.io. Data-driven segments can't be changed this way.
- Send API-triggered broadcast
Trigger an API-triggered broadcast campaign to send immediately.
- Send transactional email
Send a one-off transactional email via a transactional message template.
- Suppress person
Deletes 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 DocumentPro
DocumentPro to AccuweatherWeather data API delivering real-time forecasts, conditions, and severe weather alerts globally.
DocumentPro to CoachfulCoachful is a program delivery tool for coaches and creators.
DocumentPro to Mistral AIMistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...
DocumentPro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DocumentPro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DocumentPro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Customer.io
Wistia to Customer.ioWistia makes it easy to host, track, and measure video engagement online.
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
DocumentPro and Customer.io, answered
What can start an automation from DocumentPro?
Any of DocumentPro's 1 trigger in the catalog, including New Document. 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 DocumentPro?
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 DocumentPro?
Customer.io has no triggers in the catalog today, so automations start in DocumentPro. 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 DocumentPro 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 DocumentPro 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.