# Linking Front as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

Enter your Front API token to sync your Front data into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Front.
3.  Create an API token in your [Front settings](https://app.frontapp.com/settings/tools/api) under **Developers > API tokens**. Grant read scopes for the resources you want to sync (for example `shared_resources:read`, `contacts:read`, `tags:read`).
4.  Back in PostHog, paste the token in the **API token** field and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Front data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| events | Front events (only syncs the last 365 days on initial sync) | Incremental |
| contacts | Contacts | Full refresh |
| conversations | Conversations | Full refresh |
| accounts | Accounts | Full refresh |
| tags | Tags | Full refresh |
| teammates | Teammates | Full refresh |
| inboxes | Inboxes | Full refresh |
| channels | Channels | Full refresh |
| teams | Teams | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

The `events` table only syncs the last 365 days on its initial sync to avoid an unbounded backfill.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| API token | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| events | Only syncs the last 365 days on initial sync | Incremental, Full refresh | emitted_at | — |
| contacts | A person or company in Front's contact directory, with their handles across channels. | Full refresh | — | — |
| conversations | A thread of messages and comments in Front, the core unit of work in an inbox. | Full refresh | — | — |
| accounts | A company account in Front, grouping related contacts together. | Full refresh | — | — |
| tags | A label that can be applied to conversations to categorize them. | Full refresh | — | — |
| teammates | A user (teammate) in the Front workspace. | Full refresh | — | — |
| inboxes | A shared inbox that receives and organizes conversations. | Full refresh | — | — |
| channels | A communication channel (email, SMS, etc.) connected to an inbox. | Full refresh | — | — |
| teams | A team in the Front workspace that owns inboxes and teammates. | Full refresh | — | — |

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better