Observed since 20 Oct, 23:33 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
Agent-ready command-line interface for Close CRM — set up leads, keep contacts and notes current, track tasks and opportunities, and search across all of it. Installs the `close` command.
Set up leads, keep contacts and notes current, track tasks and opportunities, and search across all of it — a Close CRM client an LLM can drive with no prior knowledge of it.
Install: pipx install agent-tool-close-crm-cli — then run close guide.
close wraps the Close CRM REST API in a command
line built for AI agents: JSON on stdout by default, errors as JSON on stderr
with a meaningful exit code, a built-in guide that needs no network, and
--dry-run on every write. Point an agent at a website and let it stand a lead
up end to end — company, contacts, notes, a first task and an opportunity — then
keep it current, search across everything, and see what happened last.
Usage: close [OPTIONS] COMMAND [ARGS]...
Agent-friendly CLI for Close CRM: set up leads, keep contacts current, log notes
and calls, create and reschedule tasks and opportunities, and search across all of
it.
Output is JSON on stdout by default (errors are JSON on stderr with a non-zero
exit code); add `-o table` or trim with `--fields id,name`.
New here / no context? Run `close guide` for the full playbook.
╭─ Options ────────────────────────────────────────────────────────────────────────╮
│ --output -o <json|table|markdown|csv> Output format: json │
│ (default), table, │
│ markdown, csv. Also │
│ --format/-f, anywhere on │
│ the line. │
│ --fields,--columns <str> Comma-separated fields to │
│ return, e.g. │
│ 'id,display_name'. Works │
│ anywhere on the line. │
│ --profile -p <str> Configuration profile. │
│ One profile per Close API │
│ key (e.g. a second org). │
│ --dry-run Mutating commands: print │
│ the request that would be │
│ sent and exit. │
│ --stream Stream results as NDJSON. │
│ --no-context Ignore the saved session │
│ context for this command. │
│ --no-color Disable coloured output. │
│ --version -V Show version and exit. │
│ --help Show this message and │
│ exit. │
╰──────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────────────────────────────╮
│ guide Built-in operating guide — how to use this CLI without external │
│ report Report a bug / missing feature — repo + pre-filled issue link. │
│ docs. │
│ lead Leads (accounts): create, read, search, update, set status. │
│ status Discover the org's lead and opportunity statuses. │
│ contact Contacts (people at a lead): add, update, list. │
│ activity Timeline: log notes, document calls, see what happened last. │
│ task Tasks: create, see what's open, reschedule, complete. │
│ opportunity Opportunities (deals): set up, list, move close dates, win/lose. │
│ search Clever search across leads, contacts, opportunities and tasks. │
│ auth Log in with an API key, log out, inspect credentials. │
│ raw Escape hatch: call any Close API endpoint directly. │
│ settings View & change CLI settings. │
│ context Sticky session defaults (e.g. a lead), applied to later commands. │
│ install Integrate with other tools (e.g. `install claude`). │
╰──────────────────────────────────────────────────────────────────────────────────╯
Learn more: `close guide` · `close guide <topic>` · `close <group> --help`
Typed, name-resolving commands cover leads, contacts, activities (notes & calls), tasks, opportunities, statuses and search — pass a name, not an id (
--lead "Acme Inc",-s Qualified), and preview any write with--dry-run.close rawstill reaches anything not yet wrapped. Runclose guidefor the full map.
pipx install agent-tool-close-crm-cli
close auth login # paste an API key from app.close.com/settings/api/
# ...or run headless, no config file:
export CLOSE_API_KEY=api_xxxxxxxx
close guide # the built-in manual — no network needed
# stand a whole account up from a website:
close lead create -n "Acme Inc" --url https://acme.com -s Qualified
close contact add --lead "Acme Inc" -n "Jane Doe" --title CTO --email jane@acme.com
close activity note "Inbound from the website form." --lead "Acme Inc"
close task create "Book a demo" --lead "Acme Inc" --due +3d
close opportunity create --lead "Acme Inc" --value 5000 -s "Demo Completed" --close +4w
# then keep it moving:
close activity recent --lead "Acme Inc" # what happened last on this account
close task list --overdue # what's slipping
close opportunity reminders --within 14d # deals closing soon
close search leads 'status:"Qualified"' # clever search
An agent-ready CLI is one an LLM with no prior knowledge of the tool can discover, drive correctly, and know whether it worked — without a human in the loop. Concretely:
close … | jq never breaks; human status goes to stderr.{"error": "...", "status": 404} on stderr,
and a 422 carries fieldErrors — the exact fields Close rejected, as dotted
paths (contacts.0.emails.0.email) — so a rejected write is fixable on the next call.close guide is a zero-config, zero-network, offline
manual compiled into the binary; close install claude registers it as a Claude Code skill.--dry-run prints the exact request and sends nothing.| Object | Id prefix | What |
|---|---|---|
| Lead | lead_ | A company/account — the central object; everything hangs off it. Has a status. |
| Contact | cont_ | A person at a lead — names, emails, phones. |
| Activity | acti_ | The lead's timeline: notes, calls, emails, SMS, status changes. "What happened last." |
| Task | task_ | A to-do with a due date. "Open tasks" = incomplete ones due. |
| Opportunity | oppo_ | A potential deal: value, confidence, a pipeline status (active/won/lost), a close date. |
| Status | stat_ | Lead & opportunity statuses — per-org and custom; resolve them, never hard-code. |
Lists return {"data": [...], "has_more": ..., "total_results": N}; page with
_skip/_limit (max 100). Updates are PUT (partial — send only what changed).
Default output is JSON on stdout; add -o table for humans, -o csv to export,
--fields id,display_name to trim, --stream for NDJSON. Errors are JSON on
stderr with a non-zero exit code:
| Code | Meaning | Code | Meaning | |
|---|---|---|---|---|
| 0 | success (incl. a --dry-run) | 5 | not found | |
| 1 | generic error | 6 | conflict | |
| 3 | config (no API key) | 7 | validation — see fieldErrors | |
| 4 | auth (bad/insufficient key) | 130 | interrupted |
Codes 0–7 mean the same thing across every tool in the family.
A Close API key (starts with api_), minted at
app.close.com/settings/api/. The key is
the org selector — there is no server URL to configure.
close auth login # prompts, verifies against /me/, stores in your OS keyring
export CLOSE_API_KEY=api_xxxxxxxx # or headless, no config file
close auth status # names WHICH key/backend is actually in use
Precedence is env > OS keyring > 0600 file; a second Close org is a second
profile (close auth login --profile client-x).
close is built on agent-tool-shared-cli,
the shared chassis that fixes the output format, the exit-code taxonomy and the
credential handling — so an agent that has learned one tool in the family already
knows the next.
| Tool | Install | For |
|---|---|---|
| close | pipx install agent-tool-close-crm-cli | Close CRM — leads, contacts, notes, tasks, opportunities, search |
| drone-cli | pipx install agent-tool-drone-cli | Drone CI — builds, failing-step logs, promotions |
| grafana | pipx install agent-tool-grafana-cli | Grafana — log discovery, health scan, alert routing |
| openproject | pipx install agent-tool-openproject-cli | OpenProject — work packages, time, invoicing |
| lexware-office | pipx install agent-tool-lexware-office-cli | Lexware Office — invoices, contacts, AR-aging |
Keywords: Close CRM CLI, Close.com API, sales CRM command line, leads, contacts, sales opportunities, sales pipeline, tasks, CRM automation, AI agent tool, LLM tooling, Claude.
MIT — see LICENSE.
Download counts and popularity will appear here as the collector receives them.
| Version | Published | Direct dependencies | Open version |
|---|---|---|---|
| 0.2.1 | 20 Jul 2026 | 8 |
This describes our collected data; it is not a security assessment.
Shared repository data · GitHub
Observed since 20 Oct, 23:33 UTC
No superseded metadata states collected. Unchanged observations do not create new revisions.
package:f8548bf8362d5ca2a190cc4a3c174ac424971804a314e60f3fb3590d9fd72906