Integration
Connect Mailparser to redirect.pizza
When something happens in Mailparser, your agent does the next thing in redirect.pizza. 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 redirect.pizza 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 redirect.pizza
Triggers and actions 2 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.
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
Check domain DNSForces redirect.pizza to re-check the DNS records for a domain and returns the domain's updated status.
Action
Create RedirectCreates a redirect that sends visitors from one or more source domains to a destination URL.
Action
Delete RedirectDeletes a redirect so its source domains no longer forward traffic.
Action
Get DomainReturns one domain with its DNS requirements, verification state and SSL status.
Action
Get Email forwardReturns one email forward, showing which address mail arrives at and where it is delivered.
Action
Get RedirectReturns one redirect with its sources, destination, domains and forwarding settings.
Action
Get Team quotaReturns the connected team, including its plan quota and how much of it is in use.
Action
List DomainsReturns every domain in the connected team, with each domain's DNS requirements, verification state and SSL status.
Action
List Email forwardsReturns every email forward in the connected team, showing which address mail arrives at and where it is delivered.
Action
List RedirectsReturns every redirect in the connected team, with each redirect's sources, destination, domains and forwarding settings.
Action
Update RedirectUpdates an existing redirect: its sources, destination, redirect type, forwarding and tracking settings, tags or notes.
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