Integration
Connect Mailparser to Xodo Sign
When something happens in Mailparser, your agent does the next thing in Xodo Sign. 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 Xodo Sign 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 Xodo Sign
Triggers and actions 3 triggers · 10 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
Document CompletedTriggers when a new document is completed. Note: This trigger only checks for new documents being completed every 15 minutes.
Action
Add documentCreate and send a new document for signature. POST https://api.eversign.com/document — builds a document from raw files/fields/signers, optionally sends immediately.
Action
Add templateCreate a new reusable document template. POST https://api.eversign.com/document with is_template set — defines fields/signer roles for later use via "Use Template".
Action
Cancel documentCancel an in-progress document's signature process (stops further signing without deleting it). DELETE https://api.eversign.com/document with document_hash and cancel=1.
Action
Delete documentPermanently delete a document or template. DELETE https://api.eversign.com/document with document_hash param.
Action
List businessesList the businesses (sub-accounts) available on this account. GET https://api.eversign.com/business.
Action
List documentsList the account's documents. GET https://api.eversign.com/document — supports limit param, returns document summaries (not templates).
Action
List templatesList the account's saved templates. GET https://api.eversign.com/document?type=template.
Action
Reassign signerReassign a document's pending signature to a different signer email. POST https://api.eversign.com/reassign.
Action
Send reminderSend a signature reminder to a pending signer on a document. POST https://api.eversign.com/send_reminder with document_hash and signer_id.
Action
Use TemplateSends a document created from a template in your eversign account.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.