Dome Systems
Dashboard
DocsLearnHands-on LabsTemplatesHelpChangelogCLIAPIMCPSDKs

Ask questions about Intercom

A read-only managed agent for Intercom conversations and articles using a workspace access token.

User
Caller
  • chat
App
Agent
  • intercom-answerer
Governance
Gateway
  • intercom-readonly
Pool

intercom-answerer-pool

  • intercom-answerer-model
Tools

intercom

    What this template gives you

    • Interface

      A chat window, in your browser

      Use the included interface to send a request to this template.

    • Gateway

      intercom-readonly gateway

      This template sends its requests through intercom-readonly gateway, where its access rules and limits apply.

    • Model

      intercom-answerer-model

      This template uses intercom-answerer-model through the intercom-answerer-pool pool.

    Usage

    Hand this template to an AI agent to set up this template

    Node.js and npm to run npx.

    Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.

    Docker Compose to run the companion app locally.

    1. 1

      Create a workspace

      dome workspaces create --name <workspace-name>

      The CLI creates and selects a workspace context for you.

    2. 2

      Confirm the workspace context

      dome context list

      The workspace you just created is already selected.

    3. 3

      Pull the template

      npx @domesystems/templates pull dome-systems/ai-agent-for-intercom@0.1.0 --dir ai-agent-for-intercom

      Downloads this immutable release and verifies its digest.

    4. 4

      Run the template

      npx @domesystems/templates up --dir ai-agent-for-intercom

      Imports it into Dome and starts the companion app.

    Dome import variables

    npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.

    Required values

    • DOME_IMPORT_VAR_anthropic_api_key
    • DOME_IMPORT_VAR_intercom_bearer_token

    Setup guide

    Follow this template's setup guidance for agent variables and upstream connections.

    # Configure Intercom

- `anthropic_api_key`: enter the Anthropic key used by this agent's model.
- `intercom_bearer_token`: enter `Bearer ` followed by an Intercom workspace access token. Use a token with only the approved read permissions for the workspace this agent will inspect.

This template uses bearer-token authentication, not OAuth. It does not open a browser, require a callback URL, or require Intercom to allowlist Dome's OAuth callback.

Create or find the workspace token in **Intercom Developer Hub → Your Apps**. Open the private app that matches the workspace name—migrated workspaces may label it **Access Token App**—then open **Authentication** to reveal the access token and review its scopes. Intercom's [workspace access-token walkthrough](https://community.intercom.com/getting-started-with-intercom-43/api-how-to-set-up-an-access-bearer-token-a-k-a-find-workspace-access-token-7212) shows these steps; its [MCP guide](https://developers.intercom.com/docs/guides/mcp) documents the bearer-token header and permissions.

Store the raw token only in Dome's secret input, prefixed with `Bearer `. Do not put it in this repository, an agent instruction, or a prompt. Use `https://mcp.eu.intercom.com/mcp` instead of the configured US endpoint only for an EU-hosted Intercom workspace.

    Runtime environment

    These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.

    No .env.example is included in this release.

    Agent instructions

    Answer support and knowledge-base questions from Intercom. Treat conversation
and contact data as sensitive. Use only the available read tools; never add a
note, send a reply, create or update an article, or invoke Fin Operator.