Docs
CRM

CRM

Read and write the workspace's CRM from the command line, across people, companies, pipelines, lists, tags, notes, and tasks.

Query and edit the lead database and deal pipelines from scripts and automations. Every command talks to the CRM external API (/v1/crm/*) and respects the active workspace. The workspace must have CRM access, or these commands return a 403.

Commands follow a geni crm <noun> <verb> shape. Each noun is a group: some default to a search or list when you omit the verb (people, companies, lists, tags, tasks, pipelines, campaigns, sequences), others are pure verb groups (notes, stages, cards, touchpoints, fields, employments, contact-points). The full surface reads and writes: create, update, delete, move cards, log touchpoints, manage list members and tags, edit stages and custom fields, and manage campaigns and their sequence drafts.

Conventions

  • Creates and updates take their body as --json. People and companies expect a JSON array (batch find-or-create and batch update); most other nouns take a single JSON object. Notes use --body instead.
  • Output is human-readable tables by default. Pass --json for machine-readable output, or --field <path> on the single-record get commands to print one dotted-path value.
  • Card mutations (move, status, update) accept --expected-updated-at for optimistic concurrency. Omit it and the CLI fetches the card's current version first (last-write-wins).

Nouns

On this page