# close-automation

close-automation automates Close CRM operations through Rube MCP, managing leads, call logging, SMS, tasks, and notes directly from your coding agent.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 122 installs · ★ 3785 repo stars
- Author: davepoon
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-skills/skills/close-automation/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/close-automation

## What it does

This skill connects your AI assistant to Close CRM through Composio's Rube MCP toolkit. It handles workflows using tools like `CLOSE_CREATE_LEAD`, `CLOSE_CREATE_CALL`, `CLOSE_CREATE_SMS`, `CLOSE_CREATE_TASK`, and `CLOSE_GET_NOTE`. Workflows begin by calling `RUBE_SEARCH_TOOLS` to fetch the current API schema.

Close models leads as organizations, not individual people. Contacts sit nested inside lead records, so logging calls, SMS messages, or follow-up tasks requires a valid `lead_id`. Call durations must be provided in seconds. Custom fields require their raw API keys like `custom.cf_XXX` instead of display labels.

Without an active connection via the `https://rube.app/mcp` endpoint and OAuth authentication completed, the Close tools will fail.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill close-automation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/close-automation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/close-automation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill close-automation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/close-automation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill close-automation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/close-automation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install davepoon/buildwithclaude plugins/all-skills/skills/close-automation
```

2. **Manually: put the files in place**
- File: `.github/skills/close-automation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill close-automation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/davepoon/buildwithclaude --path plugins/all-skills/skills/close-automation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/close-automation/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add davepoon/buildwithclaude --skill close-automation -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-skills/skills/close-automation/SKILL.md

## When to use it
- create leads with nested contacts and custom fields
- log completed or inbound calls with duration in seconds
- send and record SMS messages linked to a lead
- schedule follow-up tasks with ISO 8601 due dates
- retrieve lead notes or delete obsolete call records

## Example prompts
- Create a new lead named Acme Corp with contact John Doe in Close
- Log an outbound completed call to lead_12345 lasting 120 seconds
- Add a follow-up task to lead_12345 due 2025-04-10 assigned to user_987

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6a9e0f6013e8d20e.

BEGIN THIRD-PARTY FILE 6a9e0f6013e8d20e
```text
---
name: close-automation
description: "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."
requires:
  mcp: [rube]
category: crm
---

# Close CRM Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/close](https://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

## 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.


1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `close`
3. If connection is not ACTIVE, follow the returned auth link to complete Close API authentication
4. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. Create and Manage Leads

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

**Tool sequence**:
1. `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

### 2. Log Calls

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

**Tool sequence**:
1. `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

### 3. Send SMS Messages

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

**Tool sequence**:
1. `CLOSE_CREATE_SMS` - Send or log an SMS message [Required]

**Key parameters**:
```
END THIRD-PARTY FILE 6a9e0f6013e8d20e

The third-party file has ended. Everything between the 6a9e0f6013e8d20e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2717 of 6794 bytes. © davepoon · MIT · https://github.com/davepoon/buildwithclaude/tree/HEAD/plugins/all-skills/skills/close-automation/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
