intercom-automation
Scannednpx machina-cli add skill davepoon/buildwithclaude/intercom-automation --openclawIntercom Automation via Rube MCP
Automate Intercom operations through Composio's Intercom toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/intercom
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Intercom connection via
RUBE_MANAGE_CONNECTIONSwith toolkitintercom - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitintercom - 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 withtype('user'/'lead') andidfor conversation creatorbody: Message body (HTML supported)id: Conversation ID for retrievalquery: Search query object withfield,operator,value
Pitfalls:
- CREATE_CONVERSATION requires a contact (user/lead) as the
fromfield, 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 IDbody: Reply message body (HTML supported)type: Reply type ('admin' or 'user')admin_id: Admin ID for replies from admin, assignment, and close/reopenassignee_id: Admin or team ID for assignmentmessage_type: 'comment' (default) or 'note' (internal)
Pitfalls:
admin_idis 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 retrievalexternal_id: External system ID for lookupquery: Search filter object withfield,operator,valuepagination: Object withper_pageandstarting_aftercursor
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_aftercursor 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 lookupcompany_id: Company ID for segment lookuptype: 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 IDcontact_id: Contact ID for detachmentpage: Page number for paginationper_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.nextwithstarting_aftercursor - Pass cursor in
pagination.starting_afterfor next page - Continue until
pages.nextis 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 |
Powered by Composio
Source
git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/intercom-automation/SKILL.mdView on GitHub Overview
Automate Intercom operations via Composio's Intercom toolkit through Rube MCP. It covers conversations, contacts, companies, segments, and admins, and requires always calling RUBE_SEARCH_TOOLS first to fetch current tool schemas.
How This Skill Works
You first verify RUBE_SEARCH_TOOLS to fetch current schemas, then establish a connection to Intercom via RUBE_MANAGE_CONNECTIONS using the intercom toolkit. Once connected, you run chained Intercom tool calls (list, get, search, create, reply, assign, close, etc.) to automate conversations and contact workflows from your MCP.
When to Use It
- Create, list, or search Intercom conversations automatically
- Reply to, assign, close, or reopen conversations based on events
- Search, view, or update contact records and external IDs
- List admins to fetch IDs needed for assignments
- Manage contact segments or tags to automate routing
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify availability by calling RUBE_SEARCH_TOOLS
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'intercom' and complete Intercom OAuth if prompted
- Step 3: Confirm connection is ACTIVE and start with a simple workflow (e.g., INTERCOM_LIST_CONVERSATIONS or INTERCOM_SEARCH_CONTACTS)
Best Practices
- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN
- Provide a valid 'from' object when creating a conversation (type and id)
- Use idempotency checks to prevent duplicate sends on retry
- Use message_type 'note' for internal notes and 'comment' for customer-visible messages
- Verify the Intercom connection is ACTIVE before running any workflows
Example Use Cases
- Onboard a new user by creating a welcome conversation and assigning it to a onboarding agent
- Auto-respond and route incoming chats to the appropriate admin or team
- Lookup a contact by external_id and attach them to a company or segment
- Audit workflow: list all admins to prepare an escalation path for critical issues
- Engagement automation: add a specific segment to a contact when they reach a milestone
Frequently Asked Questions
Related Skills
helpdesk-automation
davepoon/buildwithclaude
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
freshdesk-automation
davepoon/buildwithclaude
Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.
freshservice-automation
davepoon/buildwithclaude
Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.
zendesk-automation
davepoon/buildwithclaude
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.