Skip to main content
The Kadoa CLI offers similar features to the MCP Server — workflow, monitor, notification, variable, template, and change operations available from your terminal, scripts, and CI/CD pipelines. It wraps the Node SDK and runs on Node 18+.

Prerequisites

Authentication

The CLI authenticates with OAuth. A tk-... API key is not a CLI token. kadoa login opens your browser, signs you in via Kadoa SSO, and stores the access + refresh tokens in ~/.kadoa/config.json (mode 0600). Tokens refresh automatically; you stay logged in until you kadoa logout. For non-interactive use, provide both KADOA_ACCESS_TOKEN and KADOA_REFRESH_TOKEN so the CLI can refresh the OAuth session.
Check your current auth status, active team, and role:

Quick Start

1

Log in

Authenticate via your browser — no API key required.
2

Create a workflow

Describe what to extract in natural language and point it at a URL.
3

Run it and fetch results

Trigger a run, then read the extracted data.
4

Export the dataset

Stream the full dataset to a file.

Commands

Global Options

Auth & Team

Workflows

kadoa create accepts the full flag set: --name, --entity, --description, --tag, --limit, --schedule, --cron, plus --notify-email/--notify-webhook/--notify-slack-channel/--notify-websocket to wire notifications at creation time. The list and get status field shows the computed workflow state (Complete, Running, Failed, Paused, Scheduled, etc.) — the same display the dashboard uses.

Data

export is the right choice for large workflows — it streams the full dataset rather than paginating.

Real-time Monitors

Real-time monitors watch a page and alert on changes. Each detected change is captured in the changes log.

Notifications

Notifications are split into channels (where alerts are delivered: email, webhook, Slack, WebSocket) and settings (which events route to which channels). notifications is aliased as notify. channels create flags depend on --type:
  • EMAIL--recipient <addr> (repeatable; omit for account default), --name <name>
  • WEBHOOK--url <url>, --method <method>, --auth-bearer <token> or --auth-basic <user:pass>
  • SLACK--slack-channel-id <id> or --slack-channel-name <name> (OAuth) or --slack-webhook <url> (legacy)
  • WEBSOCKET → no extra flags
configure mirrors the MCP configure_notifications tool — accepts --workflow, repeatable --event (or --event all), and the same --notify-* flags as kadoa create.

Variables

Variables are key/value pairs you reference in workflow prompts as @key. vars is aliased as variables.

Templates

Templates are reusable, versioned workflow configurations (prompt + schema + notifications).

Shell Completion

Tab-complete subcommands, flags, and workflow IDs:
Zsh shows workflow names inline: kadoa get <TAB> displays abc123 -- My Workflow.

Output Formatting

The CLI auto-detects the right format: tables in interactive terminals, JSON when piping or redirecting. Override with --json or --format.

CI/CD

Supply OAuth tokens via environment variables and the CLI runs non-interactively:

Permissions

The commands you can run depend on your team role. Viewers and Compliance Officers have read-only access — write operations return a 403 with a hint to contact your team admin. The permission matrix matches the MCP Server tool permissions.
Each command also accepts --help for the full flag list, e.g. kadoa create --help.