Can I use Zapier as a CLI?

Yes. KosmoKrator exposes a Zapier CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Zapier through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Zapier tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Zapier credentials stored?

Zapier credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Zapier MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Zapier CLI for AI Agents

Use the Zapier CLI from KosmoKrator to call Zapier tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Zapier CLI Setup

Zapier can be configured headlessly with `kosmokrator integrations:configure zapier`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure zapier --set access_token="$ZAPIER_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor zapier --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`ZAPIER_ACCESS_TOKEN`	Secret `secret`	yes	Access Token

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call zapier.zapier_list_zaps '{"limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:zapier zapier_list_zaps '{"limit":1,"page":1}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs zapier --json
kosmo integrations:docs zapier.zapier_list_zaps --json
kosmo integrations:schema zapier.zapier_list_zaps --json
kosmo integrations:search "Zapier" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`zapier.zapier_list_zaps`

List zaps in Zapier with optional filters.

Read read

Parameters: limit, page

Generic call

kosmo integrations:call zapier.zapier_list_zaps '{"limit":1,"page":1}' --json

Shortcut

kosmo integrations:zapier zapier_list_zaps '{"limit":1,"page":1}' --json

`zapier.zapier_get_zap`

Get detailed information about a Zapier zap.

Read read

Parameters: id

Generic call

kosmo integrations:call zapier.zapier_get_zap '{"id":"example_id"}' --json

Shortcut

kosmo integrations:zapier zapier_get_zap '{"id":"example_id"}' --json

`zapier.zapier_list_executions`

List zap executions in Zapier with optional filters.

Read read

Parameters: zap_id, limit, page

Generic call

kosmo integrations:call zapier.zapier_list_executions '{"zap_id":"example_zap_id","limit":1,"page":1}' --json

Shortcut

kosmo integrations:zapier zapier_list_executions '{"zap_id":"example_zap_id","limit":1,"page":1}' --json

`zapier.zapier_get_execution`

Get detailed information about a Zapier execution.

Read read

Parameters: id

Generic call

kosmo integrations:call zapier.zapier_get_execution '{"id":"example_id"}' --json

Shortcut

kosmo integrations:zapier zapier_get_execution '{"id":"example_id"}' --json

`zapier.zapier_list_connections`

List connections in Zapier with optional filters.

Read read

Parameters: limit, page

Generic call

kosmo integrations:call zapier.zapier_list_connections '{"limit":1,"page":1}' --json

Shortcut

kosmo integrations:zapier zapier_list_connections '{"limit":1,"page":1}' --json

`zapier.zapier_get_connection`

Get detailed information about a Zapier connection.

Read read

Parameters: id

Generic call

kosmo integrations:call zapier.zapier_get_connection '{"id":"example_id"}' --json

Shortcut

kosmo integrations:zapier zapier_get_connection '{"id":"example_id"}' --json

`zapier.zapier_get_current_user`

Get the currently authenticated Zapier user.

Read read

Parameters: none

Generic call

kosmo integrations:call zapier.zapier_get_current_user '{}' --json

Shortcut

kosmo integrations:zapier zapier_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

zapier.zapier_list_zaps 2 parameters

Schema command

kosmo integrations:schema zapier.zapier_list_zaps --json

Parameter	Type	Required	Description
`limit`	integer	no	Max number of zaps to return.
`page`	integer	no	Page number for pagination.

zapier.zapier_get_zap 1 parameters

Schema command

kosmo integrations:schema zapier.zapier_get_zap --json

Parameter	Type	Required	Description
`id`	string	yes	The zap ID.

zapier.zapier_list_executions 3 parameters

Schema command

kosmo integrations:schema zapier.zapier_list_executions --json

Parameter	Type	Required	Description
`zap_id`	string	no	Filter executions by zap ID.
`limit`	integer	no	Max number of executions to return.
`page`	integer	no	Page number for pagination.

zapier.zapier_get_execution 1 parameters

Schema command

kosmo integrations:schema zapier.zapier_get_execution --json

Parameter	Type	Required	Description
`id`	string	yes	The execution ID.

zapier.zapier_list_connections 2 parameters

Schema command

kosmo integrations:schema zapier.zapier_list_connections --json

Parameter	Type	Required	Description
`limit`	integer	no	Max number of connections to return.
`page`	integer	no	Page number for pagination.

zapier.zapier_get_connection 1 parameters

Schema command

kosmo integrations:schema zapier.zapier_get_connection --json

Parameter	Type	Required	Description
`id`	string	yes	The connection ID.

zapier.zapier_get_current_user 0 parameters

Schema command

kosmo integrations:schema zapier.zapier_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.