# Connect Mailparser to Fluent Support When **New Email Parsed (One Request Per Email)** fires in [Mailparser](https://apiant.ai/connections/mailparser), your agent runs **Add Tag to Ticket** in [Fluent Support](https://apiant.ai/connections/fluent-support). Describe the whole flow and it is built, tested on every scenario and kept running. Mailparser **2** triggers Fluent Support **2** triggers Fluent Support **10** 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 Fluent Support 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 Fluent Support - When **New Email Parsed (One Request Per Email)** in Mailparser then **Add Tag to Ticket** in Fluent Support - When **New Email Parsed (One Request Per Email)** in Mailparser then **Create Customer** in Fluent Support 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 Fluent Support ## Triggers and actions 4 triggers · 10 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 Customer** Triggers when a new customer is added in Fluent Support. - Trigger **New Ticket** Triggers when a new support ticket is created in Fluent Support. - Action **Add Tag to Ticket** Adds an existing tag to a Fluent Support ticket. - Action **Close Ticket** Closes a Fluent Support ticket. - Action **Create Customer** Creates a new customer in Fluent Support with their name, email, contact details and an optional note. - Action **Create Ticket** Creates a new support ticket in Fluent Support for an existing customer. - Action **Get Ticket** Returns a Fluent Support ticket with its customer, responses and details. - Action **List Customers** Returns the customers in your Fluent Support help desk, optionally filtered by a search term. - Action **List Tickets** Returns support tickets from Fluent Support, optionally matching a search term. - Action **Reopen Ticket** Reopens a closed Fluent Support ticket. - Action **Reply to Ticket** Adds an agent reply or internal note to a Fluent Support ticket, optionally closing the ticket. - Action **Update Ticket** Updates one property of a ticket — its priority, customer priority, assigned agent or product. ## Each app on its own - [ **Mailparser** Send emails to Mailparser, get structured data in return.](https://apiant.ai/connections/mailparser) - [ **Fluent Support** WordPress helpdesk plugin for managing customer support tickets, with REST API and webhook integrations.](https://apiant.ai/connections/fluent-support) 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 Fluent Support - [ **ActiveCampaign to Fluent Support** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-fluent-support) - [ **Airtable to Fluent Support** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-fluent-support) - [ **Asana to Fluent Support** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-fluent-support) - [ **ClickUp to Fluent Support** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-fluent-support) - [ **Discord to Fluent Support** Discord is an all-in-one voice and text chat for gamers.](https://apiant.ai/connect/discord-to-fluent-support) - [ **Brevo to Fluent Support** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-fluent-support) Questions ## Mailparser and Fluent Support, 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 Fluent Support when something happens in Mailparser? Any of Fluent Support's 10 actions, including Create Customer, Create Ticket, Update Ticket and Add Tag to Ticket. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Fluent Support to Mailparser? Fluent Support has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Fluent Support's API documentation and adds it. ### ### Do I have to build a connector for Mailparser or Fluent Support? 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.