Skip to main content
Configure the source at AI Training → Data Sources. This is separate from the Front ticketing integration, though the same API token can power both.

Set up the sync

1

Open Data Sources

2

Add a Front source

Click Add source → Front.
FieldDefaultNotes
Start dateOne year agoEarliest article activity to include. Pick a date in YYYY-MM-DDTHH:mm format — the form provides a date picker.
API KeyFront API token with Knowledge Base: Read scope. Create one in the Front Developer Portal.
3

Select which Help Centers to sync

As soon as you paste a valid API key, OpenCX fetches the list of Help Centers on your Front account and shows them in a checkbox group with type (public / internal) and locale next to each name.
  • Leave all checked to sync every Help Center the token can read.
  • Uncheck internal Help Centers if you don’t want their articles in the AI index.
  • Use Select all / Deselect all for quick toggling.
Articles from unchecked Help Centers are filtered out at sync time (allowed_knowledge_base_ids saved to your source config). If you later re-check a Help Center, articles from it start syncing on the next run.
4

Start the sync

Click Connect. OpenCX saves your selection, creates the connection, and triggers the first sync. Progress shows on the source row.
5

Verify in AI Instructions

Open AI Training → AI Instructions. Articles appear grouped under Front. Confirm the eye icon matches expectations — internal Help Centers come in as internal, public as public (if published).

What gets synced

Each article is fetched twice internally: once for metadata (via Airbyte), then once more via the Front API to pull full content. The final record has title, body, and source URL.
Two layers combined:
  • KB type: If the Help Center’s type in Front is internal, every article from it is internal in OpenCX.
  • Article status: Within a non-internal Help Center, only published articles are public. Drafts and archived articles are internal.
Sync runs on the Airbyte schedule (typically every few hours). Only articles whose updated_at changed since the last run are fetched. New articles in selected Help Centers are picked up automatically.

Limits

Value
Streams syncedknowledge_bases_articles
Sync modeincremental_deduped_history on updated_at
Sync cadenceAirbyte polling — typically every few hours
Credential typeFront API token (no OAuth)
Multi-accountOne Front account per connection
Selective scopingPer-Help-Center via checkboxes. Articles are not filterable at category or team level below Help Center.
Archived / draft articlesSynced as internal

Front overview

Scope and per-HC scoping summary.

Troubleshooting

KB list empty, private articles, re-sync.

Front integration

Inbox, conversations, handoff.

Connect a knowledge source

All sources.