close-automation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Close CRM Automation via Rube MCP

通过Rube MCP实现Close CRM自动化

Automate Close CRM operations through Composio's Close toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/close

通过Rube MCP，借助Composio的Close工具包自动化Close CRM操作。

工具包文档：composio.dev/toolkits/close

Prerequisites

前提条件

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Close connection via
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
close
```
Always call
```
RUBE_SEARCH_TOOLS
```
first to get current tool schemas

必须已连接Rube MCP（需具备RUBE_SEARCH_TOOLS功能）
通过
```
RUBE_MANAGE_CONNECTIONS
```
使用
```
close
```
工具包建立有效的Close连接
请始终先调用
```
RUBE_SEARCH_TOOLS
```
以获取最新的工具模式

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_TOOLS
```
responds
Call
```
RUBE_MANAGE_CONNECTIONS
```
with toolkit
```
close
```
If connection is not ACTIVE, follow the returned auth link to complete Close API authentication
Confirm connection status shows ACTIVE before running any workflows

获取Rube MCP：在客户端配置中添加

https://rube.app/mcp

作为MCP服务器。无需API密钥——只需添加该端点即可使用。

通过确认
```
RUBE_SEARCH_TOOLS
```
能响应，验证Rube MCP是否可用
调用
```
RUBE_MANAGE_CONNECTIONS
```
并使用
```
close
```
工具包
如果连接未处于ACTIVE状态，请按照返回的认证链接完成Close API认证
在运行任何工作流之前，确认连接状态显示为ACTIVE

Core Workflows

核心工作流

1. Create and Manage Leads

1. 创建与管理线索

When to use: User wants to create new leads or manage existing lead records

Tool sequence:

```
CLOSE_CREATE_LEAD
```
- Create a new lead in Close [Required]

Key parameters:

```
name
```
: Lead/company name
```
contacts
```
: Array of contact objects associated with the lead
```
custom
```
: Custom field values as key-value pairs
```
status_id
```
: Lead status ID

Pitfalls:

Leads in Close represent companies/organizations, not individual people
Contacts are nested within leads; create the lead first, then contacts are included
Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names
Duplicate lead detection is not automatic; check before creating

适用场景：用户需要创建新线索或管理现有线索记录

工具流程:

```
CLOSE_CREATE_LEAD
```
- 在Close中创建新线索 [必填]

关键参数:

```
name
```
: 线索/公司名称
```
contacts
```
: 与线索关联的联系人对象数组
```
custom
```
: 自定义字段的键值对
```
status_id
```
: 线索状态ID

注意事项:

Close中的线索代表公司/组织，而非个人
联系人嵌套在线索中；需先创建线索，再添加联系人
自定义字段需使用字段ID（例如'custom.cf_XXX'），而非显示名称
系统不会自动检测重复线索，创建前需自行检查

2. Log Calls

2. 记录通话

When to use: User wants to log a phone call activity against a lead

Tool sequence:

```
CLOSE_CREATE_CALL
```
- Log a call activity [Required]

Key parameters:

```
lead_id
```
: ID of the associated lead
```
contact_id
```
: ID of the contact called
```
direction
```
: 'outbound' or 'inbound'
```
status
```
: Call status ('completed', 'no-answer', 'busy', etc.)
```
duration
```
: Call duration in seconds
```
note
```
: Call notes

Pitfalls:

lead_id is required; calls must be associated with a lead
Duration is in seconds, not minutes
Call direction affects reporting and analytics
contact_id is optional but recommended for tracking

适用场景：用户需要为线索记录通话活动

工具流程:

```
CLOSE_CREATE_CALL
```
- 记录通话活动 [必填]

关键参数:

```
lead_id
```
: 关联的线索ID
```
contact_id
```
: 被联系的联系人ID
```
direction
```
: 'outbound'（呼出）或 'inbound'（呼入）
```
status
```
: 通话状态（'completed'已完成、'no-answer'未接听、'busy'占线等）
```
duration
```
: 通话时长（秒）
```
note
```
: 通话备注

注意事项:

必须填写lead_id；通话必须关联到线索
时长单位为秒，而非分钟
通话方向会影响报表和数据分析
contact_id为可选参数，但建议填写以实现精准跟踪

3. Send SMS Messages

