Front

This connector uses the Front Core API (dev.frontapp.com/reference).

Setup:

1. Sign in to Front → Settings (top-right) → Developers → API Tokens → Create API Token.
2. Pick scope: private (full-access to all inboxes/conversations) or scoped to a specific inbox/role.
3. Copy the token. Set FRONT_API_TOKEN.

Authentication: Authorization: Bearer ${FRONT_API_TOKEN}.

Front's tile model:

• Conversation = a thread between your team and one or more contacts. Has status (open/archived/spam/deleted), assignee, inbox, tags.
• Message = each inbound/outbound email, SMS, chat, etc. within a conversation.
• Contact = an external entity (a customer). Has handles[] of various types (email, phone, twitter, custom).
• Inbox = a shared mailbox (could map to an email address, a Slack channel, an SMS number).
• Teammate = a Front user.

Sending replies: a 'reply' is a new message in an existing conversation. POST /conversations/{id}/messages (the adapter wraps as front_send_reply). For new outbound conversations, POST /channels/{id}/messages (different endpoint).

Pagination: cursor-based via ?limit=N&page_token=.... Response includes _pagination.next URL.

Tagged dates: dates on objects come as Unix timestamps (seconds, NOT ms).

Resource references: many fields are URLs like https://api2.frontapp.com/contacts/cnt_xxx instead of plain IDs — extract the ID after the last / if you need a bare ID, or just pass the URL back to Front in subsequent calls (Front accepts both).

Rate limits: ~50 req/sec per token (varies). On 429 honor headers.

Out of scope here: rules/automation, analytics endpoints, custom-channel creation, signature management, knowledge-base.