Use the Campaign Monitor CLI from KosmoKrator to call Campaign Monitor tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Campaign Monitor can be configured headlessly with `kosmokrator integrations:configure campaign-monitor`.
# 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 campaign-monitor --set api_key="$CAMPAIGN_MONITOR_API_KEY" --enable --read allow --write ask --jsonkosmokrator integrations:doctor campaign-monitor --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
CAMPAIGN_MONITOR_API_KEY
Secret secret
yes
API Key
url
CAMPAIGN_MONITOR_URL
URL url
no
API Base URL
Call Campaign Monitor 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 Campaign Monitor.
campaign-monitor.campaignmonitor_list_campaigns
Read read
List all email campaigns in your Campaign Monitor account. Returns campaign IDs, subjects, and status.
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.