Integration
Connect Mailparser to Zamzar
When something happens in Mailparser, your agent does the next thing in Zamzar. 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 Zamzar 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 Zamzar
Triggers and actions 4 triggers · 9 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 Conversion JobTriggered when a new conversion job is created in your Zamzar account.
- New File
Triggered when a new file appears in your Zamzar account, whether uploaded or produced by a conversion.
- Convert File
Starts a Zamzar conversion job that converts a file you supply into another format. Returns the new job with its id and status so you can check on it or collect the converted file later.
- Create Content File
Creates a file on Zamzar from text content you supply, so it can be converted or downloaded later. Returns the stored file with its id, name and size.
- Delete conversion job
Deletes a conversion job from Zamzar. Returns the job that was removed.
- Delete file
Deletes a file stored on Zamzar. Returns the file that was removed.
- Find Converted File
Looks through the files stored on Zamzar and returns the ones whose name matches the text you supply. Use it to locate a converted file after a conversion job has finished.
- Get conversion job
Returns a single Zamzar conversion job, including its current status and any converted files it produced.
- Get file
Returns the details of a single file stored on Zamzar, including its name, format and size.
- List conversion jobs
Returns the conversion jobs in your Zamzar account, most recent first.
- List formats
Returns every source format Zamzar can convert from, along with the target formats each one can be converted into.
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