Close Automation

1---
2name: close-automation
3description: "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas."
4requires:
5  mcp: [rube]
6---
7 
8# Close CRM Automation via Rube MCP
9 
10Automate Close CRM operations through Composio's Close toolkit via Rube MCP.
11 
12## Prerequisites
13 
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active Close connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `close`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17 
18## Setup
19 
20**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.
21 
22 
231. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
242. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `close`
253. If connection is not ACTIVE, follow the returned auth link to complete Close API authentication
264. Confirm connection status shows ACTIVE before running any workflows
27 
28## Core Workflows
29 
30### 1. Create and Manage Leads
31 
32**When to use**: User wants to create new leads or manage existing lead records
33 
34**Tool sequence**:
351. `CLOSE_CREATE_LEAD` - Create a new lead in Close [Required]
36 
37**Key parameters**:
38- `name`: Lead/company name
39- `contacts`: Array of contact objects associated with the lead
40- `custom`: Custom field values as key-value pairs
41- `status_id`: Lead status ID
42 
43**Pitfalls**:
44- Leads in Close represent companies/organizations, not individual people
45- Contacts are nested within leads; create the lead first, then contacts are included
46- Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names
47- Duplicate lead detection is not automatic; check before creating
48 
49### 2. Log Calls
50 
51**When to use**: User wants to log a phone call activity against a lead
52 
53**Tool sequence**:
541. `CLOSE_CREATE_CALL` - Log a call activity [Required]
55 
56**Key parameters**:
57- `lead_id`: ID of the associated lead
58- `contact_id`: ID of the contact called
59- `direction`: 'outbound' or 'inbound'
60- `status`: Call status ('completed', 'no-answer', 'busy', etc.)
61- `duration`: Call duration in seconds
62- `note`: Call notes
63 
64**Pitfalls**:
65- lead_id is required; calls must be associated with a lead
66- Duration is in seconds, not minutes
67- Call direction affects reporting and analytics
68- contact_id is optional but recommended for tracking
69 
70### 3. Send SMS Messages
71 
72**When to use**: User wants to send or log SMS messages through Close
73 
74**Tool sequence**:
751. `CLOSE_CREATE_SMS` - Send or log an SMS message [Required]
76 
77**Key parameters**:
78- `lead_id`: ID of the associated lead
79- `contact_id`: ID of the contact
80- `direction`: 'outbound' or 'inbound'
81- `text`: SMS message content
82- `status`: Message status
83 
84**Pitfalls**:
85- SMS functionality requires Close phone/SMS integration to be configured
86- lead_id is required for all SMS activities
87- Outbound SMS may require a verified sending number
88- Message length limits may apply depending on carrier
89 
90### 4. Manage Tasks
91 
92**When to use**: User wants to create or manage follow-up tasks
93 
94**Tool sequence**:
951. `CLOSE_CREATE_TASK` - Create a new task [Required]
96 
97**Key parameters**:
98- `lead_id`: Associated lead ID
99- `text`: Task description
100- `date`: Due date for the task
101- `assigned_to`: User ID of the assignee
102- `is_complete`: Whether the task is completed
103 
104**Pitfalls**:
105- Tasks are associated with leads, not contacts
106- Date format should follow ISO 8601
107- assigned_to requires the Close user ID, not email or name
108- Tasks without a date appear in the 'no due date' section
109 
110### 5. Manage Notes
111 
112**When to use**: User wants to add or retrieve notes on leads
113 
114**Tool sequence**:
1151. `CLOSE_GET_NOTE` - Retrieve a specific note [Required]
116 
117**Key parameters**:
118- `note_id`: ID of the note to retrieve
119 
120**Pitfalls**:
121- Notes are associated with leads
122- Note IDs are required for retrieval; search leads first to find note references
123- Notes support plain text and basic formatting
124 
125### 6. Delete Activities
126 
127**When to use**: User wants to remove call records or other activities
128 
129**Tool sequence**:
1301. `CLOSE_DELETE_CALL` - Delete a call activity [Required]
131 
132**Key parameters**:
133- `call_id`: ID of the call to delete
134 
135**Pitfalls**:
136- Deletion is permanent and cannot be undone
137- Only the call creator or admin can delete calls
138- Deleting a call removes it from all reports and timelines
139 
140## Common Patterns
141 
142### Lead and Contact Relationship
143 
144```
145Close data model:
146- Lead = Company/Organization
147  - Contact = Person (nested within Lead)
148  - Activity = Call, SMS, Email, Note (linked to Lead)
149  - Task = Follow-up item (linked to Lead)
150  - Opportunity = Deal (linked to Lead)
151```
152 
153### ID Resolution
154 
155**Lead ID**:
156```
1571. Search for leads using the Close search API
1582. Extract lead_id from results (format: 'lead_XXXXXXXXXXXXX')
1593. Use lead_id in all activity creation calls
160```
161 
162**Contact ID**:
163```
1641. Retrieve lead details to get nested contacts
1652. Extract contact_id (format: 'cont_XXXXXXXXXXXXX')
1663. Use in call/SMS activities for accurate tracking
167```
168 
169### Activity Logging Pattern
170 
171```
1721. Identify the lead_id and optionally contact_id
1732. Create the activity (call, SMS, note) with lead_id
1743. Include relevant metadata (duration, direction, status)
1754. Create follow-up tasks if needed
176```
177 
178## Known Pitfalls
179 
180**ID Formats**:
181- Lead IDs: 'lead_XXXXXXXXXXXXX'
182- Contact IDs: 'cont_XXXXXXXXXXXXX'
183- Activity IDs vary by type: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'
184- Custom field IDs: 'custom.cf_XXXXXXXXXXXXX'
185- Always use the full ID string
186 
187**Rate Limits**:
188- Close API has rate limits based on your plan
189- Implement delays between bulk operations
190- Monitor response headers for rate limit status
191- 429 responses require backoff
192 
193**Custom Fields**:
194- Custom fields are referenced by their API ID, not display name
195- Different lead statuses may have different required custom fields
196- Custom field types (text, number, date, dropdown) enforce value formats
197 
198**Data Integrity**:
199- Leads are the primary entity; contacts and activities are linked to leads
200- Deleting a lead may cascade to its contacts and activities
201- Bulk operations should validate IDs before executing
202 
203## Quick Reference
204 
205| Task | Tool Slug | Key Params |
206|------|-----------|------------|
207| Create lead | CLOSE_CREATE_LEAD | name, contacts, custom |
208| Log call | CLOSE_CREATE_CALL | lead_id, direction, status, duration |
209| Send SMS | CLOSE_CREATE_SMS | lead_id, text, direction |
210| Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to |
211| Get note | CLOSE_GET_NOTE | note_id |
212| Delete call | CLOSE_DELETE_CALL | call_id |
213