Front integration

What it does

The Front integration lets your agency run shared-inbox operations on behalf of your clients without leaving TaskJuice. Connect a client's Front company once and you can list and fetch conversations, send replies into a thread, list and create contacts, and list the inboxes the connection can see. Three webhook triggers fire when a conversation is created, a conversation is assigned to a teammate, or a new contact is created, so you can chain inbox activity into the rest of your workflow.

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 are short-lived; TaskJuice automatically refreshes them in the background using the refresh token issued at grant time. 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/conversation-created fires when a new conversation is created in the Front company. The activation payload carries the Front event envelope with the conversation under payload.conversation.
• front/conversation-assigned fires when a Front conversation is assigned to a teammate. The activation payload includes the assignee under payload.target.data.
• front/contact-created fires when a new contact is created in the Front company. The activation payload carries the contact under payload.contact.

Front signs every webhook with an HMAC-SHA256 base64 digest of the raw body on the X-Front-Signature header. TaskJuice verifies the signature against the OAuth app's API secret before activating the workflow. Configure the Front Rule (or App Channel) that posts to the TaskJuice ingress URL to subscribe to the relevant event types.

Actions

• front/list-conversations lists conversations across the company with cursor pagination over _pagination.next and optional Front search syntax via the q query parameter.
• front/get-conversation fetches a single conversation by its Front ID (prefixed cnv_).
• front/send-conversation-reply posts a reply (message or comment) on an existing conversation as the authenticated teammate or through a shared channel.
• front/list-contacts lists contacts in the connected company with cursor pagination over _pagination.next.
• front/create-contact creates a contact with one or more communication handles (email, phone, twitter, front_chat, etc.) and optional custom fields.
• front/list-inboxes lists every inbox the connection can see, including private inboxes the authorizing teammate has access to.

Known limitations

• Front enforces a per-company rate limit that varies by plan (see the Front Developer Portal for current ceilings). 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.
• Pagination follows the full URL returned in _pagination.next. List actions return one page per call along with the next-page URL, so workflows that need every page should drive paging explicitly.
• Webhook subscriptions are configured per event type via Front Rules (or App Channels). TaskJuice does not create rules automatically; configure the rule against the TaskJuice ingress URL.
• The integration uses OAuth on the company-level grant. Personal API tokens scoped to a single teammate are not supported.
• The send-conversation-reply action requires the authenticated teammate (or the supplied author_id) to have access to the conversation's inbox; Front rejects replies from teammates outside the inbox's team.