Integration
Connect Mailparser to Stiply
When something happens in Mailparser, your agent does the next thing in Stiply. 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 Stiply 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 Stiply
Triggers and actions 2 triggers · 8 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.
Action
Cancel sign requestCancel an in-progress sign request. POST /v2/sign_requests/{sign_request}/actions/cancel
Action
Delete sign requestDelete a sign request. DELETE /v2/sign_requests/{sign_request}
Action
Extend sign request termExtend the expiration term of a sign request. POST /v2/sign_requests/{sign_request}/actions/extend_term
Action
Get sign requestRetrieve a single sign request by id. GET /v2/sign_requests/{sign_request}
Action
Get sign request progressGet the signing progress of a sign request. GET /v2/sign_requests/{sign_request}/progress
Action
List signersList the signers of a sign request. GET /v2/sign_requests/{sign_request}/signers
Action
Send reminderSend a reminder to signers of a sign request. POST /v2/sign_requests/{sign_request}/actions/send_reminder
Action
Send Sign RequestSends a sign request in Stiply
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.