Integration
Connect Mailparser to Chili Piper
When New Email Parsed (One Request Per Email) fires in Mailparser, your agent runs Add user in Chili Piper. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Mailparser and Chili Piper to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Mailparser can start in Chili Piper
When New Email Parsed (One Request Per Email) in Mailparser
then Add user in Chili Piper
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Mailparser and Chili Piper
Triggers and actions 2 triggers · 28 actions
- 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.
- Add data field
Creates and publishes a custom data field on people or companies in Chili Piper.
- Add meeting
Books a meeting for one host on one of their personal meeting types with a primary guest, sending calendar invites immediately.
- Add meeting type
Creates a reusable team meeting type (name, duration, location, invite content, availability and schedule) in a Chili Piper workspace.
- Add user
Creates a new user in your Chili Piper organization, optionally emailing them an invitation right away.
- Add workspace
Creates a new, empty workspace in your Chili Piper organization and returns it.
- Cancel Meeting
Cancels a Chili Piper meeting.
- Delete meeting type
Permanently deletes a team meeting type. Scheduling links or routers that use it stop working.
- Delete workspace
Deletes a Chili Piper workspace; its members and Workspace Managers lose access to it. Returns the deleted workspace.
- Find available meeting slots
Returns the bookable meeting start times for a meeting type and set of attendees over a time window.
- Find User
Finds Chili Piper users whose email or name matches the search text.
- Find users by filter
Returns Chili Piper users matching a combination of search text, emails, user IDs, workspace and admin status.
- Get meeting type
Returns one team meeting type by its id, including its duration, location, availability, schedule and attached reminders.
- Get Tenant Info
Returns your Chili Piper organization's details, such as its ID, name and type.
- Get User
Returns a Chili Piper user's profile by ID.
- Get workspace
Returns one team workspace by its ID, including its name, emoji, logo and audit metadata.
- List concierge routers
Returns the concierge routers in your Chili Piper organization, optionally limited to one workspace, including each router's id and slug.
- List data fields
Returns the organization's data fields (custom, default and internal), optionally filtered by name, reference, object type or value type.
- List distributions
Returns the published round-robin distributions in your organization, optionally filtered by workspace, name, assignment type or member.
- List Meetings
Returns the meetings booked in Chili Piper between a start and end time, 50 per page.
- List Meeting Types
Lists the meeting types in your Chili Piper organization, optionally for one workspace.
- List teams
Returns the teams in your Chili Piper organization, optionally filtered by workspace, team name or member.
- List Workspaces
Lists the workspaces in your Chili Piper organization, optionally filtered by name.
- Mark Meeting No-Show
Marks a Chili Piper meeting as a no-show.
- Mark Meeting Showed
Marks a Chili Piper meeting as attended.
- Update meeting
Reschedules or edits a booked meeting: change its start time, host, assignees, additional guests or the primary guest's attendance.
- Update meeting type
Updates a team meeting type in Chili Piper — its name, invite content, duration, status, location, limits, availability or schedule. Only the values you fill in are changed.
- Update user
Updates a Chili Piper user's profile: name, job title, phone, location, conferencing details, booking slug, timezone and working hours. Fields left blank stay unchanged.
- Update workspace
Renames a Chili Piper workspace or changes its emoji or logo. Only the values you fill in are changed.
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
What our customers say
More from Mailparser
Mailparser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Mailparser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mailparser to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailparser to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Mailparser to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Mailparser to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Chili Piper
Questions
Mailparser and Chili Piper, answered
What can start an automation from Mailparser?
Any of Mailparser's 2 triggers in the catalog, including New Email Parsed (One Request Per Email) and New Email Parsed (One Request Per Row). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Chili Piper when something happens in Mailparser?
Any of Chili Piper's 28 actions, including Update meeting, Update meeting type, Update user and Update workspace. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Chili Piper to Mailparser?
Chili Piper has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Chili Piper's API documentation and adds it.
Do I have to build a connector for Mailparser or Chili Piper?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Mailparser and Chili Piper without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in Chili Piper once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.