[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-fc033f62-8e0b-4238-bb80-544d10601fda":3,"$ffpaKZIkr7KhTAFgKpIOSqXHis0Z47i_OVt4M_Ir5Ig8":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"fc033f62-8e0b-4238-bb80-544d10601fda","intercom-automation","通过Rube MCP（Composio）自动化对讲机任务：对话、联系人、公司、细分、管理员。始终首先搜索当前架构的工具。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: intercom-automation\ndescription: \"Automate Intercom tasks via Rube MCP (Composio): conversations, contacts, companies, segments, admins. Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Intercom Automation via Rube MCP\n\nAutomate Intercom operations through Composio's Intercom toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Intercom connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `intercom`\n3. If connection is not ACTIVE, follow the returned auth link to complete Intercom OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Conversations\n\n**When to use**: User wants to create, list, search, or manage support conversations\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_ADMINS` - Get admin IDs for assignment [Prerequisite]\n2. `INTERCOM_LIST_CONVERSATIONS` - List all conversations [Optional]\n3. `INTERCOM_SEARCH_CONVERSATIONS` - Search with filters [Optional]\n4. `INTERCOM_GET_CONVERSATION` - Get conversation details [Optional]\n5. `INTERCOM_CREATE_CONVERSATION` - Create a new conversation [Optional]\n\n**Key parameters**:\n- `from`: Object with `type` ('user'\u002F'lead') and `id` for conversation creator\n- `body`: Message body (HTML supported)\n- `id`: Conversation ID for retrieval\n- `query`: Search query object with `field`, `operator`, `value`\n\n**Pitfalls**:\n- CREATE_CONVERSATION requires a contact (user\u002Flead) as the `from` field, not an admin\n- Conversation bodies support HTML; plain text is auto-wrapped in `\u003Cp>` tags\n- Search query uses structured filter objects, not free-text search\n- Conversation IDs are numeric strings\n\n### 2. Reply and Manage Conversation State\n\n**When to use**: User wants to reply to, close, reopen, or assign conversations\n\n**Tool sequence**:\n1. `INTERCOM_GET_CONVERSATION` - Get current state [Prerequisite]\n2. `INTERCOM_REPLY_TO_CONVERSATION` - Add a reply [Optional]\n3. `INTERCOM_ASSIGN_CONVERSATION` - Assign to admin\u002Fteam [Optional]\n4. `INTERCOM_CLOSE_CONVERSATION` - Close conversation [Optional]\n5. `INTERCOM_REOPEN_CONVERSATION` - Reopen closed conversation [Optional]\n\n**Key parameters**:\n- `conversation_id` \u002F `id`: Conversation ID\n- `body`: Reply message body (HTML supported)\n- `type`: Reply type ('admin' or 'user')\n- `admin_id`: Admin ID for replies from admin, assignment, and close\u002Freopen\n- `assignee_id`: Admin or team ID for assignment\n- `message_type`: 'comment' (default) or 'note' (internal)\n\n**Pitfalls**:\n- `admin_id` is REQUIRED for admin replies, close, reopen, and assignment operations\n- Always fetch admin IDs first with LIST_ALL_ADMINS or IDENTIFY_AN_ADMIN\n- Duplicate sends can occur on retry; implement idempotency checks\n- Internal notes use `message_type: 'note'`; visible only to workspace members\n- Closing requires an admin_id and optional body message\n\n### 3. Manage Contacts\n\n**When to use**: User wants to search, view, or manage contacts (users and leads)\n\n**Tool sequence**:\n1. `INTERCOM_SEARCH_CONTACTS` - Search contacts with filters [Required]\n2. `INTERCOM_GET_A_CONTACT` - Get specific contact [Optional]\n3. `INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID` - Look up by external ID [Optional]\n4. `INTERCOM_LIST_CONTACTS` - List all contacts [Optional]\n5. `INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT` - Get contact tags [Optional]\n6. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Get contact segments [Optional]\n7. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]\n\n**Key parameters**:\n- `contact_id`: Contact ID for retrieval\n- `external_id`: External system ID for lookup\n- `query`: Search filter object with `field`, `operator`, `value`\n- `pagination`: Object with `per_page` and `starting_after` cursor\n\n**Pitfalls**:\n- SEARCH_CONTACTS uses structured query filters, not free-text; format: `{field, operator, value}`\n- Supported operators: `=`, `!=`, `>`, `\u003C`, `~` (contains), `!~` (not contains), `IN`, `NIN`\n- Contact types are 'user' (identified) or 'lead' (anonymous)\n- LIST_CONTACTS returns paginated results; use `starting_after` cursor for pagination\n- External IDs are case-sensitive\n\n### 4. Manage Admins and Teams\n\n**When to use**: User wants to list workspace admins or identify specific admins\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_ADMINS` - List all admins and teams [Required]\n2. `INTERCOM_IDENTIFY_AN_ADMIN` - Get specific admin details [Optional]\n\n**Key parameters**:\n- `admin_id`: Admin ID for identification\n\n**Pitfalls**:\n- LIST_ALL_ADMINS returns both admins and teams\n- Admin IDs are required for conversation replies, assignment, close, and reopen\n- Teams appear in the admins list with `type: 'team'`\n\n### 5. View Segments and Counts\n\n**When to use**: User wants to view segments or get aggregate counts\n\n**Tool sequence**:\n1. `INTERCOM_LIST_SEGMENTS` - List all segments [Optional]\n2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT` - Segments for a contact [Optional]\n3. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Segments for a company [Optional]\n4. `INTERCOM_GET_COUNTS` - Get aggregate counts [Optional]\n\n**Key parameters**:\n- `contact_id`: Contact ID for segment lookup\n- `company_id`: Company ID for segment lookup\n- `type`: Count type ('conversation', 'company', 'user', 'tag', 'segment')\n- `count`: Sub-count type\n\n**Pitfalls**:\n- GET_COUNTS returns approximate counts, not exact numbers\n- Segment membership is computed; changes may not reflect immediately\n\n### 6. Manage Companies\n\n**When to use**: User wants to list companies or manage company-contact relationships\n\n**Tool sequence**:\n1. `INTERCOM_LIST_ALL_COMPANIES` - List all companies [Required]\n2. `INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES` - Get company segments [Optional]\n3. `INTERCOM_DETACH_A_CONTACT` - Remove contact from company [Optional]\n\n**Key parameters**:\n- `company_id`: Company ID\n- `contact_id`: Contact ID for detachment\n- `page`: Page number for pagination\n- `per_page`: Results per page\n\n**Pitfalls**:\n- Company-contact relationships are managed through contact endpoints\n- DETACH_A_CONTACT removes the contact-company association, not the contact itself\n\n## Common Patterns\n\n### Search Query Filters\n\n**Single filter**:\n```json\n{\n  \"field\": \"email\",\n  \"operator\": \"=\",\n  \"value\": \"user@example.com\"\n}\n```\n\n**Multiple filters (AND)**:\n```json\n{\n  \"operator\": \"AND\",\n  \"value\": [\n    {\"field\": \"role\", \"operator\": \"=\", \"value\": \"user\"},\n    {\"field\": \"created_at\", \"operator\": \">\", \"value\": 1672531200}\n  ]\n}\n```\n\n**Supported fields for contacts**: email, name, role, created_at, updated_at, signed_up_at, last_seen_at, external_id\n\n**Supported fields for conversations**: created_at, updated_at, source.type, state, open, read\n\n### Pagination\n\n- Most list endpoints use cursor-based pagination\n- Check response for `pages.next` with `starting_after` cursor\n- Pass cursor in `pagination.starting_after` for next page\n- Continue until `pages.next` is null\n\n### Admin ID Resolution\n\n```\n1. Call INTERCOM_LIST_ALL_ADMINS to get all admins\n2. Find the desired admin by name or email\n3. Use admin.id for replies, assignments, and state changes\n```\n\n## Known Pitfalls\n\n**Admin ID Requirement**:\n- Admin ID is required for: reply (as admin), assign, close, reopen\n- Always resolve admin IDs first with LIST_ALL_ADMINS\n\n**HTML Content**:\n- Conversation bodies are HTML\n- Plain text is auto-wrapped in paragraph tags\n- Sanitize HTML input to prevent rendering issues\n\n**Idempotency**:\n- Replies and conversation creation are not idempotent\n- Duplicate sends can occur on retry or timeout\n- Track message IDs to prevent duplicates\n\n**Rate Limits**:\n- Default: ~1000 requests per minute (varies by plan)\n- 429 responses include rate limit headers\n- Implement exponential backoff for retries\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List conversations | INTERCOM_LIST_CONVERSATIONS | (pagination) |\n| Search conversations | INTERCOM_SEARCH_CONVERSATIONS | query |\n| Get conversation | INTERCOM_GET_CONVERSATION | id |\n| Create conversation | INTERCOM_CREATE_CONVERSATION | from, body |\n| Reply to conversation | INTERCOM_REPLY_TO_CONVERSATION | conversation_id, body, admin_id |\n| Assign conversation | INTERCOM_ASSIGN_CONVERSATION | conversation_id, admin_id, assignee_id |\n| Close conversation | INTERCOM_CLOSE_CONVERSATION | id, admin_id |\n| Reopen conversation | INTERCOM_REOPEN_CONVERSATION | id, admin_id |\n| Search contacts | INTERCOM_SEARCH_CONTACTS | query |\n| Get contact | INTERCOM_GET_A_CONTACT | contact_id |\n| Contact by external ID | INTERCOM_SHOW_CONTACT_BY_EXTERNAL_ID | external_id |\n| List contacts | INTERCOM_LIST_CONTACTS | (pagination) |\n| Contact tags | INTERCOM_LIST_TAGS_ATTACHED_TO_A_CONTACT | contact_id |\n| Contact segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_CONTACT | contact_id |\n| Detach contact | INTERCOM_DETACH_A_CONTACT | contact_id, company_id |\n| List admins | INTERCOM_LIST_ALL_ADMINS | (none) |\n| Identify admin | INTERCOM_IDENTIFY_AN_ADMIN | admin_id |\n| List segments | INTERCOM_LIST_SEGMENTS | (none) |\n| Company segments | INTERCOM_LIST_ATTACHED_SEGMENTS_FOR_COMPANIES | company_id |\n| Get counts | INTERCOM_GET_COUNTS | type, count |\n| List companies | INTERCOM_LIST_ALL_COMPANIES | page, per_page |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,61,1571,"2026-05-16 13:23:56",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"4e5ffa22-14cd-484a-9467-2794fafdf7d0","1.0.0","intercom-automation.zip",3585,"uploads\u002Fskills\u002Ffc033f62-8e0b-4238-bb80-544d10601fda\u002Fintercom-automation.zip","b32849b0e603a49f6bb06c78774eb661e815a58e5a4ec9363ea279827ebdf44b","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":10085}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]