[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-1049327e-576e-447b-94d4-ee59da402115":3,"$fACgAw4G2uZH5LIrRB6_x3HQ3ZxjIpSetwuVF_xtVtek":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},"1049327e-576e-447b-94d4-ee59da402115","close-automation","通过Rube MCP（Composio）自动化关闭CRM任务：创建线索、管理电话\u002F短信、处理任务和跟踪笔记。始终首先搜索当前模式下的工具。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: close-automation\ndescription: \"Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls\u002FSMS, handle tasks, and track notes. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Close CRM Automation via Rube MCP\n\nAutomate Close CRM operations through Composio's Close toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Close connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `close`\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 `close`\n3. If connection is not ACTIVE, follow the returned auth link to complete Close API authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Leads\n\n**When to use**: User wants to create new leads or manage existing lead records\n\n**Tool sequence**:\n1. `CLOSE_CREATE_LEAD` - Create a new lead in Close [Required]\n\n**Key parameters**:\n- `name`: Lead\u002Fcompany name\n- `contacts`: Array of contact objects associated with the lead\n- `custom`: Custom field values as key-value pairs\n- `status_id`: Lead status ID\n\n**Pitfalls**:\n- Leads in Close represent companies\u002Forganizations, not individual people\n- Contacts are nested within leads; create the lead first, then contacts are included\n- Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names\n- Duplicate lead detection is not automatic; check before creating\n\n### 2. Log Calls\n\n**When to use**: User wants to log a phone call activity against a lead\n\n**Tool sequence**:\n1. `CLOSE_CREATE_CALL` - Log a call activity [Required]\n\n**Key parameters**:\n- `lead_id`: ID of the associated lead\n- `contact_id`: ID of the contact called\n- `direction`: 'outbound' or 'inbound'\n- `status`: Call status ('completed', 'no-answer', 'busy', etc.)\n- `duration`: Call duration in seconds\n- `note`: Call notes\n\n**Pitfalls**:\n- lead_id is required; calls must be associated with a lead\n- Duration is in seconds, not minutes\n- Call direction affects reporting and analytics\n- contact_id is optional but recommended for tracking\n\n### 3. Send SMS Messages\n\n**When to use**: User wants to send or log SMS messages through Close\n\n**Tool sequence**:\n1. `CLOSE_CREATE_SMS` - Send or log an SMS message [Required]\n\n**Key parameters**:\n- `lead_id`: ID of the associated lead\n- `contact_id`: ID of the contact\n- `direction`: 'outbound' or 'inbound'\n- `text`: SMS message content\n- `status`: Message status\n\n**Pitfalls**:\n- SMS functionality requires Close phone\u002FSMS integration to be configured\n- lead_id is required for all SMS activities\n- Outbound SMS may require a verified sending number\n- Message length limits may apply depending on carrier\n\n### 4. Manage Tasks\n\n**When to use**: User wants to create or manage follow-up tasks\n\n**Tool sequence**:\n1. `CLOSE_CREATE_TASK` - Create a new task [Required]\n\n**Key parameters**:\n- `lead_id`: Associated lead ID\n- `text`: Task description\n- `date`: Due date for the task\n- `assigned_to`: User ID of the assignee\n- `is_complete`: Whether the task is completed\n\n**Pitfalls**:\n- Tasks are associated with leads, not contacts\n- Date format should follow ISO 8601\n- assigned_to requires the Close user ID, not email or name\n- Tasks without a date appear in the 'no due date' section\n\n### 5. Manage Notes\n\n**When to use**: User wants to add or retrieve notes on leads\n\n**Tool sequence**:\n1. `CLOSE_GET_NOTE` - Retrieve a specific note [Required]\n\n**Key parameters**:\n- `note_id`: ID of the note to retrieve\n\n**Pitfalls**:\n- Notes are associated with leads\n- Note IDs are required for retrieval; search leads first to find note references\n- Notes support plain text and basic formatting\n\n### 6. Delete Activities\n\n**When to use**: User wants to remove call records or other activities\n\n**Tool sequence**:\n1. `CLOSE_DELETE_CALL` - Delete a call activity [Required]\n\n**Key parameters**:\n- `call_id`: ID of the call to delete\n\n**Pitfalls**:\n- Deletion is permanent and cannot be undone\n- Only the call creator or admin can delete calls\n- Deleting a call removes it from all reports and timelines\n\n## Common Patterns\n\n### Lead and Contact Relationship\n\n```\nClose data model:\n- Lead = Company\u002FOrganization\n  - Contact = Person (nested within Lead)\n  - Activity = Call, SMS, Email, Note (linked to Lead)\n  - Task = Follow-up item (linked to Lead)\n  - Opportunity = Deal (linked to Lead)\n```\n\n### ID Resolution\n\n**Lead ID**:\n```\n1. Search for leads using the Close search API\n2. Extract lead_id from results (format: 'lead_XXXXXXXXXXXXX')\n3. Use lead_id in all activity creation calls\n```\n\n**Contact ID**:\n```\n1. Retrieve lead details to get nested contacts\n2. Extract contact_id (format: 'cont_XXXXXXXXXXXXX')\n3. Use in call\u002FSMS activities for accurate tracking\n```\n\n### Activity Logging Pattern\n\n```\n1. Identify the lead_id and optionally contact_id\n2. Create the activity (call, SMS, note) with lead_id\n3. Include relevant metadata (duration, direction, status)\n4. Create follow-up tasks if needed\n```\n\n## Known Pitfalls\n\n**ID Formats**:\n- Lead IDs: 'lead_XXXXXXXXXXXXX'\n- Contact IDs: 'cont_XXXXXXXXXXXXX'\n- Activity IDs vary by type: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'\n- Custom field IDs: 'custom.cf_XXXXXXXXXXXXX'\n- Always use the full ID string\n\n**Rate Limits**:\n- Close API has rate limits based on your plan\n- Implement delays between bulk operations\n- Monitor response headers for rate limit status\n- 429 responses require backoff\n\n**Custom Fields**:\n- Custom fields are referenced by their API ID, not display name\n- Different lead statuses may have different required custom fields\n- Custom field types (text, number, date, dropdown) enforce value formats\n\n**Data Integrity**:\n- Leads are the primary entity; contacts and activities are linked to leads\n- Deleting a lead may cascade to its contacts and activities\n- Bulk operations should validate IDs before executing\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create lead | CLOSE_CREATE_LEAD | name, contacts, custom |\n| Log call | CLOSE_CREATE_CALL | lead_id, direction, status, duration |\n| Send SMS | CLOSE_CREATE_SMS | lead_id, text, direction |\n| Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to |\n| Get note | CLOSE_GET_NOTE | note_id |\n| Delete call | CLOSE_DELETE_CALL | call_id |\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,64,942,"2026-05-16 13:11:15",{"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},"4267fdb4-a732-4eca-919c-7fa8f9d5f4a6","1.0.0","close-automation.zip",2929,"uploads\u002Fskills\u002F1049327e-576e-447b-94d4-ee59da402115\u002Fclose-automation.zip","fc94d37fa8615ef8fdceb90d5b1c12054b55d21737093a7393c64feaa9e466b4","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":7099}]",{"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]