Use the Drip CLI from KosmoKrator to call Drip tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Drip can be configured headlessly with `kosmokrator integrations:configure drip`.
# 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 drip --set api_key="$DRIP_API_KEY" --set account_id="$DRIP_ACCOUNT_ID" --enable --read allow --write ask --jsonkosmokrator integrations:doctor drip --jsonkosmokrator integrations:status --json
Credentials
Authentication type: API keyapi_key. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
api_key
DRIP_API_KEY
Secret secret
yes
API Key
account_id
DRIP_ACCOUNT_ID
Text string
yes
Account ID
url
DRIP_URL
URL url
no
Drip API URL
Call Drip Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Drip.
drip.drip_list_campaigns
Read read
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.
Fetch a single email campaign from Drip by its campaign ID. Returns full campaign details including name, status, configuration, and associated actions.
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.
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.
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.
Fetch a single workflow from Drip by its workflow ID. Returns full workflow details including name, status, trigger configuration, and associated actions.
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.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
drip.drip_list_campaigns
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.
Number of results per page, max 1000 (default: 100).
drip.drip_get_campaign
Fetch a single email campaign from Drip by its campaign ID. Returns full campaign details including name, status, configuration, and associated actions.
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.
Number of results per page, max 1000 (default: 100).
drip.drip_get_subscriber
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.
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.
Number of results per page, max 1000 (default: 100).
drip.drip_get_workflow
Fetch a single workflow from Drip by its workflow ID. Returns full workflow details including name, status, trigger configuration, and associated actions.
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.
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.