Front
Capture shared inbox conversations and comments from Front
The Front integration captures conversations from your Front shared inboxes in real time. Customer messages, your team’s replies, and the internal comments alongside them flow into Modem, where they are grouped into topics, classified by type, and linked to the people and companies behind them.
How it works
Modem connects to your Front company with OAuth, authorized once by a Front admin. During that exchange Modem records which Front company the connection belongs to, which is also how it attributes each incoming webhook delivery to your organization.
From then on Front pushes conversation activity to Modem as it happens: new messages, comments, and changes to a conversation’s status, assignee, and tags. Every delivery is signature-verified and time-stamped, and Modem rejects deliveries that fail verification or arrive more than five minutes late.
Front access tokens are short-lived, so a background job refreshes the connection’s credentials before they expire. The connection normally stays authenticated without any action from you.
Connecting also requests a one-time backfill of your recent conversations, so history shows up without waiting for new traffic. See Historical Backfill below.
Prerequisites
- Owner or admin role in your Modem organization, to connect and manage the integration
- A Front admin to authorize the connection. Front only lets admins authorize an app, and a non-admin’s attempt comes back as a rejected grant.
Setup
Start the connection
Go to Settings → Integrations → Front in your Modem dashboard and click Connect Front. Only organization owners and admins can connect.
Authorize Modem in Front
You’ll be redirected to Front to sign in and approve the connection. This step must be done by a Front admin. See Permissions below for what Modem can read.
Confirm the connection
Front redirects you back to Modem automatically. The settings page shows the connected Front company, and new conversation activity starts flowing immediately.
Wait for the backfill
Modem imports your recent conversations in the background. See Historical Backfill below.
Permissions
Modem’s Front app holds read-only access, configured on the app itself rather than requested each time someone connects. There is nothing to pick during authorization: a Front admin approves the connection, and the app’s read access applies.
Modem can read:
- Shared inbox conversations and their messages
- Internal comments on those conversations
- Contacts and teammates on a conversation
- Conversation metadata: inbox, status, and tags
Modem does not access:
- Sending, replying, or changing anything in Front
- Private (individual) inboxes, unless an admin turns one on in Choosing inboxes
- Front account credentials or billing information
What Gets Captured
Shared inboxes are captured by default, and private inboxes are not. Each inbox becomes its own channel in Modem, and a conversation is filed under the inbox it lives in. To change which inboxes are captured, see Choosing inboxes.
Choosing inboxes
Settings → Integrations → Front lists every inbox in your Front company with the addresses it receives on. Owners and admins can turn individual inboxes on or off and save; other members see the list read-only.
- Turning an inbox off stops new conversations from it reaching Modem. Conversations already in Modem stay.
- New shared inboxes start on. Private inboxes, marked Private, start off.
- A conversation in several inboxes is captured if any of them is on, and is filed under an inbox that is on.
- The backfill skips conversations whose inboxes are all off.
Messages and comments
Each Front conversation is captured as one conversation in Modem, threaded like a support ticket:
- Inbound messages from customers and other external parties
- Outbound messages your teammates send in reply
- Internal comments written by your team, marked as internal
Email bodies are cleaned before they’re stored: quoted-reply chains and signature blocks are stripped, so topics quote what the person actually wrote rather than the history beneath it. Short-form channels Front delivers (chat, SMS, and similar) are kept as-is, since a trailing “Thanks” there is content rather than a signature. Inline attachment data is dropped; attachment files themselves are not ingested.
Modem reacts to these Front events:
| Front event | What Modem does |
|---|---|
| Inbound message received | Adds the customer’s message to the conversation |
| Outbound message sent | Adds your teammate’s reply |
| Comment added | Adds the internal comment |
| Conversation archived or reopened | Updates the conversation’s state |
| Conversation deleted or restored | Records the change; a deleted conversation stays in Modem |
| Conversation moved | Updates the inbox the conversation is filed under |
| Assignee changed | Refreshes the conversation’s status and tags |
| Tag added or removed | Updates the conversation’s tags |
Status, inbox, and tag changes are recorded on the conversation for context, but these housekeeping entries don’t feed topic analysis; only real messages and comments do.
Conversation status
Front’s conversation statuses are mapped onto Modem’s conversation states. Companies using Front’s ticket statuses get the finer-grained mapping through the status category:
| Front status | Modem state |
|---|---|
| Unassigned, assigned, or open | Open |
| Waiting (ticket status category) | Waiting |
| Archived, or resolved (ticket status category) | Done |
A deleted conversation, or one with a status Modem doesn’t recognize, keeps its last known state rather than being guessed at.
Authors
Customers are captured with the name and address they wrote from and, when Front has linked the message to a contact, that contact’s identity, so the same person is recognized across conversations and resolves to Modem people. Your teammates are captured with their Front email addresses, so replies link to existing team members instead of creating duplicates. Front’s automated identities (rules, AI, API and integration senders, bulk replies, and similar) are flagged as bots.
Historical Backfill
Connecting requests a one-time import of your recent history automatically: conversations started in the last 90 days, up to 2,500 conversations, along with their messages and comments. The window is measured from when a conversation was created, not when it was last active, so a long-running thread opened before the window isn’t included even if it received a reply yesterday. It runs in the background and doesn’t block real-time capture.
Front’s API is rate-limited, so a busy company can take a while to finish. The backfill runs once per connection; reconnecting the same company later doesn’t run it again.
Analyzing Front Conversations
Once conversations are flowing, ask the Modem Agent about them from the web dashboard like any other source.
Troubleshooting
Authorization was rejected in Front
Only a Front admin can authorize the connection. A regular teammate’s attempt comes back as a rejected grant. Ask a Front admin to complete the authorization step.
Connected, but no conversations are appearing
Confirm the integration shows as connected in Settings → Integrations → Front, then allow a few minutes for webhook delivery and processing. Check that the conversation’s inbox is turned on under Choosing inboxes; private inboxes are off unless an admin turns them on. Recent history arrives through the backfill, which can take a while on a busy company.
The backfill seems incomplete
The backfill covers conversations started in the last 90 days, up to 2,500 conversations, so conversations that began before that window (even ones still active) and any beyond the cap aren’t imported. It runs once per connection. If it looks wrong, contact support@modem.ai.
New activity stopped arriving
If Front has revoked Modem’s access, for example after the app was removed from your Front company, new activity stops arriving but Settings → Integrations → Front still shows the connection as connected. Disconnect and reconnect from the same page. Reconnecting requires a Front admin.
Authors aren't linking to people
Authors are matched to Modem people by email address. A customer who wrote in over a channel without an email address, such as chat or SMS, is captured under the handle they used and won’t be linked to an existing profile automatically.
Disconnecting
To disconnect Front:
- Go to Settings → Integrations → Front
- Click Disconnect and confirm
Modem stops accepting deliveries for the company immediately and stops refreshing its stored credentials, though the disconnected connection record is retained. Nothing was created in your Front company when you connected, so there is nothing to clean up on the Front side; to revoke Modem’s access at the source, remove the Modem app from your Front company’s settings, which invalidates the tokens Modem holds. Historical data remains in Modem after disconnecting.