# Front (v2)
Information note **Front is supported by the Singer community**
This integration is powered by [Singer's](https://www.singer.io/) FrontApp tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-frontapp) or [join the Singer Slack](https://singer-slackin.herokuapp.com/).
## Front integration summary
Stitch’s Front integration replicates data using the [Front API](https://dev.frontapp.com/). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/front/v2#schema) section for a list of objects available for replication.
## Front feature snapshot
A high-level look at Stitch's Front (v2) integration, including release status, useful links, and the features supported in Stitch.
| **STITCH** | | | |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Deprecated on June 22, 2026 | **Supported by**
the Info icon
Indicates if the integration is supported by Stitch or the Singer community. | [Singer Community](https://www.singer.io/) |
| **Stitch plan**
the Info icon
The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**
the Info icon
Indicates if the integration is available as a source in Stitch Connect. | the Remove icon
This version of the integration isn't available via the API.
Not available |
| **Singer GitHub repository** | [singer-io/tap-frontapp](https://github.com/singer-io/tap-frontapp) | | |
| **REPLICATION SETTINGS** | | | |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**
the Info icon
A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon
This feature is supported for this version of the integration.
Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**
the Info icon
A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon
This feature is supported for this version of the integration.
Supported |
| **Table-level reset**
the Info icon
Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon
Table-level resets are not supported for this integration. Resets are only supported at the integration level.
Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**
the Info icon
Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon
Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.
Unsupported |
| **DATA SELECTION** | | | |
| **Table selection**
the Info icon
The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported | **Column selection**
the Info icon
The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported |
| **Select all**
the Info icon
Indicates if the integration supports selecting all available tables and columns. | the Success icon
Supported
Supported | | |
| **TRANSPARENCY** | | | |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**
the Info icon
Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**
the Info icon
Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported |
## Connecting Front
### Front setup requirements
To set up Front in Stitch, you need:
* **A Premium or Enterprise Front plan**. These plans include API access, which is required to use Stitch’s Front integration. Refer to [Front’s pricing page for more info](https://frontapp.com/pricing).
### Step 1: Generate a Front API token
The New API token page in FrontThe New API token page in Front
1. Sign into your [Front account](https://app.frontapp.com/).
2. Click the user menu (your icon) in the top left corner of the page.
3. Click **Settings**.
4. In the **Company** section on the left side of the page, click **Plugins & API**.
5. On the page that displays, click **API**.
6. Click the **New Token** button.
7. On the **New Token** page, click the **Select Scopes** dropdown and select the type of resources you want to replicate data from.
8. Click **Create** to create the API token.
Keep the token handy - you’ll need it in the next step to complete the setup.
### Step 2: Add Front as a Stitch data source
1. [Sign into your Stitch account](https://app.stitchdata.com/).
2. On the Stitch Dashboard page, click the **Add Integration** button.
3. Click the **Front** icon.
4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Front” would create a schema called `stitch_front` in the destination. **Note**: Schema names cannot be changed after you save the integration.
5. In the **API Token** field, paste the Front API token you generated in [Step 1](https://help.qlik.com/en-US/stitch/integrations/saas/front/v2#generate-front-api-token).
### Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Front integration. This means that data **equal to or newer than this date** will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Front’s default setting of **1 year**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.
### Step 4: Create a replication schedule
Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.
In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Front integrations support the following replication scheduling methods:
* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)
* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)
* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.
### Step 5: Set objects to replicate
Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).
The last step is to select the tables and columns you want to replicate. [Learn about the available tables for this integration.](https://help.qlik.com/en-US/stitch/integrations/saas/front/v2#schema)
**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.
* Selection options
* Individual tables and columns
* All tables and columns
For Front integrations, you can select:
1. **Individual tables and columns**
2. **All tables and columns**
Click the tabs to view instructions for each selection method.
1. In the integration’s **Tables to Replicate tab**, locate a table you want to replicate.
2. To track a table, click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.
3. To track a column, click the **checkbox** next to the column’s name. A blue checkmark means the column is set to replicate.
4. Repeat this process for all the tables and columns you want to replicate.
5. When finished, click the **Finalize Your Selections** button at the bottom of the screen to save your selections.
Information note **Important**: Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections. Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.
1. Click into the integration from the Stitch Dashboard page.
2. Click the **Tables to Replicate** tab.
3. In the list of tables, click the box next to the **Table Names** column.
4. In the menu that displays, click **Track all Tables and Fields**:
The Track all Tables and Fields menu in the Tables to Replicate tabThe Track all Tables and Fields menu in the Tables to Replicate tab
5. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.
### Initial and historical replication jobs
After you finish setting up Front, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**
Information note
**Initial replication jobs with Anchor Scheduling**
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.
#### Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.
## Front table reference
Information note
**Schemas and versioning**
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for **version 2** of this integration.
Information note
**Table and column names in your destination**
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.
### accounts\_table
The `accounts_table` table contains data about accounts in your Front account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | report\_id |
| **Replication Keys ** | analytics\_date
analytics\_range |
| **Useful links** | [Front documentation](https://dev.frontapp.com/reference/analytics "Opens in new tab: Front documentation")
[accounts_table schema on GitHub](https://github.com/singer-io/tap-frontapp/blob/master/tap_frontapp/schemas/accounts_table.json "Opens in new tab: accounts_table schema on GitHub") |
accounts\_table table schema
| **analytics\_date**
STRING |
| --- |
| **analytics\_range**
STRING |
| **avg\_first\_response\_time**
NUMBER |
| **avg\_handle\_time**
NUMBER |
| **avg\_response\_time**
NUMBER |
| **avg\_sla\_breach\_time**
NUMBER |
| **avg\_total\_reply\_time**
NUMBER |
| **metric\_description**
STRING |
| **metric\_id**
STRING |
| **new\_segments\_count**
NUMBER |
| **num\_active\_segments\_full**
NUMBER |
| **num\_archived\_segments**
NUMBER |
| **num\_archived\_segments\_with\_reply**
NUMBER |
| **num\_closed\_segments**
NUMBER |
| **num\_csat\_survey\_response**
NUMBER |
| **num\_messages\_received**
NUMBER |
| **num\_messages\_sent**
NUMBER |
| **num\_open\_segments\_end**
NUMBER |
| **num\_open\_segments\_start**
NUMBER |
| **num\_sla\_breach**
NUMBER |
| **num\_workload\_segments**
NUMBER |
| **pct\_csat\_survey\_satisfaction**
NUMBER |
| **pct\_tagged\_conversations**
NUMBER |
| **report\_id**
STRING |
### channels\_table
The `channels_table` table contains data about channels in your Front account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | report\_id |
| **Replication Keys ** | analytics\_date
analytics\_range |
| **Useful links** | [Front documentation](https://dev.frontapp.com/reference/analytics "Opens in new tab: Front documentation")
[channels_table schema on GitHub](https://github.com/singer-io/tap-frontapp/blob/master/tap_frontapp/schemas/channels_table.json "Opens in new tab: channels_table schema on GitHub") |
channels\_table table schema
| **analytics\_date**
STRING |
| --- |
| **analytics\_range**
STRING |
| **avg\_first\_response\_time**
NUMBER |
| **avg\_handle\_time**
NUMBER |
| **avg\_response\_time**
NUMBER |
| **avg\_sla\_breach\_time**
NUMBER |
| **avg\_total\_reply\_time**
NUMBER |
| **metric\_description**
STRING |
| **metric\_id**
STRING |
| **new\_segments\_count**
NUMBER |
| **num\_active\_segments\_full**
NUMBER |
| **num\_archived\_segments**
NUMBER |
| **num\_archived\_segments\_with\_reply**
NUMBER |
| **num\_closed\_segments**
NUMBER |
| **num\_csat\_survey\_response**
NUMBER |
| **num\_messages\_received**
NUMBER |
| **num\_messages\_sent**
NUMBER |
| **num\_open\_segments\_end**
NUMBER |
| **num\_open\_segments\_start**
NUMBER |
| **num\_sla\_breach**
NUMBER |
| **num\_workload\_segments**
NUMBER |
| **pct\_csat\_survey\_satisfaction**
NUMBER |
| **pct\_tagged\_conversations**
NUMBER |
| **report\_id**
STRING |
### inboxes\_table
The `inboxes_table` table contains data about inboxes in your Front account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | report\_id |
| **Replication Keys ** | analytics\_date
analytics\_range |
| **Useful links** | [Front documentation](https://dev.frontapp.com/reference/analytics "Opens in new tab: Front documentation")
[inboxes_table schema on GitHub](https://github.com/singer-io/tap-frontapp/blob/master/tap_frontapp/schemas/inboxes_table.json "Opens in new tab: inboxes_table schema on GitHub") |
inboxes\_table table schema
| **analytics\_date**
STRING |
| --- |
| **analytics\_range**
STRING |
| **avg\_first\_response\_time**
NUMBER |
| **avg\_handle\_time**
NUMBER |
| **avg\_response\_time**
NUMBER |
| **avg\_sla\_breach\_time**
NUMBER |
| **avg\_total\_reply\_time**
NUMBER |
| **metric\_description**
STRING |
| **metric\_id**
STRING |
| **new\_segments\_count**
NUMBER |
| **num\_active\_segments\_full**
NUMBER |
| **num\_archived\_segments**
NUMBER |
| **num\_archived\_segments\_with\_reply**
NUMBER |
| **num\_closed\_segments**
NUMBER |
| **num\_csat\_survey\_response**
NUMBER |
| **num\_messages\_received**
NUMBER |
| **num\_messages\_sent**
NUMBER |
| **num\_open\_segments\_end**
NUMBER |
| **num\_open\_segments\_start**
NUMBER |
| **num\_sla\_breach**
NUMBER |
| **num\_workload\_segments**
NUMBER |
| **pct\_csat\_survey\_satisfaction**
NUMBER |
| **pct\_tagged\_conversations**
NUMBER |
| **report\_id**
STRING |
### tags\_table
The `tags_table` table contains a list of tag statistics since the last completed replication job through the most recent iteration of the defined [**Incremental Range**](https://help.qlik.com/en-US/stitch/integrations/saas/front/v2#add-stitch-data-source) (day or hour). This table will include tags in your Front account. **Note**: During the historical replication job, all increments (defined using the **Incremental Range** setting) since the **Start Date** will be replicated. This will result in the first record for this table being an aggregated record across all tags.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | report\_id |
| **Replication Keys ** | analytics\_date
analytics\_range |
| **Useful links** | [Front documentation](https://dev.frontapp.com/reference/analytics "Opens in new tab: Front documentation")
[tags_table schema on GitHub](https://github.com/singer-io/tap-frontapp/blob/master/tap_frontapp/schemas/tags_table.json "Opens in new tab: tags_table schema on GitHub") |
tags\_table table schema
| **analytics\_date**
STRING |
| --- |
| **analytics\_range**
STRING |
| **avg\_first\_response\_time**
NUMBER |
| **avg\_handle\_time**
NUMBER |
| **avg\_response\_time**
NUMBER |
| **avg\_sla\_breach\_time**
NUMBER |
| **avg\_total\_reply\_time**
NUMBER |
| **metric\_description**
STRING |
| **metric\_id**
STRING |
| **new\_segments\_count**
NUMBER |
| **num\_active\_segments\_full**
NUMBER |
| **num\_archived\_segments**
NUMBER |
| **num\_archived\_segments\_with\_reply**
NUMBER |
| **num\_closed\_segments**
NUMBER |
| **num\_csat\_survey\_response**
NUMBER |
| **num\_messages\_received**
NUMBER |
| **num\_messages\_sent**
NUMBER |
| **num\_open\_segments\_end**
NUMBER |
| **num\_open\_segments\_start**
NUMBER |
| **num\_sla\_breach**
NUMBER |
| **num\_workload\_segments**
NUMBER |
| **pct\_csat\_survey\_satisfaction**
NUMBER |
| **pct\_tagged\_conversations**
NUMBER |
| **report\_id**
STRING |
### teammates\_table
The `teammates_table` table contains data about teammates in your Front account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | report\_id |
| **Replication Keys ** | analytics\_date
analytics\_range |
| **Useful links** | [Front documentation](https://dev.frontapp.com/reference/analytics "Opens in new tab: Front documentation")
[teammates_table schema on GitHub](https://github.com/singer-io/tap-frontapp/blob/master/tap_frontapp/schemas/teammates_table.json "Opens in new tab: teammates_table schema on GitHub") |
teammates\_table table schema
| **analytics\_date**
STRING |
| --- |
| **analytics\_range**
STRING |
| **avg\_first\_response\_time**
NUMBER |
| **avg\_handle\_time**
NUMBER |
| **avg\_response\_time**
NUMBER |
| **avg\_sla\_breach\_time**
NUMBER |
| **avg\_total\_reply\_time**
NUMBER |
| **metric\_description**
STRING |
| **metric\_id**
STRING |
| **new\_segments\_count**
NUMBER |
| **num\_active\_segments\_full**
NUMBER |
| **num\_archived\_segments**
NUMBER |
| **num\_archived\_segments\_with\_reply**
NUMBER |
| **num\_closed\_segments**
NUMBER |
| **num\_csat\_survey\_response**
NUMBER |
| **num\_messages\_received**
NUMBER |
| **num\_messages\_sent**
NUMBER |
| **num\_open\_segments\_end**
NUMBER |
| **num\_open\_segments\_start**
NUMBER |
| **num\_sla\_breach**
NUMBER |
| **num\_workload\_segments**
NUMBER |
| **pct\_csat\_survey\_satisfaction**
NUMBER |
| **pct\_tagged\_conversations**
NUMBER |
| **report\_id**
STRING |
### teams\_table
The `teams_table` table contains data about teams in your Front account.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | report\_id |
| **Replication Keys ** | analytics\_date
analytics\_range |
| **Useful links** | [Front documentation](https://dev.frontapp.com/reference/analytics "Opens in new tab: Front documentation")
[teams_table schema on GitHub](https://github.com/singer-io/tap-frontapp/blob/master/tap_frontapp/schemas/teams_table.json "Opens in new tab: teams_table schema on GitHub") |
teams\_table table schema
| **analytics\_date**
STRING |
| --- |
| **analytics\_range**
STRING |
| **avg\_first\_response\_time**
NUMBER |
| **avg\_handle\_time**
NUMBER |
| **avg\_response\_time**
NUMBER |
| **avg\_sla\_breach\_time**
NUMBER |
| **avg\_total\_reply\_time**
NUMBER |
| **metric\_description**
STRING |
| **metric\_id**
STRING |
| **new\_segments\_count**
NUMBER |
| **num\_active\_segments\_full**
NUMBER |
| **num\_archived\_segments**
NUMBER |
| **num\_archived\_segments\_with\_reply**
NUMBER |
| **num\_closed\_segments**
NUMBER |
| **num\_csat\_survey\_response**
NUMBER |
| **num\_messages\_received**
NUMBER |
| **num\_messages\_sent**
NUMBER |
| **num\_open\_segments\_end**
NUMBER |
| **num\_open\_segments\_start**
NUMBER |
| **num\_sla\_breach**
NUMBER |
| **num\_workload\_segments**
NUMBER |
| **pct\_csat\_survey\_satisfaction**
NUMBER |
| **pct\_tagged\_conversations**
NUMBER |
| **report\_id**
STRING |