crm
Copper CRM CLI for Cron Jobs
Use the Copper CRM CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.
13 functions 8 read 5 write API key auth
Copper CRM CLI for Cron Jobs
Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.
Use the headless CLI from cron when an operation should run without an interactive agent session. The Copper CRM CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Copper CRM CLI for Cron Jobs
kosmokrator integrations:configure copper --set api_key="$COPPER_API_KEY" --set email="$COPPER_EMAIL" --enable --read allow --write ask --json
kosmo integrations:call copper.copper_list_contacts '{"page_size":1,"sort_by":"example_sort_by"}' --json Discovery Before Execution
Agents and scripts can inspect Copper CRM docs and schemas before choosing a function.
kosmo integrations:docs copper --json
kosmo integrations:docs copper.copper_list_contacts --json
kosmo integrations:schema copper.copper_list_contacts --json
kosmo integrations:search "Copper CRM" --json
kosmo integrations:list --json Useful Copper CRM CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
copper.copper_list_contacts | Read | page_size, sort_by | Search and list contacts in Copper CRM. Returns contact names, emails, and IDs. |
copper.copper_get_contact | Read | id | Get details of a specific contact in Copper CRM by ID. |
copper.copper_create_contact | Write | name, email | Create a new contact in Copper CRM. Provide at least a name. |
copper.copper_update_contact | Write | id, name, email | Update an existing contact in Copper CRM. Only the fields provided will be updated. |
copper.copper_delete_contact | Write | id | Delete a contact from Copper CRM. This action cannot be undone. |
copper.copper_list_companies | Read | page_size, sort_by | Search and list companies in Copper CRM. Returns company names, domains, and IDs. |
copper.copper_get_company | Read | id | Get details of a specific company in Copper CRM by ID. |
copper.copper_create_company | Write | name | Create a new company in Copper CRM. |
copper.copper_list_opportunities | Read | page_size, sort_by | Search and list opportunities (deals) in Copper CRM. Returns opportunity names, values, stages, and IDs. |
copper.copper_get_opportunity | Read | id | Get details of a specific opportunity (deal) in Copper CRM by ID. |
copper.copper_create_opportunity | Write | name, pipeline_id | Create a new opportunity (deal) in Copper CRM. Provide a name and pipeline ID. Use copper_list_pipelines first to find available pipeline IDs. |
copper.copper_list_pipelines | Read | none | List all sales pipelines in Copper CRM. Each pipeline contains stages that opportunities move through. |
copper.copper_get_current_user | Read | none | Get the currently authenticated Copper CRM user. Useful for verifying the connection and account context. |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.