3. 发送短信

When to use: User wants to send or log SMS messages through Close

Tool sequence:

```
CLOSE_CREATE_SMS
```
- Send or log an SMS message [Required]

Key parameters:

```
lead_id
```
: ID of the associated lead
```
contact_id
```
: ID of the contact
```
direction
```
: 'outbound' or 'inbound'
```
text
```
: SMS message content
```
status
```
: Message status

Pitfalls:

SMS functionality requires Close phone/SMS integration to be configured
lead_id is required for all SMS activities
Outbound SMS may require a verified sending number
Message length limits may apply depending on carrier

适用场景：用户需要通过Close发送或记录短信

工具流程:

```
CLOSE_CREATE_SMS
```
- 发送或记录短信 [必填]

关键参数:

```
lead_id
```
: 关联的线索ID
```
contact_id
```
: 联系人ID
```
direction
```
: 'outbound'（发送）或 'inbound'（接收）
```
text
```
: 短信内容
```
status
```
: 消息状态

注意事项:

短信功能需要先配置Close的电话/短信集成
所有短信活动都必须填写lead_id
发送短信可能需要验证发送号码
消息长度限制可能因运营商而异

4. Manage Tasks

4. 管理任务

When to use: User wants to create or manage follow-up tasks

Tool sequence:

```
CLOSE_CREATE_TASK
```
- Create a new task [Required]

Key parameters:

```
lead_id
```
: Associated lead ID
```
text
```
: Task description
```
date
```
: Due date for the task
```
assigned_to
```
: User ID of the assignee
```
is_complete
```
: Whether the task is completed

Pitfalls:

Tasks are associated with leads, not contacts
Date format should follow ISO 8601
assigned_to requires the Close user ID, not email or name
Tasks without a date appear in the 'no due date' section

适用场景：用户需要创建或管理跟进任务

工具流程:

```
CLOSE_CREATE_TASK
```
- 创建新任务 [必填]

关键参数:

```
lead_id
```
: 关联的线索ID
```
text
```
: 任务描述
```
date
```
: 任务截止日期
```
assigned_to
```
: 任务负责人的用户ID
```
is_complete
```
: 任务是否已完成

注意事项:

任务关联到线索，而非联系人
日期格式需遵循ISO 8601标准
assigned_to需填写Close用户ID，而非邮箱或姓名
未设置日期的任务会显示在“无截止日期”板块

5. Manage Notes

5. 管理笔记

When to use: User wants to add or retrieve notes on leads

Tool sequence:

```
CLOSE_GET_NOTE
```
- Retrieve a specific note [Required]

Key parameters:

```
note_id
```
: ID of the note to retrieve

Pitfalls:

Notes are associated with leads
Note IDs are required for retrieval; search leads first to find note references
Notes support plain text and basic formatting

适用场景：用户需要为线索添加或查看笔记

工具流程:

```
CLOSE_GET_NOTE
```
- 获取指定笔记 [必填]

关键参数:

```
note_id
```
: 要获取的笔记ID

注意事项:

笔记关联到线索
获取笔记必须提供note_id；需先搜索线索以找到笔记引用
笔记支持纯文本和基础格式

6. Delete Activities

6. 删除活动

When to use: User wants to remove call records or other activities

Tool sequence:

```
CLOSE_DELETE_CALL
```
- Delete a call activity [Required]

Key parameters:

```
call_id
```
: ID of the call to delete

Pitfalls:

Deletion is permanent and cannot be undone
Only the call creator or admin can delete calls
Deleting a call removes it from all reports and timelines

适用场景：用户需要删除通话记录或其他活动

工具流程:

```
CLOSE_DELETE_CALL
```
- 删除通话活动 [必填]

关键参数:

```
call_id
```
: 要删除的通话ID

注意事项:

删除操作不可逆，数据会永久清除
只有通话创建者或管理员有权限删除通话
删除通话会将其从所有报表和时间线中移除

Common Patterns

通用模式

Lead and Contact Relationship

线索与联系人关系

Close data model:
- Lead = Company/Organization
  - Contact = Person (nested within Lead)
  - Activity = Call, SMS, Email, Note (linked to Lead)
  - Task = Follow-up item (linked to Lead)
  - Opportunity = Deal (linked to Lead)

