Integration
Connect Airparser to Customer.io
When something happens in Airparser, your agent does the next thing in Customer.io. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Airparser and Customer.io to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Airparser and Customer.io
Triggers and actions 1 trigger ยท 10 actions
Trigger
Document ParsedTriggers when Airparser finishes parsing a document in the chosen inbox, giving you the extracted data.
- Create an Inbox
Creates a new Airparser inbox that documents can be sent to for parsing.
- Create or Update Extraction Schema
Sets which fields Airparser should pull out of documents sent to an inbox, replacing whatever schema was there before.
- Delete an Inbox
Deletes an Airparser inbox and the documents stored in it.
- Extract Data From a Document
Sends a document to an Airparser inbox, waits for it to be parsed, and returns the extracted data.
- Extract Data From a Document (Async)
Sends a document to an Airparser inbox and returns straight away without waiting for parsing. Use the Document Parsed trigger or Get Document to pick up the result.
- Get a Document
Returns a parsed Airparser document, including the data extracted from it.
- Get an Inbox
Returns one Airparser inbox with its settings, its email address prefix and its current extraction schema.
- List Documents
Lists the documents in an Airparser inbox, with the data extracted from each one.
- List Inboxes
Lists all the Airparser inboxes in the connected account.
Action
List segmentsList all manual and data-driven segments in the workspace. GET /v1/segments (App API).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.