---
title: "Connect Mailparser to Journy Io - APIANT.ai"
description: "When \"New Email Parsed (One Request Per Email)\" fires in Mailparser, your agent runs \"Add or update user\" in Journy Io."
canonical: "https://apiant.ai/connect/mailparser-to-journy-io"
---

# Connect Mailparser to Journy Io

When **New Email Parsed (One Request Per Email)** fires in [Mailparser](https://apiant.ai/connections/mailparser), your agent runs **Add or update user** in [Journy Io](https://apiant.ai/connections/journy-io). Describe the whole flow and it is built, tested on every scenario and kept running.

Mailparser **2** triggers Journy Io **7** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Mailparser and Journy Io to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Mailparser can start in Journy Io

- When **New Email Parsed (One Request Per Email)** in Mailparser then **Add or update user** in Journy Io
- When **New Email Parsed (One Request Per Email)** in Mailparser then **Add users to account** in Journy Io

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 Journy Io

## 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.

- Trigger

**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

**Add or update account**

Creates an account in journy.io, or updates its properties if it already exists.

- Action

**Add or update user**

Creates a user in journy.io, or updates the properties of an existing user identified by user ID or email.

- Action

**Add users to account**

Adds up to 100 users to a journy.io account, identifying the account by its ID or domain.

- Action

**Delete account**

Deletes an account in journy.io, identified by its account ID and/or domain.

- Action

**Delete user**

Deletes a user from journy.io, identified by user ID, email, or both.

- Action

**List events**

Returns the event types defined in your journy.io workspace, with each event's name, id and group.

- Action

**Remove user from account**

Removes up to 100 users from a journy.io account. The users stay stored in journy.io but are marked as removed from the account.

## Each app on its own

- [ **Mailparser** Send emails to Mailparser, get structured data in return.](https://apiant.ai/connections/mailparser)
- [ **Journy Io** Customer success platform that tracks product usage, support, and CRM signals to detect churn risk and...](https://apiant.ai/connections/journy-io)

Reviews

## What our customers say

## More from Mailparser

- [ **Mailparser to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/mailparser-to-hubspot)
- [ **Mailparser to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/mailparser-to-salesforce)
- [ **Mailparser to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/mailparser-to-slack)
- [ **Mailparser to Google Sheets** Google Sheets](https://apiant.ai/connect/mailparser-to-google-sheets)
- [ **Mailparser to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/mailparser-to-gmail)
- [ **Mailparser to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/mailparser-to-google-calendar)

## More into Journy Io

- [ **HubSpot to Journy Io** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-journy-io)
- [ **Salesforce to Journy Io** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-journy-io)
- [ **Slack to Journy Io** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-journy-io)
- [ **Google Sheets to Journy Io** Google Sheets](https://apiant.ai/connect/google-sheets-to-journy-io)
- [ **Gmail to Journy Io** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-journy-io)
- [ **Google Calendar to Journy Io** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-journy-io)

Questions

## Mailparser and Journy Io, 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 Journy Io when something happens in Mailparser?

Any of Journy Io's 7 actions, including Add or update account, Add or update user, Add users to account and List events. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Journy Io to Mailparser?

Journy Io has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Journy Io's API documentation and adds it.

###

### Do I have to build a connector for Mailparser or Journy Io?

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 Journy Io without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in Journy Io 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.
