Reference · built on requestConnectorSupport & service desks

Front

Conversations, messages, comments, contacts, and events from Front's shared inbox through the Core API and webhooks.

Request accessPricing ↗

About

Front is a shared inbox for teams. It holds conversations and the messages inside them, comments between teammates, contacts, tags, inboxes, channels, and teammates. The Core API is served at api2.frontapp.com and records an event for each thing that happens to a conversation.

Through Fibric, an operator reads conversations and events as webhooks deliver them, checks the contact, and proposes a reply, a comment, an assignment, a tag, or a move to another inbox for your approval. Calls are paced to your plan's per-minute limit and burst allowance. What you approve is applied once and recorded with its reason and a way to undo it.

This is a reference listing. It documents what Fibric would read from Front and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Conversations, with assignee, inbox, status, and tags
  • Messages and attachments on a conversation, inbound and outbound
  • Comments and mentions between teammates
  • Contacts, tags, inboxes, channels, and teammates
  • Events such as inbound, outbound, assign, unassign, archive, reopen, comment, tag, untag, move, conversations_merged, and sending_error
  • Application webhooks, which deliver the full event payload and retry failed deliveries

Proposed actions

  • Target capability: propose a reply through POST /conversations/{conversation_id}/messages
  • Target capability: propose a new outbound message through POST /channels/{channel_id}/messages
  • Target capability: propose an assignee, inbox, status, or tag change through PATCH /conversations/{id}
  • Target capability: propose an internal comment through POST /conversations/{id}/comments

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Assemble an escalation

    When a conversation is tagged for escalation, the operator gathers the thread, comments, and contact, and proposes a comment with the summary and a reassignment.

    With Escalation Packet

  • Keep a lane for priority contacts

    The operator matches inbound messages to a list of priority contacts and proposes an assignment and tag before the message waits in the queue.

    With VIP Lane

  • Merge duplicate threads

    When the same contact starts two conversations, the operator proposes which one continues and a comment on the other, with both linked.

    With Thread Merge

  • Keep a callback promise

    The operator reads a reply that promises a callback and proposes a reminder and an assignment at the promised time.

    With Callback Promise

Requirements

  • A Front account; only an admin can create or manage API tokens
  • A token scoped to the right namespace: Global resources, Shared resources, or Private resources, with read, write, and send permissions as needed
  • An application webhook, or a rule webhook created in the inbox whose events you need
  • An HTTPS endpoint that receives POST requests carrying the event JSON
Authentication
An API token created by an admin under Settings > Developers > API Tokens, or OAuth2.0 for a public app.

Limits

  • Per-company rate limits by plan: 50 requests per minute on Starter, 100 on Professional, 200 on Enterprise
  • Burst allowance is half the plan limit and takes 10 minutes to replenish; analytics endpoints allow 1 request per 3 seconds
  • Rule webhooks do not carry retry guarantees; an event that fails to deliver may be missed
  • Mass actions, such as moving inbox content between teams or importing history, do not emit webhooks

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Front ↗

Questions and answers

What is the difference between application webhooks and rule webhooks?
Application webhooks are configured once for your app, always send the full event payload, and retry failed deliveries. Rule webhooks are created inside a rule and see only that rule's scope; a rule in a private inbox sees that inbox. They do not offer the same retry guarantees.
How are rate limits enforced?
Per company, not per token. The plan limit is 50, 100, or 200 requests per minute for Starter, Professional, and Enterprise. Responses carry x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, and burst headers. A 429 response includes retry-after in seconds.
Which events does Front record?
The reference lists assign, unassign, archive, reopen, trash, restore, comment, mention, inbound, outbound, move, forward, tag, untag, link_added, link_removed, sending_error, reminder, out_reply, conversations_merged, ticket_status_update, and a set of call events. Each event has a source and a target.
Ask about Front

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Front through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy