Integration
Connect Mailparser to Buttondown
When something happens in Mailparser, your agent does the next thing in Buttondown. 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 Buttondown 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 Buttondown
Triggers and actions 6 triggers · 29 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 DraftTriggers when a new draft is created.
- New Scheduled Email
Triggers when a new email is scheduled.
- Newsletters
Triggers when a new newsletter is created.
- New Tag
Triggers when a new tag is created.
- Add Segment
Create a new subscriber segment.
- Add Survey
Create a new survey.
- Create Draft
Creates a draft.
- Create Email
Creates an email.
- Create Subscriber
Creates a subscriber.
- Delete Automation
Delete an automation by id.
- Delete Email
Delete an email by id.
- Delete Newsletter
Delete a newsletter by id.
- Delete Segment
Delete a subscriber segment by id.
- Delete Subscriber
Remove a subscriber by id or email address.
- Delete Survey
Delete a survey by id.
- Delete Tag
Delete a tag by id.
- Find Tag
Finds a tag given its name.
- Get Automation
Retrieve a single automation by id.
- Get Email
Retrieve a single email by id.
- Get Newsletter
Retrieve a single newsletter by id.
- Get Segment
Retrieve a single subscriber segment by id.
- Get Survey
Retrieve a single survey by id.
- Get Tag
Retrieve a single tag by id.
- List Automations
List all automations configured on the account.
- List Segments
List all subscriber segments.
- List Surveys
List all surveys on the account.
- Publish Email
Publish a drafted email so it is sent and made public.
- Update Automation
Update an automation's configuration.
- Update Email
Update an existing email's content or metadata.
- Update Newsletter
Update a newsletter's settings.
- Update Segment
Update a subscriber segment's definition.
- Update Survey
Update a survey's configuration.
- Update Tag
Update a tag's name or metadata.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.