> ## Documentation Index > Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt > Use this file to discover all available pages before exploring further. # Connect your app to Intercom > Connect your app to Intercom, the customer messaging platform, to search and reply to conversations, manage contacts and tickets, and read help center articles. [Intercom](https://www.intercom.com/) is a customer messaging platform for support conversations, tickets, contacts, and a help center. The Intercom connector lets your Lovable app read and update one Intercom workspace. It's designed for teams that already support customers in Intercom and want that data in their own app. Intercom is available as an [app + chat connector](https://docs.lovable.dev/integrations/app-connectors.md): one shared connection that works in [Chats](https://docs.lovable.dev/features/chats.md), in the project chat while you build, and in your published apps. With Intercom, your app can: * Search and read conversations, then reply, add an internal note, or close, open, snooze, and assign them * Look up, create, and update contacts and companies, and attach notes and tags * Create and update support tickets, and read ticket types and states * Search help center articles and publish new ones * Read the admins and teams in the workspace Each connection uses one access token for one workspace. It's a good fit for a support inbox, a customer lookup page, or help center search inside your app. ## Common use cases and example apps These examples show what you can build with Intercom, each with a prompt to start from. | Example app | Example prompt | Description | | :- | :- | :- | | **Support inbox** | *Use Intercom and build an inbox that lists open conversations and lets a teammate reply.* | **Work the queue from one page.** The app searches open conversations and posts a reply or an internal note back to Intercom. | | **Contact form** | *Use Intercom and build a contact form that creates a support ticket when a visitor submits it.* | **Turn a website question into a ticket.** The app creates a ticket with the visitor's details and message, then shows the ticket as confirmation. | | **Customer conversation view** | *Use Intercom and build a page where a signed-in customer sees their open conversations and can add a reply.* | **Show each customer their own conversations.** The app must filter to that customer's email, because every request uses the same Intercom access token. | | **Customer lookup** | *Use Intercom and build a lookup page that finds a contact by email and shows their company and recent conversations.* | **See the customer before you reply.** The app searches contacts and companies and lists the conversations tied to that contact. | | **Help center search** | *Use Intercom and build a search box that answers common questions from help center articles.* | **Reuse the help center inside your app.** The app searches articles and links to the full article in Intercom. | | **Queue dashboard** | *Use Intercom and build a dashboard of open conversations by team, refreshed every ten minutes.* | **See the queue without refreshing it constantly.** The app reads a recent window of conversations, groups them by team, and caches the result. | ## How to connect Intercom Who can create Intercom connections depends on your plan and workspace settings. App + chat connectors are available by default. On Business and Enterprise plans, [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients) starts at **Admins**. Some Enterprise workspaces start at **No one**, which disables the connector. An admin or owner changes it in **Connectors → Admin settings → App + chat connectors**. You can create multiple Intercom connections using different access tokens, which is useful for separating workspaces (for example, a test workspace and production). When the connection is created, you can [link it to the projects](https://docs.lovable.dev/integrations/app-connectors.md#link-a-connection-to-a-project) where you want to use it. Anyone building in a project can ask Lovable in the project chat to link their project to it. Linking follows the connection's access rules. ### Prerequisites A private app is an Intercom app installed only on your workspace. Intercom gives that private app an access token. Before connecting Intercom, make sure you have: * An Intercom workspace, and access to its Developer Hub * The access token from a private app in that workspace * Permission to **create connections** in your Lovable workspace (see [Who can create connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-create-connections-and-clients)) > [!NOTE] > > All API requests made through this connector count toward your Intercom workspace's API rate limits. Billing and quota are handled directly by Intercom, not Lovable. ### Step 1: Get an Intercom access token An access token lets your Lovable app read and update one Intercom workspace. Intercom creates the token when you create a private app in the Developer Hub. To create an Intercom access token: **1. Open your Intercom workspace** Sign in to [Intercom](https://app.intercom.com/) and choose the region your workspace uses. The address shows the region: `app.intercom.com` for the United States, `app.eu.intercom.com` for Europe, and `app.au.intercom.com` for Australia. You select the same region in Lovable. **2. Create a private app** In Intercom, go to **Settings → Integrations → Developer Hub**. In **Your apps**, click **New app**. Name the private app, for example `Lovable`, select the workspace, and click **Create app**. Intercom installs the private app on that workspace and creates an access token. **3. Review the private app's permissions** Open **Configure → Authentication**. The access token is on that page. The token can only read and change what the private app's permissions allow. For the actions on this page, include read and write access for conversations, contacts, companies, tickets, and help center articles, and read access for admins. Intercom lists the permission names in [OAuth scopes](https://developers.intercom.com/docs/build-an-integration/learn-more/authentication/oauth-scopes). **4. Copy the token** Copy the access token and store it securely. > [!NOTE] > > The access token follows the conversation access of the teammate who creates the private app, or who last regenerates the token. Workspace admins set that under **Settings → Workspace → Teammates**. **All conversations** is the default. A narrower setting includes only the conversations that teammate can open. > [!WARNING] > > Your access token functions like a password. Keep it secure and never share it publicly. You'll need it in the next step. See Intercom's documentation for more: [Authentication](https://developers.intercom.com/docs/build-an-integration/learn-more/authentication). ### Step 2: Connect Intercom to Lovable Create the connection in Lovable with the access token from Step 1. **1. Open Intercom in Connectors** Open [Connectors](https://lovable.dev/dashboard?connectors) and select **Intercom**. For the other places to open the catalog from, see [Where to find connectors](https://docs.lovable.dev/integrations/introduction#where-to-find-connectors). **2. Add a connection** Click **Connect** on the connector page. The form is split into collapsible sections, **Details**, **Configure connection**, and **Sharing**. **3. Name the connection** Under **Details**, Lovable fills in a name for the connection, which you can change. The name is only used inside Lovable to identify the connection. **4. Configure the connection** Under **Configure connection**, enter: 1. **Data region**: the region where your Intercom workspace is hosted. **United States (api.intercom.io)** is selected by default. Select **Europe (api.eu.intercom.io)** for a workspace at `app.eu.intercom.com`, or **Australia (api.au.intercom.io)** for a workspace at `app.au.intercom.com`. 2. **Access token**: paste the private app access token. **5. Choose who can use this connection** Under **Sharing**, the connection is private to you by default and shows a **Private** label. To share it, click **Share with others**. Then add workspace members by email, or click **Invite entire workspace** to make the connection available to everyone in your Lovable workspace. Everyone you add can use this access token, including the conversations it can open. See [Who can use connections and clients](https://docs.lovable.dev/integrations/admin-controls.md#who-can-use-connections-and-clients) for more information. **6. Connect** Click **Connect** at the bottom of the form. Lovable verifies the access token against the Intercom API before saving the connection. The check calls Intercom in the data region you selected, so a region that does not match the workspace fails the check. When connected, anyone building in a project can ask Lovable in the project chat to link their project to Intercom. Linking follows the connection's access rules. Your Lovable apps can then search and reply to conversations, manage contacts, companies, and tickets, and read help center articles that the access token is allowed to use. ## Limitations The Intercom connector cannot: * Add the Intercom Messenger to your site. The connector reads and updates data in an Intercom workspace. Installing the Messenger is a separate setup in Intercom. * Subscribe your Lovable app to Intercom events. You can still add an endpoint in your Lovable app and point Intercom at that address. * Support per-end-user Intercom login. Each connection represents a single Intercom workspace shared across all projects linked to it. ## Troubleshooting Use these checks when connecting fails or an Intercom request returns an unexpected status. > [accordion] Enter a valid Intercom access token > > Lovable shows this on **Access token** before it calls Intercom. The token must be one string of 16 to 512 characters with no spaces. Copy it again from **Configure → Authentication** in the Developer Hub. > [accordion] Intercom did not validate your credentials. > > Intercom rejected the token when Lovable checked it. Click **Show error** to read Intercom's response. The usual causes are a token that was regenerated or revoked, or a **Data region** that does not match the workspace address. Copy the current token from **Configure → Authentication**, select the region that matches `app.intercom.com`, `app.eu.intercom.com`, or `app.au.intercom.com`, and try again. > > To replace the token on a connection you already saved, open the connection, paste the new token under **Configure connection**, and click **Update**. Regenerating the token under **Test & Publish → Your Workspaces** stops the previous token. > [accordion] Not authorized to access this conversation > > Intercom returns this 403 when the conversation sits outside the conversation access of the teammate who created the private app, or who last regenerates the token. A workspace admin widens that under **Settings → Workspace → Teammates**. **All conversations** reaches every conversation the private app's permissions allow. The change applies to the next request. > [accordion] Intercom returns 429 Too Many Requests > > Intercom is over the workspace limit. Private apps share 10,000 calls per minute, enforced in 10-second windows. Ask Lovable to read a shorter time range and cache it. ## Manage your Intercom connection Connections are managed from [**Connectors**](https://lovable.dev/dashboard?connectors): select **Intercom**, then open the connection. * **Unlink projects** to remove Intercom access from specific projects while keeping the connection available for others. See [Unlink projects from a connection](https://docs.lovable.dev/integrations/app-connectors.md#unlink-projects-from-a-connection) for the steps. * **Delete the connection** to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use Intercom stop working until a new connection is added. See [Delete a connection](https://docs.lovable.dev/integrations/app-connectors.md#delete-a-connection) for the steps and who can delete.