Integration
Connect Mailparser to Basin
When something happens in Mailparser, your agent does the next thing in Basin. 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 Basin 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 Basin
Triggers and actions 3 triggers · 11 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.
- 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
New SubmissionTriggers when your form receives a submission.
- Add form
Create a new form under a project. POST /api/v1/forms.
- Add project
Create a new project (form-organizing container). POST /api/v1/projects.
- Delete form
Destroy a form. DELETE /api/v1/forms/:id.
- Delete submission
Destroy a submission. DELETE /api/v1/submissions/:id.
- Get form
Retrieve a single form by id. GET /api/v1/forms/:id.
- Get submission
Retrieve a single submission by id. GET /api/v1/submissions/:id.
- List forms
List all forms accessible to the account. GET /api/v1/forms.
- List projects
List all projects accessible to the account. GET /api/v1/projects.
- List submissions
List submissions for a form. GET /api/v1/submissions.
- Update form
Update a form's configuration (notifications, spam protection, branding, etc). PATCH/PUT /api/v1/forms/:id.
- Update submission
Update a submission's state fields (spam, read, trash). PATCH/PUT /api/v1/submissions/:id.
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