Oo Kommo

Kommo

Operate Kommo through your OOMOL-connected account. This skill calls the kommo connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Kommo. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "kommo" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "kommo" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• get_account — Get Kommo account information for the connected account.
• get_company — Get one Kommo company by ID.
• get_contact — Get one Kommo contact by ID.
• get_lead — Get one Kommo lead by ID.
• get_pipeline — Get one Kommo lead pipeline by ID.
• get_task — Get one Kommo task by ID.
• get_user — Get one Kommo user by ID.
• list_companies — List companies from the connected Kommo account.
• list_contacts — List contacts from the connected Kommo account.
• list_leads — List leads from the connected Kommo account.
• list_pipelines — List lead pipelines from the connected Kommo account.
• list_tasks — List tasks from the connected Kommo account.
• list_users — List users from the connected Kommo account.

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Kommo state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Kommo is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=kommo
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Kommo homepage: https://www.kommo.com/