Integration
Connect Mailparser to Postali
When something happens in Mailparser, your agent does the next thing in Postali. 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 Postali 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 Postali
Triggers and actions 2 triggers · 8 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
Find postal codes in bulkBatch lookup of multiple postal codes in one call. POST /api/v1/{country}/bulk — send a list of codes, get back the per-code results (same shape as Get postal code).
- Find postal locations by query
Fuzzy search over settlement names, municipalities, and postal codes for a country. GET /api/v1/{country}/search?q=...&limit=. Useful for autocomplete.
- Get municipality
Get detail for one municipality identified by state + municipality path segments. GET /api/v1/{country}/municipio/{estado}/{municipio}.
- Get postal code
Look up a postal code (CP) for a country (mx/co/es). GET /api/v1/{country}/cp/{codigo} — returns estado, municipio, and all asentamientos (settlements) tied to the code.
- Get state
Get detail (with totals) for one state/department/province by slug. GET /api/v1/{country}/estado/{slug}.
- List municipalities
List municipalities belonging to a given state, by state slug. GET /api/v1/{country}/estado/{slug}/municipios.
- List states
List level-1 administrative divisions (states/departments/provinces) for a country, with precomputed totals. GET /api/v1/{country}/estados.
- Validate postal code
Quick validation of a postal code — returns whether it exists and how many asentamientos it covers, without the full list. GET /api/v1/{country}/validate/{codigo}. Useful for checkout form gating.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.