> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/integrations/front.md).
# Front
Support conversations say things about an account that no property captures. Connecting Front syncs its conversations into Zero as issues, linked to the right companies and contacts, so they sit alongside the rest of the record.
## How to connect Front to Zero
Only workspace admins can connect or disconnect issue tracker integrations.
{% stepper %}
{% step %}
In [Front Developer settings](https://app.frontapp.com/settings/developers), create a new API token with the **Shared Resources** scope and copy it.
{% endstep %}
{% step %}
In Zero, go to **Settings → Connections → Integrations**. Scroll to **Issue Tracker integrations** and click **Connect Issue Tracker**.
{% endstep %}
{% step %}
Select **Front**, paste the token into the **Issue Tracker API Key** field, and click **Connect Integration**.
{% endstep %}
{% endstepper %}
The first sync starts immediately after connecting and pulls conversations from the **last 90 days**. After that, the integration updates **hourly**; the connected card shows the sync status and the last update time. You can also trigger a sync manually from the card's **⋯ menu → Sync data**.
## What gets synced
Each Front conversation becomes an issue in Zero:
* **Name** — the conversation subject; falls back to the last message preview, then "Conversation with \".
* **Status** — with Front ticketing enabled, open conversations sync as **Todo**, waiting conversations as **Waiting on customer**, and resolved conversations as done. For classic conversations, archived conversations sync as done, snoozed conversations stay snoozed, and deleted conversations are canceled.
* **Labels** — Front conversation tags. Tag changes are picked up on later syncs, even without new activity on the conversation.
* **Messages** — the conversation transcript as plain text (the most recent 100 messages), in chronological order.
* **Link** — a deep link that opens the conversation in Front.
Response and resolution times are not tracked for Front conversations.
## How issues are matched to companies and contacts
Zero uses the conversation's main recipient to link each issue:
* For email channels, the recipient handle is the person's **email address**. For Front Chat and social channels, the handle is opaque, so Zero resolves the email from the linked Front contact instead.
* The email is matched (case-insensitively) against contact emails in your workspace.
* The **email domain** is matched against company domains. For free-mail senders, the matched contact's company is used instead.
* The source email is stored on the issue, so conversations are linked retroactively when a matching contact is created later. Associations are re-checked on every sync.
## Where the data appears in Zero
In any company list, add the properties related to **Issues** — for example **Issues**, **Open issues**, **Closed issues**, and **Issues by month**. These fields are shared with the other issue trackers (Linear, Pylon, Plain, Intercom). Click an issue to preview the conversation and open it in Front. You can also use **Issues** as an entity in [**Reports**](/features/reports.md) to chart the data and pin it to dashboards.
## Disconnecting
Open the connected card's **⋯ menu → Disconnect**. Disconnecting stops the sync and removes the synced issue data from Zero.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.zero.inc/settings/integrations/front.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
