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

# Connect Mailparser to Quilia

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

Mailparser **2** triggers Quilia **3** triggers Quilia **18** 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 Quilia 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 Quilia

- When **New Email Parsed (One Request Per Email)** in Mailparser then **Create Contact** in Quilia
- When **New Email Parsed (One Request Per Email)** in Mailparser then **Update a Contact** in Quilia

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 Quilia

## Triggers and actions 5 triggers · 18 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

**Appointment Created**

Triggers when a new appointment is created in Quilia.

- Trigger

**Appointment Updated**

Triggers when an appointment is updated in Quilia.

- Trigger

**New Client Activity**

Triggers when a client performs an activity in Quilia, such as uploading a document to their case.

- Action

**Add New Client**

Creates a new client in Quilia with their name, phone, email, address and date of birth.

- Action

**Create Contact**

Creates a contact (such as a witness, adjustor, employer or medical provider) attached to a case or a client.

- Action

**Delete a Contact**

Permanently deletes a company or people contact from your Quilia organization.

- Action

**Delete Case**

Permanently deletes a case, including its members, documents and chat history.

- Action

**Delete Client**

Permanently deletes a client from your firm, including their case memberships.

- Action

**Delete Documents**

Deletes one or more Quilia documents, removing both the records and their stored files.

- Action

**Find a Document**

Finds a document by its id and returns its type plus a secure download link that expires after 30 minutes.

- Action

**Find Client by Phone**

Finds a client in your firm by phone number and returns the client record with the cases they belong to.

- Action

**Invite Clients to Case**

Invites clients or staff to a Quilia case. Clients are texted an invite; staff are added as invited. Returns who was invited and who was skipped.

- Action

**List Clients**

Returns the firm's clients, optionally filtered by name, email or phone.

- Action

**List Webhook Events**

Returns the webhook events your Quilia firm can subscribe to, with their descriptions and payload schemas.

- Action

**Retrieve a Single Client**

Returns a single client by id, including the cases the client belongs to.

- Action

**Retrieve Individual Case**

Returns one case by its ID, including its status, type, dates, client, organization and case members.

- Action

**Simulate Webhook Event**

Sends a sample Quilia webhook event to an endpoint URL so you can test a webhook integration.

- Action

**Update a Contact**

Updates an existing Quilia contact (a company or a person). Only the fields you fill in are changed.

- Action

**Update Case**

Updates an existing case's status, type, opening date or custom CMS data. Only the fields you fill in are changed.

- Action

**Update Client Information**

Updates an existing client's contact details, address and demographic information. Only the fields you fill in are changed.

- Action

**Upload Documents**

Uploads a document file to a client's case in Quilia and returns the new document ids.

## Each app on its own

- [ **Mailparser** Send emails to Mailparser, get structured data in return.](https://apiant.ai/connections/mailparser)
- [ **Quilia** Quilia is a platform that syncs client data to your tools, providing effortless integration and real-time...](https://apiant.ai/connections/quilia)

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 Quilia

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

Questions

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

Any of Quilia's 18 actions, including Create Contact, Update a Contact, Update Case and Update Client Information. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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

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