Front

Overview

The Front connector uses application webhooks, so events from the inboxes you choose reach Tessel as they happen. Each event includes the conversation, the message and the teammate involved, and Tessel links it to the run it starts.

Teams use it to tag inbound mail from Salesforce key accounts, to draft refund replies that wait for approval in Slack and to route billing questions based on the customer's Stripe plan.

Event coverage

• Inbound and outbound messages, including replies

• Tags added or removed, assignments and unassignments

• Comments and mentions, archives and reopens

How webhooks work

Tessel registers an application webhook, and Front signs every delivery with an X-Front-Signature header. Tessel checks the signature and the timestamp, then drops any event it has already seen by its ID.

{
  "type": "inbound",
  "id": "evt_5a1c2e9f",
  "emitted_at": 1759741021.34,
  "conversation": { "id": "cnv_y4tq81", "status": "unassigned" },
  "target": { "_meta": { "type": "message" } }
}

{
  "type": "inbound",
  "id": "evt_5a1c2e9f",
  "emitted_at": 1759741021.34,
  "conversation": { "id": "cnv_y4tq81", "status": "unassigned" },
  "target": { "_meta": { "type": "message" } }
}

{
  "type": "inbound",
  "id": "evt_5a1c2e9f",
  "emitted_at": 1759741021.34,
  "conversation": { "id": "cnv_y4tq81", "status": "unassigned" },
  "target": { "_meta": { "type": "message" } }
}

Rate limits

Front sets an API rate limit per company that depends on your plan, starting at 50 requests a minute. Tessel reads the X-RateLimit-Remaining header and queues writes, so a burst of replies never fails.

Permissions needed

Connect with OAuth as a Front admin. Tessel needs read access to the shared inboxes you pick. Write and send access is only used by the reply, tag, assign and comment actions.

• Read on shared resources for the inboxes you pick

• Write on shared resources for tags, assignments and comments

• Send only if workflows reply to customers