Connect Front

Agents search conversations, draft replies, add comments and tags in the shared inbox; connects by signing in to Front once the operator has registered an app.

Once Front is connected, an agent can search conversations in your shared inboxes, read the messages, add a comment or tag while triaging, and write a customer reply as a draft for a teammate to send.

Before you start

A Front seat in the company you want to connect. Actions run as the teammate who signs in, so the agent sees only your inboxes.
One-time setup by the woble operator. In Front go to Settings, Company, Developer and create an app. Add the OAuth feature with woble's callback URL, and under Feature access enable only MCP Server (other feature access causes 403 errors). Put the Client ID and Client Secret into OAUTH_FRONT_CLIENT_ID and OAUTH_FRONT_CLIENT_SECRET. The app works for your own Front company; other companies would need it published through Front's partner program.
You must be an owner or admin of the woble workspace. Only owners and admins can connect integrations.

Connect it

In woble open Marketplace, go to the Integrations tab, find Front and press Connect.
Press Continue with Front. A new tab opens at Front.
Sign in if needed. Front shows a consent page asking for MCP access on your behalf. Press Authorize.
The tab closes. The card shows Connected and the agent panel lists the new Front tools.

Or ask an agent

Type @ruby connect Front in any chat. The same card appears in the conversation. Only owners and admins can complete it.

Try it

"@atlas find unassigned Front conversations in the Support inbox from today and give me a one-line summary of each."
"@atlas open the Front conversation from jane@acme.com about shipping, add a team comment, and draft a reply asking for the order number."

Agents draft replies rather than sending them, and ask before archiving, moving or deleting.

If it does not connect

Front is missing or not configured: the operator has not registered the app and set the two OAUTH_FRONT settings.
403 after signing in: the app has feature access beyond MCP Server, or the redirect URL does not match. Fix it in Settings, Company, Developer, then Remove and reconnect.
Wrong company: sign in with the Front company the app was created for.
Press Test connection in Marketplace, Connected tab, to check the connection. Remove and reconnect fixes most token problems.

Disconnect

Marketplace, Connected tab, Remove. The tokens are deleted and agents lose the Front tools immediately.