RecipesIntercom
Intercom inbox
FreeOpen conversations, waiting on you, the newest threads, and teammates. Botopticon is not affiliated with Intercom.
Access
Intercom access token, read conversations
Required. Env INTERCOM_ACCESS_TOKEN. Mode api_key.
- Read conversations
- Read admins
In the Intercom Developer Hub create a private app on your workspace. Copy the access token. Read conversations is often an extended scope and may need Intercom's review. Do not grant Write conversations. This board only lists and counts threads.
Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.
Board
Sample · not your account.
Open
Newest
- 12:04North · Invoice date on Pro
- 11:51Acme · SSO timeout
- 11:20West · Export the board
Teammates
- 1Sam11open
- 2Riley8open
- 3Quinn5open
Command Tiles
ProSample · not your account. The agent puts the ask on the board. You answer there. How Command Tiles work
Take the waiting thread
Needs youApproval · Intercom
Assign the oldest waiting thread to you?
Who takes the queue?
Needs youQuestion · Intercom
Six conversations are waiting on an admin. Who takes them?
Tiles
- Open
- Waiting on youneeds you
- Newest
- Teammates
- Waiting on you. Set needs_you true when conversations waiting on an admin are greater than 0.
Setup
01
Mint a read-only Intercom key
Create a key that can only read. Never grant write. Keep it in the env var named on this page, on the agent or cron host. Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.
02
Create a Botopticon token
In the app, open Connection tokens and create one named after this board. Copy it. It is shown once. That token posts to Botopticon. It is not the source key.
03
Paste the prompt into your agent
Open the tab for Grok Bot, Muse, MCP, Cursor, Claude, or curl. Replace $BOTOPTICON_TOKEN. The agent fetches the source, maps the fields in the brief, and posts. Do not paste canned sample JSON as live data.
04
Wait for the first live post
These numbers are sample. They flip when your agent posts with the key. Each tile keeps the sample label until that tile is replaced.
Snippets
Same recipe, one tab per platform. Replace $BOTOPTICON_TOKEN with a connection token. The prompt fetches the source and posts. Do not paste the sample numbers as live data.
Paste this into Grok Bot. Replace $BOTOPTICON_TOKEN with a Botopticon connection token. Connect MCP at https://www.botopticon.com/api/mcp if this client can. If it cannot, POST /api/ingest with curl instead. Keep the Botopticon board "Intercom inbox" current. Source: Intercom. You hold INTERCOM_ACCESS_TOKEN (Intercom access token, read conversations). Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time. In the Intercom Developer Hub create a private app on your workspace. Copy the access token. Read conversations is often an extended scope and may need Intercom's review. Do not grant Write conversations. This board only lists and counts threads. Scopes (read-only): Read conversations, Read admins. What to fetch and how to map it: Read the current Intercom API docs. Objects: Conversation, Conversation part, Admin. Open: conversations that are not closed. Waiting on you: open conversations whose last part is from a contact, or whose state is waiting on admin. Set needs_you true when that count is greater than 0. Newest: newest open conversations as a feed. Label the contact name or id and the subject or first line. Never post full transcripts or customer lists. Teammates: rank admins by open conversations assigned to them. Tiles: - Open — bot Intercom, tile open-conv, type kpi. - Waiting on you — bot Intercom, tile waiting-you, type kpi. Set needs_you true when conversations waiting on an admin are greater than 0. Sample shows needs_you true. - Newest — bot Intercom, tile newest-conv, type feed. - Teammates — bot Intercom, tile teammates, type leaderboard. Post each tile to https://www.botopticon.com/api/ingest with header Authorization: Bearer $BOTOPTICON_TOKEN and Content-Type: application/json. Fields: bot, tile, type, title, subtitle, props, needs_you, ttl_seconds. If you can call MCP, connect to https://www.botopticon.com/api/mcp with the same Authorization header and call post_tile once per tile. The arguments are those JSON fields. Do not invent numbers. Do not post the same body again just to keep a tile fresh. Set ttl_seconds to how often the value really changes. A quiet tile should show as stale. When needs_you is true, say who is asking, what it is about, and the ask.
FAQ
- Which pane turns amber?
- Waiting on you. When any open conversation is waiting on an admin, the agent sets needs_you. Do not post the body of the thread.
- Does this run on the Free plan?
- Yes. Every tile in this recipe is a Free type. A Free workspace still has one board and 8 live tiles. Using this recipe adds the sample tiles to that board.
- Does Botopticon store the Intercom key?
- Botopticon never stores this key. Paste it into the agent, cron host, or MCP config. Revoke it any time.
- How does the board stay current?
- Your agent fetches the source and posts when a number changes. Set ttl_seconds to how often that work really happens, so a quiet tile shows as stale. Use a timer only for data no agent touches, and then at most daily. Never post the same content again just to keep a tile fresh.