---
title: "Connect Mailparser to iContact - APIANT.ai"
description: "When \"New Email Parsed (One Request Per Email)\" fires in Mailparser, your agent runs \"Create Contact\" in iContact."
canonical: "https://apiant.ai/connect/mailparser-to-icontact"
---

# Connect Mailparser to iContact

When **New Email Parsed (One Request Per Email)** fires in [Mailparser](https://apiant.ai/connections/mailparser), your agent runs **Create Contact** in [iContact](https://apiant.ai/connections/icontact). Describe the whole flow and it is built, tested on every scenario and kept running.

Mailparser **2** triggers iContact **2** triggers iContact **25** 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 iContact 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 iContact

- When **New Email Parsed (One Request Per Email)** in Mailparser then **Create Contact** in iContact
- When **New Email Parsed (One Request Per Email)** in Mailparser then **Create Message** in iContact

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 iContact

## Triggers and actions 4 triggers · 25 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.

- Trigger

**New contact**

Triggers when a new contact is added to an iContact client folder, optionally only contacts on a chosen list.

- Trigger

**New list**

Triggers when a new subscriber list is created in an iContact client folder.

- Action

**Add campaign**

Creates a new campaign (sending profile with sender name, sender email and CAN-SPAM mailing address) in an iContact client folder.

- Action

**Add custom field**

Creates a new custom field for contacts in an iContact client folder.

- Action

**Create Contact**

Create a new contact in an iContact client folder.

- Action

**Create List**

Create a new contact list in a client folder.

- Action

**Create Message**

Create a new email message in a client folder.

- Action

**Delete Contact**

Delete an iContact contact by contact ID.

- Action

**Delete list**

Deletes a subscriber list from an iContact client folder.

- Action

**Get Accounts**

List iContact accounts accessible to these credentials.

- Action

**Get campaign**

Returns one iContact campaign (its sending profile, from name and email, and mailing address) by its id.

- Action

**Get Client Folders**

List client folders within an iContact account.

- Action

**Get Contact**

Retrieve a single iContact contact by contact ID.

- Action

**Get list**

Returns one subscriber list from an iContact client folder, including its name, public name and description.

- Action

**Get message**

Returns one email message from an iContact client folder, including its subject, HTML and text bodies, and SpamCheck results.

- Action

**List Campaigns**

List sending campaigns (from-name/email profiles) in a client folder.

- Action

**List Contacts**

List contacts in a client folder, optionally filtered by email or status.

- Action

**List Custom Fields**

List custom fields defined in a client folder.

- Action

**List Lists**

Retrieve all contact lists in a client folder.

- Action

**List Messages**

List email messages in a client folder.

- Action

**List sends**

Returns every email send (pending, sending, released and cancelled) in an iContact client folder, including its message, target lists and segments, schedule, recipient count and status.

- Action

**List Subscriptions**

List subscriptions in a client folder, optionally filtered by contact or list.

- Action

**Send Message to List**

Schedule/send an existing message to one or more lists.

- Action

**Subscribe Contact to List**

Subscribe a contact to a list (creates a subscription).

- Action

**Unsubscribe Contact from List**

Remove a subscription, unsubscribing a contact from a list.

- Action

**Update Contact**

Update an existing iContact contact by contact ID.

- Action

**Update list**

Updates an existing iContact subscriber list's name, public name, description or owner-notification setting. Only the values you supply are changed.

## Each app on its own

- [ **Mailparser** Send emails to Mailparser, get structured data in return.](https://apiant.ai/connections/mailparser)
- [ **iContact** iContact allows your company to create, send, and track your email marketing messages with ease and...](https://apiant.ai/connections/icontact)

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 iContact

- [ **HubSpot to iContact** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-icontact)
- [ **Google Sheets to iContact** Google Sheets](https://apiant.ai/connect/google-sheets-to-icontact)
- [ **Gmail to iContact** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-icontact)
- [ **Google Calendar to iContact** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-icontact)
- [ **Google Drive to iContact** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-icontact)
- [ **ActiveCampaign to iContact** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-icontact)

Questions

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

Any of iContact's 25 actions, including Create Contact, Create List, Create Message and Send Message to List. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from iContact to Mailparser?

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

###

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

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

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