productivity
Zapier CLI for Cron Jobs
Use the Zapier CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 7 read 0 write Bearer token auth
Zapier 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 Zapier CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Zapier CLI for Cron Jobs
kosmokrator integrations:configure zapier --set access_token="$ZAPIER_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call zapier.zapier_list_zaps '{"limit":1,"page":1}' --json Discovery Before Execution
Agents and scripts can inspect Zapier docs and schemas before choosing a function.
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 Useful Zapier CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
zapier.zapier_list_zaps | Read | limit, page | List zaps in Zapier with optional filters. |
zapier.zapier_get_zap | Read | id | Get detailed information about a Zapier zap. |
zapier.zapier_list_executions | Read | zap_id, limit, page | List zap executions in Zapier with optional filters. |
zapier.zapier_get_execution | Read | id | Get detailed information about a Zapier execution. |
zapier.zapier_list_connections | Read | limit, page | List connections in Zapier with optional filters. |
zapier.zapier_get_connection | Read | id | Get detailed information about a Zapier connection. |
zapier.zapier_get_current_user | Read | none | Get the currently authenticated Zapier user. |
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.