Front integration

What it does

The Front integration lets your agency run a client's shared inbox from inside TaskJuice. Connect a client's Front company once and you can work across conversations, contacts, accounts, tags, inboxes, teammates, message templates, and the knowledge base. Nineteen webhook triggers cover the inbox lifecycle, so activity in Front can drive the rest of your workflow.

Coverage is measured against Front's published Core API specification rather than against what other automation tools expose. TaskJuice ships 227 actions covering every operation in that specification except eighteen, each of which is excluded for a documented reason: eleven are deprecated by Front, five return raw file bytes rather than JSON, one is restricted to custom channels, and one needs a token feature Front does not offer to OAuth apps.

Connect a Front account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Front and click Connect.
3. Sign in to the Front company that should authorize the connection and approve the scopes configured on the TaskJuice OAuth app in the Front Developer Portal.
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

Front access tokens last 60 minutes and TaskJuice refreshes them in the background using the refresh token issued at grant time. Refresh tokens are valid for six months, and Front issues a replacement during the final 24 hours of validity. To revoke access, open Front, navigate to Settings, then Integrations, and remove TaskJuice. See the Front OAuth setup guide for the full grant flow and scope configuration.

Triggers

Front delivers webhooks on two separate lanes, and they do not share a wire contract. TaskJuice supports both and verifies each with the signature scheme that lane actually uses.

• Rule webhooks are the lane you configure yourself inside a Front rule. Front signs them with a base64 HMAC-SHA1 digest of the raw body under the company API secret.
• Application webhooks fan every installing company into one endpoint. Front signs them with a base64 HMAC-SHA256 digest of the request timestamp, a colon, and the raw body, under the application signing key.

Front publishes no API for creating or deleting webhook subscriptions, so the subscription itself is created by hand in Front and pointed at the TaskJuice ingress URL.

Conversation lifecycle:

• front/inbound-message-received fires on a new inbound message.
• front/outbound-message-sent fires when a teammate sends an outbound message.
• front/conversation-assigned fires when a conversation is assigned to a teammate.
• front/conversation-archived, front/conversation-reopened, front/conversation-moved, front/conversation-deleted, front/conversation-restored follow the rest of the conversation lifecycle.
• front/conversation-snoozed and front/conversation-snooze-expired cover reminders.
• front/message-delivery-failed fires when Front cannot deliver an outbound message.

Tags, links, comments and contacts:

• front/tag-added and front/tag-removed fire when a tag changes on a conversation.
• front/link-added and front/link-removed fire when a link is attached or detached.
• front/comment-added fires on an internal comment.
• front/contact-created fires when a new contact is created.

Generic:

• front/rule-event exposes any Front rule delivery, for event types without a dedicated trigger.

The legacy front/conversation-created trigger is retained so existing workflows keep resolving, but Front emits no such event and it can never fire. Use front/inbound-message-received instead.

Actions

Actions are grouped by the resource they operate on. Every list action pages over the full URL Front returns in _pagination.next.

• Conversations (27) list, search, fetch, create, update, assign, tag, comment, follow, and inspect events, drafts, inboxes and messages.
• Contacts (27) full contact lifecycle plus handles, notes, custom fields, conversations, and per-team and per-teammate scoping.
• Teammates (30) fetch and update teammates, and read their channels, inboxes, rules, shifts, signatures, tags, templates and assigned conversations.
• Knowledge base (25) create and update knowledge bases, articles and categories, including localized content in a specified locale.
• Inboxes (16) create and fetch inboxes, manage access, and list channels and conversations.
• Teams (14) read teams and manage their inboxes, tags, templates, views, contacts and membership.
• Tags (13) full tag hierarchy including child tags and tagged conversations.
• Messages and templates (10) fetch messages, seen receipts, and manage message templates.
• Channels (7), template folders (7), accounts (6), comments (5), links (5), drafts (4), analytics (4), shifts (4), time off (4), rules (3), signatures (3), views (3), ticket statuses (2) and events (2) round out the surface.

Known limitations

• Front enforces a per-company rate limit that varies by plan. When the budget is exhausted Front returns a 429 status with a Retry-After header, which TaskJuice surfaces as a retryable error so downstream resilience policies can back off.
• Shifts are gated by plan. On a company whose plan does not include shifts, every shift endpoint returns 403 with the message Your plan does not give you access to shifts.
• Front publishes no endpoint that lists knowledge base categories across all knowledge bases. Actions that address a category directly take the category ID as free text. The four actions that create content inside a knowledge base offer a category picker, because they carry the parent knowledge base ID.
• Attachment downloads are not available as actions. Those endpoints return raw file bytes rather than JSON.
• Creating a link accepts either an external URL or a pattern, never both. Sending both returns a 400.