Close数据模型:
- Lead（线索）= 公司/组织
  - Contact（联系人）= 个人（嵌套在线索中）
  - Activity（活动）= 通话、短信、邮件、笔记（关联到线索）
  - Task（任务）= 跟进项（关联到线索）
  - Opportunity（商机）= 交易（关联到线索）

ID Resolution

ID解析

Lead ID:

1. Search for leads using the Close search API
2. Extract lead_id from results (format: 'lead_XXXXXXXXXXXXX')
3. Use lead_id in all activity creation calls

Contact ID:

1. Retrieve lead details to get nested contacts
2. Extract contact_id (format: 'cont_XXXXXXXXXXXXX')
3. Use in call/SMS activities for accurate tracking

线索ID:

1. 使用Close搜索API搜索线索
2. 从结果中提取lead_id（格式: 'lead_XXXXXXXXXXXXX'）
3. 在所有活动创建调用中使用该lead_id

联系人ID:

1. 获取线索详情以查看嵌套的联系人
2. 提取contact_id（格式: 'cont_XXXXXXXXXXXXX'）
3. 在通话/短信活动中使用以实现精准跟踪

Activity Logging Pattern

活动记录模式

1. Identify the lead_id and optionally contact_id
2. Create the activity (call, SMS, note) with lead_id
3. Include relevant metadata (duration, direction, status)
4. Create follow-up tasks if needed

1. 确定lead_id（可选contact_id）
2. 使用lead_id创建活动（通话、短信、笔记）
3. 包含相关元数据（时长、方向、状态）
4. 如有需要，创建跟进任务

Known Pitfalls

常见注意事项

ID Formats:

Lead IDs: 'lead_XXXXXXXXXXXXX'
Contact IDs: 'cont_XXXXXXXXXXXXX'
Activity IDs vary by type: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'
Custom field IDs: 'custom.cf_XXXXXXXXXXXXX'
Always use the full ID string

Rate Limits:

Close API has rate limits based on your plan
Implement delays between bulk operations
Monitor response headers for rate limit status
429 responses require backoff

Custom Fields:

Custom fields are referenced by their API ID, not display name
Different lead statuses may have different required custom fields
Custom field types (text, number, date, dropdown) enforce value formats

Data Integrity:

Leads are the primary entity; contacts and activities are linked to leads
Deleting a lead may cascade to its contacts and activities
Bulk operations should validate IDs before executing

ID格式:

线索ID: 'lead_XXXXXXXXXXXXX'
联系人ID: 'cont_XXXXXXXXXXXXX'
活动ID因类型而异: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'
自定义字段ID: 'custom.cf_XXXXXXXXXXXXX'
请始终使用完整的ID字符串

速率限制:

Close API根据你的套餐设置速率限制
批量操作之间需设置延迟
监控响应头中的速率限制状态
收到429响应时需执行退避策略

自定义字段:

自定义字段需通过API ID引用，而非显示名称
不同的线索状态可能需要不同的必填自定义字段
自定义字段类型（文本、数字、日期、下拉框）会强制要求对应的值格式

数据完整性:

线索是核心实体；联系人和活动都关联到线索
删除线索可能会级联删除其关联的联系人和活动
批量操作前应先验证ID的有效性

Quick Reference

快速参考

Task	Tool Slug	Key Params
Create lead	CLOSE_CREATE_LEAD	name, contacts, custom
Log call	CLOSE_CREATE_CALL	lead_id, direction, status, duration
Send SMS	CLOSE_CREATE_SMS	lead_id, text, direction
Create task	CLOSE_CREATE_TASK	lead_id, text, date, assigned_to
Get note	CLOSE_GET_NOTE	note_id
Delete call	CLOSE_DELETE_CALL	call_id

Powered by Composio

任务	工具标识	关键参数
创建线索	CLOSE_CREATE_LEAD	name, contacts, custom
记录通话	CLOSE_CREATE_CALL	lead_id, direction, status, duration
发送短信	CLOSE_CREATE_SMS	lead_id, text, direction
创建任务	CLOSE_CREATE_TASK	lead_id, text, date, assigned_to
获取笔记	CLOSE_GET_NOTE	note_id
删除通话	CLOSE_DELETE_CALL	call_id

由Composio提供支持