Intercom Automation via Rube MCP
Automate Intercom operations through Composio's Intercom toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Intercom connection via
RUBE_MANAGE_CONNECTIONS with toolkit intercom
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit intercom
- If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Conversations
When to use: User wants to create, list, search, or manage support conversations
Tool sequence:
INTERCOM_LIST_ALL_ADMINS - Get admin IDs for assignment [Prerequisite]
INTERCOM_LIST_CONVERSATIONS - List all conversations [Optional]
INTERCOM_SEARCH_CONVERSATIONS - Search with filters [Optional]
INTERCOM_GET_CONVERSATION - Get conversation details [Optional]
INTERCOM_CREATE_CONVERSATION - Create a new conversation [Optional]
Key parameters:
from: Object with type ('user'/'lead') and id for conversation creator
body: Message body (HTML supported)
id: Conversation ID for retrieval
query: Search query object with field, operator, value
Pitfalls:
- CREATE_CONVERSATION requires a contact (user/lead) as the
from field, not an admin
- Conversation bodies support HTML; plain text is auto-wrapped in
<p> tags
- Search query uses structured filter objects, not free-text search
- Conversation IDs are numeric strings
2. Reply and Manage Conversation State
When to use: User wants to reply to, close, reopen, or assign conversations
Tool sequence:
INTERCOM_GET_CONVERSATION - Get current state [Prerequisite]
INTERCOM_REPLY_TO_CONVERSATION - Add a reply [Optional]
INTERCOM_ASSIGN_CONVERSATION - Assign to admin/team [Optional]
INTERCOM_CLOSE_CONVERSATION - Close conversation [Optional]
INTERCOM_REOPEN_CONVERSATION - Reopen closed conversation [Optional]
Key parameters:
conversation_id / id: Conversation ID
body: Reply message body (HTML supported)
type: Reply type ('admin' or 'user')
admin_id: Admin ID for replies from admin, assignment, and close/reopen
assignee_id: Admin or team ID for assignment
message_type: 'comment' (default) or 'note' (internal)
Pitfalls:
admin_id is REQUIRED for admin replies, close, reopen, and assignment operations
- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN
- Duplicate sends can occur on retry; implement idempotency checks
- Internal notes use
message_type: 'note'; visible only to workspace members
- Closing requires an admin_id and optional body message
3. Manage Contacts
When to use: User wants to search, view, or manage contacts (users and leads)
Tool sequence:
INTERCOM_SEARCH_CONTACTS - Search contacts with filters [Required]
INTERCOM_GET_A_CONTACT - Get specific contact [Optional]
INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID - Look up by external ID [Optional]
INTERCOM_LIST_CONTACTS - List all contacts [Optional]
INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT - Get contact tags [Optional]
INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT - Get contact segments [Optional]
INTERCOM_DETACH_A_CONTACT - Remove contact from company [Optional]
Key parameters:
contact_id: Contact ID for retrieval
external_id: External system ID for lookup
query: Search filter object with field, operator, value
pagination: Object with per_page and starting_after cursor
Pitfalls:
- SEARCH_CONTACTS uses structured query filters, not free-text; format:
{field, operator, value}
- Supported operators:
=, !=, >, <, ~ (contains), !~ (not contains), IN, NIN
- Contact types are 'user' (identified) or 'lead' (anonymous)
- LIST_CONTACTS returns paginated results; use
starting_after cursor for pagination
- External IDs are case-sensitive
4. Manage Admins and Teams
When to use: User wants to list workspace admins or identify specific admins
Tool sequence:
INTERCOM_LIST_ALL_ADMINS - List all admins and teams [Required]
INTERCOM_IDENTIFY_AN_ADMIN - Get specific admin details [Optional]
Key parameters:
admin_id: Admin ID for identification
Pitfalls:
- LIST_ALL_ADMINS returns both admins and teams
- Admin IDs are required for conversation replies, assignment, close, and reopen
- Teams appear in the admins list with
type: 'team'
5. View Segments and Counts
When to use: User wants to view segments or get aggregate counts
Tool sequence:
INTERCOM_LIST_SEGMENTS - List all segments [Optional]
INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT - Segments for a contact [Optional]
INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES - Segments for a company [Optional]
INTERCOM_GET_COUNTS - Get aggregate counts [Optional]
Key parameters:
contact_id: Contact ID for segment lookup
company_id: Company ID for segment lookup
type: Count type ('conversation', 'company', 'user', 'tag', 'segment')
count: Sub-count type
Pitfalls:
- GET_COUNTS returns approximate counts, not exact numbers
- Segment membership is computed; changes may not reflect immediately
6. Manage Companies
When to use: User wants to list companies or manage company-contact relationships
Tool sequence:
INTERCOM_LIST_ALL_COMPANIES - List all companies [Required]
INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES - Get company segments [Optional]
INTERCOM_DETACH_A_CONTACT - Remove contact from company [Optional]
Key parameters:
company_id: Company ID
contact_id: Contact ID for detachment
page: Page number for pagination
per_page: Results per page
Pitfalls:
- Company-contact relationships are managed through contact endpoints
- DETACH_A_CONTACT removes the contact-company association, not the contact itself
Common Patterns
Search Query Filters
Single filter:
{
"field": "email",
"operator": "=",
"value": "user@example.com"
}
Multiple filters (AND):
{
"operator": "AND",
"value": [
{"field": "role", "operator": "=", "value": "user"},
{"field": "created_at", "operator": ">", "value": 1672531200}
]
}
Supported fields for contacts: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id
Supported fields for conversations: created_at, updated_at, source.type, state, open, read
Pagination
- Most list endpoints use cursor-based pagination
- Check response for
pages.next with starting_after cursor
- Pass cursor in
pagination.starting_after for next page
- Continue until
pages.next is null
Admin ID Resolution
1. Call INTERCOM_LIST_ALL_ADMINS to get all admins
2. Find the desired admin by name or email
3. Use admin.id for replies, assignments, and state changes
Known Pitfalls
Admin ID Requirement:
- Admin ID is required for: reply (as admin), assign, close, reopen
- Always resolve admin IDs first with LIST_ALL_ADMINS
HTML Content:
- Conversation bodies are HTML
- Plain text is auto-wrapped in paragraph tags
- Sanitize HTML input to prevent rendering issues
Idempotency:
- Replies and conversation creation are not idempotent
- Duplicate sends can occur on retry or timeout
- Track message IDs to prevent duplicates
Rate Limits:
- Default: ~1000 requests per minute (varies by plan)
- 429 responses include rate limit headers
- Implement exponential backoff for retries
Quick Reference
| Task |
Tool Slug |
Key Params |
| List conversations |
INTERCOM_LIST_CONVERSATIONS |
(pagination) |
| Search conversations |
INTERCOM_SEARCH_CONVERSATIONS |
query |
| Get conversation |
INTERCOM_GET_CONVERSATION |
id |
| Create conversation |
INTERCOM_CREATE_CONVERSATION |
from, body |
| Reply to conversation |
INTERCOM_REPLY_TO_CONVERSATION |
conversation_id, body, admin_id |
| Assign conversation |
INTERCOM_ASSIGN_CONVERSATION |
conversation_id, admin_id, assignee_id |
| Close conversation |
INTERCOM_CLOSE_CONVERSATION |
id, admin_id |
| Reopen conversation |
INTERCOM_REOPEN_CONVERSATION |
id, admin_id |
| Search contacts |
INTERCOM_SEARCH_CONTACTS |
query |
| Get contact |
INTERCOM_GET_A_CONTACT |
contact_id |
| Contact by external ID |
INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID |
external_id |
| List contacts |
INTERCOM_LIST_CONTACTS |
(pagination) |
| Contact tags |
INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT |
contact_id |
| Contact segments |
INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT |
contact_id |
| Detach contact |
INTERCOM_DETACH_A_CONTACT |
contact_id, company_id |
| List admins |
INTERCOM_LIST_ALL_ADMINS |
(none) |
| Identify admin |
INTERCOM_IDENTIFY_AN_ADMIN |
admin_id |
| List segments |
INTERCOM_LIST_SEGMENTS |
(none) |
| Company segments |
INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES |
company_id |
| Get counts |
INTERCOM_GET_COUNTS |
type, count |
| List companies |
INTERCOM_LIST_ALL_COMPANIES |
page, per_page |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: intercom-automation3description: "Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/intercom-automation10---1112# Intercom Automation via Rube MCP1314Automate Intercom operations through Composio's Intercom toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active Intercom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`293. If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. Manage Conversations3536**When to use**: User wants to create, list, search, or manage support conversations3738**Tool sequence**:391. `INTERCOM_LIST_ALL_ADMINS` - Get admin IDs for assignment [Prerequisite]402. `INTERCOM_LIST_CONVERSATIONS` - List all conversations [Optional]413. `INTERCOM_SEARCH_CONVERSATIONS` - Search with filters [Optional]424. `INTERCOM_GET_CONVERSATION` - Get conversation details [Optional]435. `INTERCOM_CREATE_CONVERSATION` - Create a new conversation [Optional]4445**Key parameters**:46- `from`: Object with `type` ('user'/'lead') and `id` for conversation creator47- `body`: Message body (HTML supported)48- `id`: Conversation ID for retrieval49- `query`: Search query object with `field`, `operator`, `value`5051**Pitfalls**:52- CREATE_CONVERSATION requires a contact (user/lead) as the `from` field, not an admin53- Conversation bodies support HTML; plain text is auto-wrapped in `<p>` tags54- Search query uses structured filter objects, not free-text search55- Conversation IDs are numeric strings5657### 2. Reply and Manage Conversation State5859**When to use**: User wants to reply to, close, reopen, or assign conversations6061**Tool sequence**:621. `INTERCOM_GET_CONVERSATION` - Get current state [Prerequisite]632. `INTERCOM_REPLY_TO_CONVERSATION` - Add a reply [Optional]643. `INTERCOM_ASSIGN_CONVERSATION` - Assign to admin/team [Optional]654. `INTERCOM_CLOSE_CONVERSATION` - Close conversation [Optional]665. `INTERCOM_REOPEN_CONVERSATION` - Reopen closed conversation [Optional]6768**Key parameters**:69- `conversation_id` / `id`: Conversation ID70- `body`: Reply message body (HTML supported)71- `type`: Reply type ('admin' or 'user')72- `admin_id`: Admin ID for replies from admin, assignment, and close/reopen73- `assignee_id`: Admin or team ID for assignment74- `message_type`: 'comment' (default) or 'note' (internal)7576**Pitfalls**:77- `admin_id` is REQUIRED for admin replies, close, reopen, and assignment operations78- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN79- Duplicate sends can occur on retry; implement idempotency checks80- Internal notes use `message_type: 'note'`; visible only to workspace members81- Closing requires an admin_id and optional body message8283### 3. Manage Contacts8485**When to use**: User wants to search, view, or manage contacts (users and leads)8687**Tool sequence**:881. `INTERCOM_SEARCH_CONTACTS` - Search contacts with filters [Required]892. `INTERCOM_GET_A_CONTACT` - Get specific contact [Optional]903. `INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID` - Look up by external ID [Optional]914. `INTERCOM_LIST_CONTACTS` - List all contacts [Optional]925. `INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT` - Get contact tags [Optional]936. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Get contact segments [Optional]947. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]9596**Key parameters**:97- `contact_id`: Contact ID for retrieval98- `external_id`: External system ID for lookup99- `query`: Search filter object with `field`, `operator`, `value`100- `pagination`: Object with `per_page` and `starting_after` cursor101102**Pitfalls**:103- SEARCH_CONTACTS uses structured query filters, not free-text; format: `{field, operator, value}`104- Supported operators: `=`, `!=`, `>`, `<`, `~` (contains), `!~` (not contains), `IN`, `NIN`105- Contact types are 'user' (identified) or 'lead' (anonymous)106- LIST_CONTACTS returns paginated results; use `starting_after` cursor for pagination107- External IDs are case-sensitive108109### 4. Manage Admins and Teams110111**When to use**: User wants to list workspace admins or identify specific admins112113**Tool sequence**:1141. `INTERCOM_LIST_ALL_ADMINS` - List all admins and teams [Required]1152. `INTERCOM_IDENTIFY_AN_ADMIN` - Get specific admin details [Optional]116117**Key parameters**:118- `admin_id`: Admin ID for identification119120**Pitfalls**:121- LIST_ALL_ADMINS returns both admins and teams122- Admin IDs are required for conversation replies, assignment, close, and reopen123- Teams appear in the admins list with `type: 'team'`124125### 5. View Segments and Counts126127**When to use**: User wants to view segments or get aggregate counts128129**Tool sequence**:1301. `INTERCOM_LIST_SEGMENTS` - List all segments [Optional]1312. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Segments for a contact [Optional]1323. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Segments for a company [Optional]1334. `INTERCOM_GET_COUNTS` - Get aggregate counts [Optional]134135**Key parameters**:136- `contact_id`: Contact ID for segment lookup137- `company_id`: Company ID for segment lookup138- `type`: Count type ('conversation', 'company', 'user', 'tag', 'segment')139- `count`: Sub-count type140141**Pitfalls**:142- GET_COUNTS returns approximate counts, not exact numbers143- Segment membership is computed; changes may not reflect immediately144145### 6. Manage Companies146147**When to use**: User wants to list companies or manage company-contact relationships148149**Tool sequence**:1501. `INTERCOM_LIST_ALL_COMPANIES` - List all companies [Required]1512. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Get company segments [Optional]1523. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]153154**Key parameters**:155- `company_id`: Company ID156- `contact_id`: Contact ID for detachment157- `page`: Page number for pagination158- `per_page`: Results per page159160**Pitfalls**:161- Company-contact relationships are managed through contact endpoints162- DETACH_A_CONTACT removes the contact-company association, not the contact itself163164## Common Patterns165166### Search Query Filters167168**Single filter**:169```json170{171 "field": "email",172 "operator": "=",173 "value": "user@example.com"174}175```176177**Multiple filters (AND)**:178```json179{180 "operator": "AND",181 "value": [182 {"field": "role", "operator": "=", "value": "user"},183 {"field": "created_at", "operator": ">", "value": 1672531200}184 ]185}186```187188**Supported fields for contacts**: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id189190**Supported fields for conversations**: created_at, updated_at, source.type, state, open, read191192### Pagination193194- Most list endpoints use cursor-based pagination195- Check response for `pages.next` with `starting_after` cursor196- Pass cursor in `pagination.starting_after` for next page197- Continue until `pages.next` is null198199### Admin ID Resolution200201```2021. Call INTERCOM_LIST_ALL_ADMINS to get all admins2032. Find the desired admin by name or email2043. Use admin.id for replies, assignments, and state changes205```206207## Known Pitfalls208209**Admin ID Requirement**:210- Admin ID is required for: reply (as admin), assign, close, reopen211- Always resolve admin IDs first with LIST_ALL_ADMINS212213**HTML Content**:214- Conversation bodies are HTML215- Plain text is auto-wrapped in paragraph tags216- Sanitize HTML input to prevent rendering issues217218**Idempotency**:219- Replies and conversation creation are not idempotent220- Duplicate sends can occur on retry or timeout221- Track message IDs to prevent duplicates222223**Rate Limits**:224- Default: ~1000 requests per minute (varies by plan)225- 429 responses include rate limit headers226- Implement exponential backoff for retries227228## Quick Reference229230| Task | Tool Slug | Key Params |231|------|-----------|------------|232| List conversations | INTERCOM_LIST_CONVERSATIONS | (pagination) |233| Search conversations | INTERCOM_SEARCH_CONVERSATIONS | query |234| Get conversation | INTERCOM_GET_CONVERSATION | id |235| Create conversation | INTERCOM_CREATE_CONVERSATION | from, body |236| Reply to conversation | INTERCOM_REPLY_TO_CONVERSATION | conversation_id, body, admin_id |237| Assign conversation | INTERCOM_ASSIGN_CONVERSATION | conversation_id, admin_id, assignee_id |238| Close conversation | INTERCOM_CLOSE_CONVERSATION | id, admin_id |239| Reopen conversation | INTERCOM_REOPEN_CONVERSATION | id, admin_id |240| Search contacts | INTERCOM_SEARCH_CONTACTS | query |241| Get contact | INTERCOM_GET_A_CONTACT | contact_id |242| Contact by external ID | INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID | external_id |243| List contacts | INTERCOM_LIST_CONTACTS | (pagination) |244| Contact tags | INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT | contact_id |245| Contact segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT | contact_id |246| Detach contact | INTERCOM_DETACH_A_CONTACT | contact_id, company_id |247| List admins | INTERCOM_LIST_ALL_ADMINS | (none) |248| Identify admin | INTERCOM_IDENTIFY_AN_ADMIN | admin_id |249| List segments | INTERCOM_LIST_SEGMENTS | (none) |250| Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id |251| Get counts | INTERCOM_GET_COUNTS | type, count |252| List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page |253254## When to Use255This skill is applicable to execute the workflow or actions described in the overview.