Integration
Connect Mailparser to Caspio
When something happens in Mailparser, your agent does the next thing in Caspio. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and Caspio 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 Mailparser and Caspio
Triggers and actions 6 triggers · 4 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
Trigger
New Email Parsed (One Request Per Row)Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
Trigger
Deleted RecordFires when a record is deleted from the selected Caspio table. Instant self-registering webhook (table.recordDelete) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.
Trigger
New or Updated RecordFires when a record is inserted or updated in the selected Caspio table. Instant self-registering webhook registering both table.recordInsert and table.recordUpdate — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.
Trigger
New RecordFires when a new record is inserted into the selected Caspio table. Instant self-registering webhook (table.recordInsert) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table. Payload: trigger.body = {data:[record...], objectName, eventType, eventDate, eventId, ...}.
Trigger
Updated RecordFires when a record's field value changes in the selected Caspio table. Instant self-registering webhook (table.recordUpdate) — picking this trigger and a Table auto-registers the Caspio webhook on activation, scoped to that table.
Action
Download File from FieldDownload the file stored in an Attachment-type field of a specific record. Returns the raw file content.
Action
Find RecordsQuery records from a selected Caspio table with an optional WHERE filter, ORDER BY, and limit. Returns the matching records.
Action
Find View RecordsQuery records from a Caspio View (a saved joined/filtered/aggregated dataset spanning tables). Optional WHERE / ORDER BY / limit.
Action
Upload File to FieldUpload a file (from a URL) into an Attachment-type field of a specific record. Table from a dropdown, the attachment field and record ID (the record's primary-key value) are supplied per call. Requires an Attachment-type column (not the legacy File type).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.