> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data-sources/business-apps/intercom.md).
# Intercom
Sync your contacts data (users and leads) from Intercom into your Jet app.
Using Intercom you can do the following:
* View your top Intercom customers alongside customer data stored in other data sources
* Share limited Intercom data with your team or external stakeholders
* Keep your account team alerted to users that are most active, or drifting away
Jet syncs the following Intercom data:
* Contacts
* Conversations
## 1. Get Intercom Access Token
Firstly, you need to sign up for [Intercom](https://www.intercom.com/) and create an account. Complete the account creation process to get started.
Intercom provides you with an Access Token as soon as you [create an app](https://app.intercom.com/a/developer-signup) on your workspace. You can find your Access Token in the **Configure > Authentication** section in your app within the [Developer Hub](https://app.intercom.io/a/apps/_/developer-hub/app-packages).
Copy your Access Token to connect Intercom to Jet Admin.
### 2. Add to Jet Admin
Add Intercom to an existing project or connect Intercom as a resource when creating a new project. Copy your Access Token into AccessToken field to connect the resource.
---
# 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.jetadmin.io/user-guide/data-sources/business-apps/intercom.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.
