marketing
Drip CLI for Coding Agents
Use the Drip CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 7 read 0 write API key auth
Drip CLI for Coding Agents
Let coding agents discover schemas and execute integration functions through CLI commands or MCP.
Use this pattern when another coding agent needs exact commands and schema discovery. The Drip CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Drip CLI for Coding Agents
kosmokrator integrations:configure drip --set api_key="$DRIP_API_KEY" --set account_id="$DRIP_ACCOUNT_ID" --enable --read allow --write ask --json
kosmo integrations:call drip.drip_list_campaigns '{"page":1,"per_page":1}' --json Discovery Before Execution
Agents and scripts can inspect Drip docs and schemas before choosing a function.
kosmo integrations:docs drip --json
kosmo integrations:docs drip.drip_list_campaigns --json
kosmo integrations:schema drip.drip_list_campaigns --json
kosmo integrations:search "Drip" --json
kosmo integrations:list --json Useful Drip CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
drip.drip_list_campaigns | Read | page, per_page | List email campaigns in your Drip account. Returns campaign details including name, status, and configuration. Paginated — use page and per_page parameters to navigate results. |
drip.drip_get_campaign | Read | id | Fetch a single email campaign from Drip by its campaign ID. Returns full campaign details including name, status, configuration, and associated actions. |
drip.drip_list_subscribers | Read | page, per_page | List subscribers in your Drip account. Returns subscriber records including email, status, tags, and custom fields. Paginated — use page and per_page parameters to navigate results. |
drip.drip_get_subscriber | Read | id | Fetch a single subscriber from Drip by their subscriber ID or email address. Returns full subscriber details including status, tags, custom fields, and subscription information. |
drip.drip_list_workflows | Read | page, per_page | List workflows in your Drip account. Returns workflow details including name, status, and trigger configuration. Paginated — use page and per_page parameters to navigate results. |
drip.drip_get_workflow | Read | id | Fetch a single workflow from Drip by its workflow ID. Returns full workflow details including name, status, trigger configuration, and associated actions. |
drip.drip_get_current_user | Read | none | Get the currently authenticated Drip user. Returns user profile information including name, email, and account details. Useful for verifying the API connection and identifying which account is active. |
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.