Integration
Connect Mailparser to Digital Humani
When something happens in Mailparser, your agent does the next thing in Digital Humani. 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 Digital Humani 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 Digital Humani
Triggers and actions 2 triggers · 7 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 tree count by userRetrieve the number of trees planted by a specific end user for an enterprise. GET /tree?enterpriseId=:enterpriseId&user=:user — returns enterpriseId, user, count.
- Get authenticated user
Retrieve details of the currently authenticated API user. GET /user/whoami — returns internal user id, name, email, and associated enterpriseId.
- Get enterprise
Retrieve details of an enterprise by id. GET /enterprise/:id — returns created/updated dates, id, name, contact name.
- Get project
Retrieve details of a single reforestation project by id. GET /project/:id — returns full project attributes (organization, address, description, country, website in EN/FR).
- Get tree planting request
Retrieve details of a single tree-planting request by its uuid. GET /tree/:uuid — returns uuid, created date, treeCount, enterpriseId, projectId, user.
- List projects
Retrieve all available reforestation projects. GET /project — returns array of project objects (id, name, active, description, country, website, reforestation company) that can be used as projectId when planting trees.
- Plant Tree
Plants one or multiple trees
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.