Automate Intercom Conversations and Contacts

Automates Intercom operations - conversation management and replies, contact search, admin/team lookup, segment viewing, and company management - through Composio's Intercom toolkit exposed via Rube MCP. It documents exact tool sequences, required parameters, and the admin-ID and idempotency pitfalls needed to drive Intercom correctly.

Use this skill when a task requires creating/searching/managing Intercom support conversations, replying to or reassigning conversations, searching contacts, looking up admins and teams, viewing segments/counts, or managing companies. It assumes Rube MCP is already connected (RUBE_SEARCH_TOOLS available) and the Intercom connection is ACTIVE via RUBE_MANAGE_CONNECTIONS - always call RUBE_SEARCH_TOOLS first for current schemas.

Setup: add https://rube.app/mcp as an MCP server (no API keys needed), verify RUBE_SEARCH_TOOLS responds, call RUBE_MANAGE_CONNECTIONS with toolkit intercom, complete the OAuth link if not ACTIVE.

Six core workflows: Conversations - INTERCOM_CREATE_CONVERSATION requires a contact (user/lead) as the from field, not an admin, with HTML-supported body text. Reply/state management - INTERCOM_REPLY_TO_CONVERSATION, INTERCOM_ASSIGN_CONVERSATION, INTERCOM_CLOSE_CONVERSATION, and INTERCOM_REOPEN_CONVERSATION all require an admin_id, resolved first via INTERCOM_LIST_ALL_ADMINS; message_type: 'note' creates a workspace-internal note instead of a customer-visible reply. Contacts - INTERCOM_SEARCH_CONTACTS uses structured {field, operator, value} filters (operators include =, !=, >, <, ~, !~, IN, NIN), not free text; contact types are user (identified) or lead (anonymous); pagination uses a starting_after cursor. Admins/teams - INTERCOM_LIST_ALL_ADMINS returns both admins and teams (teams have type: 'team'); admin IDs are required for replies, assignment, close, and reopen. Segments/counts - INTERCOM_LIST_SEGMENTS, per-contact/company segment lookups, and INTERCOM_GET_COUNTS which returns approximate, not exact, counts with possibly-delayed segment membership. Companies - INTERCOM_LIST_ALL_COMPANIES and INTERCOM_DETACH_A_CONTACT, which removes the contact-company association without deleting the contact itself.

Search query filters use structured JSON, e.g. {"field": "email", "operator": "=", "value": "user@example.com"}, combinable with an AND operator over multiple filter objects; supported contact fields include email, name, role, created_at, and external_id, while conversation fields include created_at, state, open, and read.

Known pitfalls preserved from the source: conversation and reply operations are not idempotent, so duplicate sends can occur on retry and message IDs should be tracked to prevent them; conversation bodies are HTML (plain text auto-wraps in <p> tags) and should be sanitized; and rate limits default to roughly 1000 requests/minute with 429 responses carrying rate-limit headers, requiring exponential backoff.

Runs entirely through Rube MCP (https://rube.app/mcp) and Composio's Intercom toolkit - RUBE_SEARCH_TOOLS for schema discovery and RUBE_MANAGE_CONNECTIONS for the Intercom OAuth connection, with no separate Intercom API key management required.

Support and ops teams and automation builders who need to drive Intercom conversation, contact, admin, segment, and company workflows through Composio/Rube MCP tools correctly - especially around the admin-ID requirements, structured search filters, and idempotency concerns that are easy to get wrong from the raw Intercom API alone.