Quick start

From the Teamspace where you want data to land, go to Settings → Integrations → Front → Connect, paste your Front API token, then create a subscription to auto-import new Front tickets/conversations as Highlights in this Teamspace. (Front supports API tokens and OAuth; tokens are simplest for server-to-server auth.)

Why integrate with Front?

Each source adds a new dimension of customer truth. Front contributes the support/inbox perspective—email, chat, and social conversations—that complements sales calls, meeting recordings, reviews, and surveys already in NEXT AI. Bringing these streams together builds a richer customer-intelligence graph so teams prioritize the right work with evidence attached.

What gets imported

Object in NEXT AI: Highlight (short-form signal) in the Teamspace where you configure the subscription.
Included fields (when available): subject/title (or first line), latest message text, requester/contact, assignee/teammate, status (open/archived/spam/trashed), tags/labels, timestamps, and a source link to the Front conversation. (In Front, a conversation is a thread of messages across an inbox.)
Dedupe: handled by Front object IDs behind the scenes.

Connect Front

Create or locate an API token in Front
Front company admins can create a token in Settings → Developers → API tokens, then Reveal/Copy it for use in Core API requests.
Paste the token in NEXT AI
In the target Teamspace, open Settings → Integrations → Front → Connect, paste the API token, then Save. (Bearer token auth.)

Tip: For private inboxes, ensure the token has the scope required to read private resources; otherwise some conversations won’t import.

Auto-import support tickets/conversations

Create a subscription that watches for new Front conversations/tickets and creates a Highlight for each new item in this Teamspace.

Scope: target the inboxes/segments you care about first (e.g., Support, Success).
Freshness: subscriptions capture new or recently changed items; use a short backfill window if offered.
Event-driven option (advanced): Front also supports webhooks (rule-based or app webhooks) for push delivery if your architecture prefers events.

Tips

Route by status and tags: use status (open/archived) and tags from Front to auto-label Highlights for triage.
Manage volume: if you’re importing from multiple busy inboxes, start with one and expand; Front’s Core API enforces per-company rate limits (50/100/200 requests/min depending on plan).
Keep the source link: the Front link lets product/CX validate context or reply in-thread before acting.

Troubleshooting

401/403 on connect: verify the API token is active and has scopes to read the targeted inboxes (private inboxes require additional permission).
Delays or 429s: respect rate limits (Starter 50 rpm, Professional 100 rpm, Enterprise 200 rpm); add backoff or stagger backfills. Recent platform updates improved limiter behavior (429s no longer count against your quota).
We prefer push over polling: configure Front webhooks via Rules or an App so new events POST to your endpoint; your subscription in NEXT AI can align with that flow.

FAQ

Q: What exactly is created in NEXT AI from Front?

Highlights—one per new conversation/ticket—with text, requester/assignee, status, tags, timestamps, and a source link to the Front thread.

Q: Do we authenticate with OAuth or a token?

NEXT AI supports API tokens (simple Bearer auth). Front also offers OAuth if your security policy prefers it; both yield a Bearer token for Core API access.