# Connect Mailparser to Modusign

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

Mailparser **2** triggers Modusign **1** trigger Modusign **12** 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 Modusign to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

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 Modusign

- When **New Email Parsed (One Request Per Email)** in Mailparser then **Add document request** in Modusign
- When **New Email Parsed (One Request Per Email)** in Mailparser then **Request Document With Template** in Modusign

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 Modusign

## Triggers and actions 3 triggers · 12 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

**Document Updated**

Triggers when a document is created, signed, completed, or aborted.

- Action

**Add document request**

Request signatures on a document (signature request).

- Action

**Add label**

Creates a new label in Modusign.

- Action

**Cancel document request**

Cancel a pending signature request.

- Action

**Delete label**

Delete a label.

- Action

**Delete template**

Delete a template.

- Action

**Get Document**

Retrieves the details of a single Modusign document by its ID.

- Action

**Get template**

Get a template by id.

- Action

**Get user**

Gets the Modusign user whose credentials the connection uses.

- Action

**Remind Signing**

Resend signing request notifications to signers who did not sign.

- Action

**Request Document With Template**

Create a document using a template and request signers to sign it.

- Action

**Search Documents**

Search for documents with specific conditions.

- Action

**Update label**

Update a label.

## Each app on its own

- [ **Mailparser** Send emails to Mailparser, get structured data in return.](https://apiant.ai/connections/mailparser)
- [ **Modusign** Modusign is a simple electronic contract service that makes signing a contract and its storage at once at...](https://apiant.ai/connections/modusign)

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 Modusign

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

Questions

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

Any of Modusign's 12 actions, including Update label, Add document request, Add label and Get Document. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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.