Integration
Connect Mailparser to Exist
When New Email Parsed (One Request Per Email) fires in Mailparser, your agent runs Get User Profile in Exist. 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 Exist to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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)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 Exist
When New Email Parsed (One Request Per Email) in Mailparser
then Get User Profile in Exist
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 Exist
Triggers and actions 3 triggers · 8 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.
- New Attribute Value
Triggers when a new daily value is recorded for the chosen Exist attribute, such as steps or mood.
- Acquire Attributes
Takes ownership of one or more Exist attributes for this app so it can write their values, creating templated attributes the user doesn't have yet.
- Create Attributes
Creates one or more new attributes in the user's Exist account, from a template or as custom attributes, and returns which succeeded and which failed.
- Get Attribute Values
Returns the daily values recorded for one of the user's Exist attributes, newest first.
- Get User Profile
Returns the authenticated Exist user's profile: name, avatar, timezone, local time and unit preferences.
- Increment Attribute Values
Adds amounts to the existing daily values of attributes your app owns in Exist, returning each attribute's new total.
- List Attributes with Values
Returns the user's Exist attributes together with their recent daily values.
- Release Attributes
Releases your ownership of one or more Exist attributes so another service can provide their data, or they become inactive.
- Update Attribute Values
Saves daily total values for attributes you own in Exist, up to 35 at a time, replacing any value already stored for those days.
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
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 Exist
ActiveCampaign to ExistActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to ExistOrganize anything with Airtable, a modern database created for everyone.
Asana to ExistAsana is a collaborative information manager for workspace.
ClickUp to ExistClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to ExistDiscord is an all-in-one voice and text chat for gamers.
Brevo to ExistBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Questions
Mailparser and Exist, 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 Exist when something happens in Mailparser?
Any of Exist's 8 actions, including Create Attributes, Update Attribute Values, Acquire Attributes and Get Attribute Values. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Exist to Mailparser?
Exist has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Exist's API documentation and adds it.
Do I have to build a connector for Mailparser or Exist?
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.
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.