AI + Workflows

Hi, When did contacts become relationships? I’ve been away from the community for a while and am not up to speed on changes. Today I discovered my contacts on the right are now relationships. Sidebar still has contacts, but that is not visible or usable on the right. This didn’t seem like a big deal until I discovered you can no longer create new accounts as quickly and easily as before. We use the contacts and accounts visibility on the right all day, so this has really thrown a wrench in the works. Please tell me there is a way to fix this! 

Hey, Having MCP and / or API be able to (at least) read the rules details would be a game changer. Other mail services allow to import / export rules as JSON files, which also helps a lot. Concrete example: Having to screenshot your rules 1 by 1 to share it to Claude to find bugs and inconsistencies is a real pain. The bigger the company, the more relevant this would be. Is this something Front could implement? 

We use Front MCP (mcp.frontapp.com) from an inbox agent (Pit Bot / grok@xxx.com) Workflow: a teammate @mentions the agent in a Front comment and asks for a fairing-kit mockup. The agent generates a PNG and needs to post it as an internal comment on that same conversation, visible to CS, not to the customer.What we tried: add_comment with conversationId + body. The MCP schema only has those two fields. get_attachment can download comment images, but nothing can upload them.What we expected: add_comment to take an attachments list, same as Core API POST /conversations/{id}/comments which already documents attachments as multipart/form-data, max 25 MB (https://dev.frontapp.com/docs/attachments-1). Teammates already attach images to comments in the Front UI (we do this daily with color swatches).What happened: we can only post text. We have to drop the mockup in a side chat and ask a human to attach it on the thread. That breaks the workflow.Ask: please add an attachments argument on add_c

You can now connect ChatGPT and Codex assistants to the Front MCP server using the official OpenAI plugin, which greatly simplifies setup! To connect via an official directory:A Front admin (or any user authorized to install integrations from the Front App Store) must connect via the directory links above. Then, any user in your company can use the directory links to connect their own accounts.

I run an agency and we support many clients.  I want to be able to go to one spot and see all the emails from that company.  I had originally thought about doing this as tags. Then we made mailboxes for all the clients. This seems to be challenging though. I am seeing messages not show up in the mailboxes. I don’t think each client should have their own mailbox. How are other agencies doing this?

I was hoping to run some high-level reports through Claude using Front’s Analytics API, but hadn’t realized the Analytics API isn’t exposed in the MCP. Is there a timeline for this?Here is exactly what I was after:Total inbound message volume by inbox (in a specific calendar month) from the Workload report Topic breakdowns by inbox (in a specific calendar month) from the Topics report Average Response Time from Team Performance (for a specific calendar month) Smart QA / Smart CSAT scores (for a specific month)Here is what Claude said: The MCP doesn't expose Front's Analytics module (Workload, Topics, Team Performance, Smart QA, Smart CSAT reports) — those live in a separate reporting API that isn't part of the connector we have access to. 

I connected the Front MCP server to Claude Code and it works well for conversations, messages, drafts, comments and tags. Thank you for shipping it. One gap: there is no way to work with message templates. The OAuth app's Resource permissions grid includes a "Message templates" row with Read, Write and Delete, so I ticked it and re-authorized, but the MCP server still exposes no tool that touches templates. The full tool list I get is: search_conversations, read_conversation, move_conversation, assign_conversation, tag_conversation, update_conversation_status, read_message, send_message, list_drafts, create_draft, update_draft, delete_draft, add_comment, get_attachment, list_channels, list_inboxes, list_tags, list_statuses, list_teammates, list_teams, read_contact, search_contacts, read_account, search_accounts, get_my_identity. The server also advertises no MCP resources. For comparison, the Core REST API does support templates: GET /message_templates works with an API token carrying

Our operations email is basically a distribution list that consist of our shared mailbox + archiving backend.  We would like to take advantage of the auto reply feature on FRONT.Has anyone found a good workaround, or an easy way to automate replies when there’s a distribution list in the recipients field?

I'm currently working through Front onboarding and have only seen the platform through the training exercises so far.One thing I'm curious about is how experienced teams decide when to create new rules, tags, or automations versus keeping things manual. The examples in training make sense, but I imagine real environments can become complex pretty quickly.For those who manage Front long-term, what are some "lessons learned" or best practices you wish you had known when setting up workflows for the first time?

When Claude creates a reply draft through the Front MCP server, the draft contains only the body text - no quoted thread history and no signature. Front's own Reply button adds both.The Core API already supports this. POST /conversations/{id}/drafts accepts quote_body, signature_id and should_add_default_signature. The MCP create_draft and update_draft tools expose none of them, so an AI-created draft can never match what Front itself produces.Separately, there is no way to create a forward at all: no forward endpoint exists in the Core API, only in the Plugin SDK (Front.forward() / replyOptions.type: "forward"), which requires a plugin running in the Front UI.Impact: I have to re-add the quoted history and my signature by hand on every AI-drafted reply. The manual rework defeats the purpose of the integration - it is faster to skip the connector and hit Reply.Asks: (1) expose quote_body, signature_id and should_add_default_signature in create_draft and update_draft, ideally with quoti

Hi guysWe have unique use case where we have certain Mentors on our platform + their respective VAs, VAs go through their inbox and support our customers. Here is the structure:We treat their personal inboxes (Mentors) as support inboxes, the Mentees are our customers essentially. Currently mirroring the mentor convos into shared inboxes and only capturing mentee comms using our CRM integration and custom fields + rules.Was wondering if there’s a way that we can leverage Front AI to automatically segment normal conversations from actual tickets and tag them, actual concerns raised by the mentees.We are currently using conversation custom dropdown fields to automatically move convos to a general/no escalation inbox (e.g Conversation Type = Ticket/Conversation)

I recently joined a team that uses Front as their primary tool for communicating with it’s users. I wanted to learn what others have found helpful as they were in the process to become a Front admin for their organizations and what features they utilize the most to gain operational efficiencies 

I am exploring the available features that front offers and how they may help our operations. We tend to have many issue types and categories. I was thinking of either using tags or custom fields to identify issue types. How have your teams utilized custom fields and how does that impact your reporting and analytics?

Does the Front MCP connector have the ability to auto-draft templates for bulk sends to a list of contacts?

Hello, Curious if anyone has seen any rules (outside of the “standard” rule set that really helps CS teams perform well? I am aware of the SLA features and love those, but any creative workflows or sequences anyone has seen work really well for Customer Success teams?

Good news :) Hopefully v1.1 will be ready soon. When you query open conversations via the API or MCP, you get the global conversation status not the per-inbox view your sidebar shows. This means archived conversations still show as open if they're active in any other inbox, making it impossible to programmatically replicate what you see in Front. For any team building AI agents or automations on top of Front, this is a fundamental blocker. 

My team and I aren’t able to send emails. We can receive them, but we get an “unable to send” error. Is this happening to anyone else? Hoping to get the resolved as soon as possible. Thank you!

We’re happy to announce that we’re now officially listed in Claude’s connector directory! This should make it easy for you to connect to the Front MCP server. Prior to being listed on the directory, you had to connect Claude to Front’s MCP server as a custom connector, which involved setting up a developer app in Front and then configuring the connection details in Claude. You can now connect directly from the directory listing by simply logging into Front when prompted. If you have other directories you’d like to see us listed in, please let us know in the comments!