Integration · Front
Your service agent in Front. Drafts, tags and comments for the team.
Carla works in your shared inboxes through Front’s MCP server, signed in as a Front teammate of its own. It reads new conversations, tags them, drafts replies and leaves comments for the people who decide.
Create a Front app once. Then sign in as the agent.
Front’s MCP server needs an app with OAuth. A webhook brings new messages to the agent.
- 01
Create an app in Front
In Front, open Settings, Company, Developer, create an app and add an OAuth feature with only the MCP server enabled.
- 02
Add Front in zwrm
Paste the app’s client ID and secret in the dashboard. Grant the narrowest scopes: read; write for drafts, comments and tags; send only if needed.
- 03
Sign in as the agent
Give the agent a Front teammate account and sign in with it from the agent’s page.
- 04
Bring in new messages
Add a Front webhook trigger, so that new messages in the inboxes you choose start a run.
zwrm checks the signature of every Front webhook before a run starts.
Read the docsWhat agents can do in Front. Within the scopes you grant.
The agent works as a Front teammate, through Front’s MCP server. Its inboxes and permissions are that teammate’s.
Agents can read
- Conversations and messages in the inboxes its account can see
- Comments and tags on those conversations
- The status of a conversation and who it’s assigned to
Agents can write
- Reply drafts for a person to check and send
- Internal comments for teammates
- Tags on conversations
- Sent replies, only if you grant the send scope
Agents can’t
- Read inboxes its Front account can’t see
- Send anything when you granted only read and write
- Borrow a colleague’s Front account: without its own sign-in, the agent is denied
Front’s MCP server decides which actions exist. zwrm passes on only the tools you select.
A teammate of its own. With the scopes you grant.
Its own Front account
Carla signs in as a Front teammate you create for it. Comments and drafts show that name, and it sees only that teammate’s inboxes.
Drafts unless you allow sending
Grant read and write for drafts, comments and tags, and leave send out. Then a person sends every reply.
Signed webhooks
zwrm checks the signature of every Front webhook before a run starts, so only Front can wake the agent.
Every call logged
Each Front call is logged with the agent, the account and the result, next to the run that made it.
Every run is logged in the dashboard, with the tools the agent called and what came back.
How zwrm handles securityRoutines in Front. Explained once, they run on their own.
- On every new message
Support inbox triage
Tags each new conversation, drafts a reply to routine questions and leaves a comment for the right teammate on the rest.
Carla · Customer service - Daily · 16:00 →
Waiting conversations
Lists the conversations that have waited longer than a day and sends the list to the support lead in Teams.
Carla · Customer service - Mon · 08:00 →
Questions of the week
Groups last week’s conversations by topic and adds new questions to the FAQ page in Notion.
Pia · Writing
More integrations. Same setup, other tools.
-
Mention an agent on a shared page. It answers in the thread as its own Notion user.
-
Mail, calendars, files and Teams chats, through a Microsoft 365 user of the agent’s own.
-
Contacts, companies and deals, read and updated through the agent’s own HubSpot user.
-
Open items and accounting data, through an MCP server or exports you set up.
-
Mention it in an issue. It works on a branch and opens a pull request.
Tell us what lands on your desk every week. We’ll show you an agent doing it.
A demo with our team, in English or German. Bring one recurring task and the tools it touches.