Integration
Connect Mailparser to 5pm
When something happens in Mailparser, your agent does the next thing in 5pm. 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 5pm 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 5pm
Triggers and actions 9 triggers · 21 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 ProgressTriggers when a new task progress is created.
- New Project
Fires when a new project is created in 5pm (poll ProjectsService getList).
- New Task
Triggers when a new support task is created.
- New User
Triggers when a new support user is created.
- Updated Project
Fires when a project is updated in 5pm (poll ProjectsService getList).
- Updated Task
Triggers when a new support task is updated.
- Updated User
Triggers when a new support user is updated.
- Add Task Progress
Add Task Progress (progress in percent and house down).
- Add User
Create a new user in the 5pm account (UsersService add).
- Create Note
Creates a new note in task.
- Create Project
Creates a new project.
- Create Task
- Delete Note
Remove an activity note/progress message (ActivityService remove).
- Delete Project
Remove a project (ProjectsService remove).
- Delete Task
Remove a task from a 5pm project (TasksService remove).
- Delete User
Remove a user from the account (UsersService remove).
- Find Project by Id
Retrieve a single project by its id (ProjectsService getById).
- Find Task
Finds a task in the application.
- Find Task by Id
Finds a task by Id in the application.
- Find User by Email
Retrieve a user by their email address (UsersService getByEmail).
- Find User by Id
Finds a user by Id in the system.
- List Notes
List activity notes/progress messages on a task (ActivityService getList).
- List Projects
List all projects in the account (ProjectsService getAll/getList).
- List Users
List all users in the account (UsersService getAll).
- Update Note
Update an activity note/progress message (ActivityService update).
- Update Project
Update a project's fields (ProjectsService update).
- Update Task
Update task in the application.
- Update User
Update a user's fields (UsersService update).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.