Integration
Connect Mailparser to FilePost
When something happens in Mailparser, your agent does the next thing in FilePost. 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 FilePost 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 FilePost
Triggers and actions 2 triggers · 10 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.
Action
Create Intake LinkCreates a FilePost intake link — a public upload page you can send to someone so they can drop files to you, with your own limits on file type, size, count and how long it stays open.
- Delete File
Permanently deletes a file from FilePost. The stored file and its public link are removed and cannot be recovered.
- Delete intake link
Closes a FilePost intake link so it stops accepting uploads. Files already uploaded through it are untouched, and the slot frees up against your plan's limit on active links.
- Get file
Returns the details FilePost holds about one stored file — its name, size, type, download link and when it expires.
- Get intake link
Returns one intake link from your FilePost account, looked up by its intake link ID. FilePost has no single-link endpoint, so the link is selected out of your full list of intake links.
- List Files
Returns the files stored in your FilePost account, newest first, together with the total number of files.
- List intake links
Returns the intake links on your FilePost account, with each link's label, public upload page, limits and expiry.
- Update file
Changes whether a stored file's name appears in its public link, and returns the file with its new link.
- Upload File
Uploads a file to FilePost and returns its shareable link.
- Upload File From URL
Stores a file from a public web link in FilePost and returns its shareable link.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.