Front

Connect Front and your assistant can work your shared inbox — search and read conversations, pull contact and account context, and draft, send, or triage messages — so customer email turns into digests, follow-ups, and answers without leaving Town.

Everything runs as you: your assistant sees exactly the inboxes and conversations your Front teammate account can see, and every change it proposes — a draft, a reply, an assignment — asks for your approval before it happens.

What’s included

With Front connected, your assistant can:

Search and read conversations — find threads by keyword, inbox, assignee, tag, status, or date, and read the full message history
Look up contacts and accounts — pull who a customer is and their history for context
Read messages and attachments — open individual messages and fetch attachments
Create and update drafts (with approval) — prepare replies for you to review in Front
Send replies and new messages (with approval) — every send is confirmed by you first
Triage conversations (with approval) — assign, tag, move, or change the status of threads
Add internal comments (with approval) — leave notes for your team on a thread

Connecting Front

Go to Integrations
Find Front and click Connect
Sign in to Front and authorize Town when prompted
Return to Town

Town connects through Front’s official MCP server (mcp.frontapp.com) using Front’s sign-in — no API keys or setup. Your assistant is limited to what your Front teammate account can already see and do, and you can revoke access anytime from Front settings.

Front connects as you personally — each teammate connects their own Front account. Team-level Front connections aren’t supported yet.

What your assistant can do

Capability	What it does	Makes changes?
Search conversations	Find threads by keyword, inbox, assignee, tag, status, or date	No
Read a conversation	Read a thread’s full message history, including internal comments	No
Read a message	Open one message in full	No
Get an attachment	Fetch a file attached to a message	No
Search contacts	Find a customer by name, email, or handle	No
Read contact details	See a contact’s full record	No
Search and read accounts	Look up company accounts and their details	No
List drafts	See your in-flight drafts	No
List inboxes, teammates, teams, tags, statuses, and channels	Browse your workspace’s structure	No
Get your identity	Confirm which teammate the connection acts as	No
Create or update a draft	Prepare a reply for review in Front	Yes (with approval)
Delete a draft	Discard one of your unsent drafts	Yes (with approval)
Send a message	Send a reply or a new message to real recipients	Yes (with approval)
Assign, tag, move, or change status	Triage a conversation	Yes (with approval)
Add a comment	Leave an internal note on a thread	Yes (with approval)

Every capability that changes anything in Front asks for your approval first — including in routines that otherwise run on their own. Sending a message is never automatic.

Use cases

Inbox triage

Turn a busy shared inbox into a short list:

“What in Front still needs a reply from us?”
Summarize a long customer thread before you jump in
Flag conversations that have been waiting the longest

Draft replies with context

Answer grounded in the full history:

Draft a reply that reflects the whole thread and the customer’s account
Prepare responses to the morning’s new conversations for you to review in Front
Pull a contact’s past conversations before you respond

Customer context everywhere

Bring Front into your other work:

Before a call, summarize a customer’s recent conversations
Combine Front threads with your calendar and CRM in one brief
Include shared-inbox highlights in a daily digest

Example routine

A routine that keeps the inbox moving:


Every weekday at 4pm:
1. Search Front for conversations that are open and unanswered
2. Summarize each thread and who's waiting on us
3. Draft a suggested reply for the two most urgent ones
4. Send me the digest — I'll review and approve any drafts

Best practices

Approvals are the point. Sends, drafts, and triage change what your customers and team see. Review each approval card — especially sends, which email real recipients.

Name the inbox. Front workspaces get big. Telling your assistant which inbox or tag to look at keeps searches fast and precise.

Tags can trigger Front rules. Tagging or changing a conversation’s status can fire your team’s Front automations. Test triage routines on a low-stakes inbox first.

Troubleshooting

Can’t connect

Make sure you’re signing in to the correct Front account

Can’t find a conversation

Verify your Front teammate account has access to that inbox
Try narrowing by inbox, tag, or date instead of keywords alone

A send or triage action fails

Approve the pending request in Town first — writes never run without it
Confirm your Front role allows that action (the assistant can’t do more than you can)

Rate limits

Front limits how many operations each teammate can run in a short period (searches and writes have tighter limits than reads). If you hit rate limits:

Reduce how often the routine runs
Narrow searches so fewer calls are needed

Integrations overview — How integrations give your assistant context
Context and memory — How your assistant remembers and reuses what it learns