Front is where many client-facing teams handle the day-to-day: shared inboxes that bring email, SMS, chat, and social conversations in one place. Every reply sent, comment left, and conversation moved is a signal of how accounts are actually being managed. 

WorkSights connects to Front and brings that activity into a continuous timeline, so the conversations your team is already having show up alongside the rest of your work without anyone changing how they use Front.

WorkSights only receives activity from shared inboxes. Conversations in private inboxes are not delivered by Front and will not appear in WorkSights. There is also no historical backfill: only conversations and events from the point of connection forward are captured.

For connection steps, see Front Setup.

How Front Activity Appears

WorkSights receives Front events in real time via webhooks. Every action your team takes in Front, whether sending a reply, leaving a comment, or moving a conversation, is delivered to the timeline as a structured activity.

All activity from the same conversation is grouped under a single object on the timeline, tit;ed with the conversation in Front. This makes it easy to follow a client thread from the first inbound message through resolution, regardless of how many teammates touched it.

Activities are attributed to the teammate who acted. Outbound messages and comments are attributed to their author. Inbound messages and ticket actions are attributed to the conversation’s assignee. Front teammates are matched to WorkSights users by email address, and only matched users have activity attributed to them on the timeline.

What WorkSights Receives

WorkSights captures three types of activity from your shared Front inboxes.

Messages

Inbound messages from clients appear as New message in “{subject}” in the Email (Inbox) category. Outbound replies sent by teammates appear as Replied in “{subject}” in the Email (Send) category. The activity detail includes a short message preview.

Comments and Mentions

Internal comments and mentions on a conversation appear as Commented on “{subject}” or Mentioned in “{subject}” in the General category, the same category used for comments from tools like Notion and ClickUp.

Workflow Actions

Conversation workflow events appear in the Ticket category. WorkSights receives assignment changes, archive and reopen events, conversation moves between inboxes, snooze and snooze-expiry events, and tag and link additions. Each appears with a descriptive title, for example Archived “{subject}”, Assignment changed on “{subject}”, or Tagged “{subject}”.

Integration Page Overview

The Front integration page contains three tabs:

• Overview: connection owner, status, subscribed user count, remote user mapping count, created and last modified dates. Also shows a Connections summary panel with each connected Front company, its owner, remote user count, and a Re-import action.
• Users: all Front teammates and their mapped WorkSights user, subscription status, and last processed date. Users can be mapped manually if email addresses do not match between systems.
• Connections: connected Front workspaces with connection ID, owner, created and last updated dates, status, remote user count, and Re-import and Refresh actions.

Data Access and Privacy

WorkSights connects to Front using OAuth 2.0. No Front credentials are stored. The connection is read-only: WorkSights receives webhook events delivered by Front but cannot send messages, modify conversations, or take any action inside Front.

WorkSights captures structured activity data: who did what, on which conversation, and when. Message and comment previews are included for context, but full message bodies and attachments are not stored.

Connection removal is handled by the WorkSights team. Contact us via in-app chat if you need a connection removed.

Troubleshooting

No activities appearing after connecting

• WorkSights does not backfill historical Front conversations. The timeline will be empty until your team takes action in Front after connecting.
• Confirm that your conversations are in a shared inbox. Activity in private inboxes is never delivered to connected apps by Front.
• Check the Users tab on the Front integration page and confirm your teammates are mapped to WorkSights users. Activity is only attributed to matched users.

Activity attributed to the wrong teammate, or not appearing for a known sender

• Open the Users tab and confirm teammates are mapped to WorkSights users by email. Front teammates whose email does not match a WorkSights user will not have activity attributed to them.
• Outbound messages and comments are attributed to the author. Inbound messages and ticket actions are attributed to the conversation’s assignee. If a conversation has no assignee, those events will not create user-attributed activity.

Related Guides

Front Setup