--- title: "Connect Mailparser to TemplateDocs - APIANT.ai" description: "When \"New Email Parsed (One Request Per Email)\" fires in Mailparser, your agent runs \"Add template\" in TemplateDocs." canonical: "https://apiant.ai/connect/mailparser-to-templatedocs" --- # Connect Mailparser to TemplateDocs When **New Email Parsed (One Request Per Email)** fires in [Mailparser](https://apiant.ai/connections/mailparser), your agent runs **Add template** in [TemplateDocs](https://apiant.ai/connections/templatedocs). Describe the whole flow and it is built, tested on every scenario and kept running. Mailparser **2** triggers TemplateDocs **5** 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 TemplateDocs 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 TemplateDocs - When **New Email Parsed (One Request Per Email)** in Mailparser then **Add template** in TemplateDocs - When **New Email Parsed (One Request Per Email)** in Mailparser then **Update template** in TemplateDocs 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 TemplateDocs ## Triggers and actions 2 triggers · 5 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 template** Uploads a Word document to TemplateDocs as a new template, and returns the template's id along with the placeholders found inside it. - Action **Delete template** Removes a template from your TemplateDocs account. - Action **Get template** Returns the details of one template, including its name, size, checksum and the placeholder tags it contains. - Action **List templates** Returns the templates available in your TemplateDocs account, each with its name, size and placeholder tags. - Action **Update template** Renames a template or changes its settings. Returns the id of the template that was updated. ## Each app on its own - [ **Mailparser** Send emails to Mailparser, get structured data in return.](https://apiant.ai/connections/mailparser) - [ **TemplateDocs** TemplateDocs is a tool for creating documents from templates.](https://apiant.ai/connections/templatedocs) 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 TemplateDocs - [ **Goaffpro to TemplateDocs** Affiliate marketing platform for ecommerce stores, managing affiliate recruiting, commissions, and referral...](https://apiant.ai/connect/goaffpro-to-templatedocs) - [ **Mailjet to TemplateDocs** Mailjet is an all-in-one solution to send, track and deliver transactional, notification and marketing emails.](https://apiant.ai/connect/mailjet-to-templatedocs) - [ **Perigon to TemplateDocs** REST API for real-time news search, monitoring, and enriched data on companies, people, and topics.](https://apiant.ai/connect/perigon-to-templatedocs) - [ **HubSpot to TemplateDocs** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-templatedocs) - [ **Salesforce to TemplateDocs** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-templatedocs) - [ **Slack to TemplateDocs** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-templatedocs) Questions ## Mailparser and TemplateDocs, 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 TemplateDocs when something happens in Mailparser? Any of TemplateDocs's 5 actions, including Update template, Add template, Get template and List templates. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from TemplateDocs to Mailparser? TemplateDocs has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads TemplateDocs's API documentation and adds it. ### ### Do I have to build a connector for Mailparser or TemplateDocs? 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 TemplateDocs without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in TemplateDocs 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.