Can I use Customer.io as a CLI?

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

Can I expose Customer.io through MCP?

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

Where are Customer.io credentials stored?

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

Can I deny write access for Customer.io MCP tools?

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

marketing

Customer.io CLI for Headless Automation

Use the Customer.io CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write API key auth

Submit Customer.io feedback View package source

Customer.io CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Customer.io CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Customer.io CLI for Headless Automation
kosmokrator integrations:configure customerio --set api_key="$CUSTOMERIO_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call customerio.customerio_identify_customer '{"id":"example_id","email":"example_email","name":"example_name","attributes":"example_attributes"}' --json

Discovery Before Execution

Agents and scripts can inspect Customer.io docs and schemas before choosing a function.

kosmo integrations:docs customerio --json
kosmo integrations:docs customerio.customerio_identify_customer --json
kosmo integrations:schema customerio.customerio_identify_customer --json
kosmo integrations:search "Customer.io" --json
kosmo integrations:list --json

Useful Customer.io CLI Functions

Function	Type	Parameters	Description
`customerio.customerio_identify_customer`	Write	id, email, name, attributes	Create or update a customer profile in Customer.io. Use this to add new customers or update existing customer attributes like email, name, and custom properties.
`customerio.customerio_track_event`	Write	id, name, data	Track a custom event for a customer in Customer.io. Events trigger campaign workflows and can be used to segment customers.
`customerio.customerio_list_segments`	Read	none	List all segments in the Customer.io workspace. Segments are dynamic groups of customers defined by conditions.
`customerio.customerio_list_campaigns`	Read	none	List all campaigns in the Customer.io workspace. Campaigns are automated message sequences triggered by events or segments.
`customerio.customerio_get_campaign`	Read	id	Get detailed information about a specific campaign in Customer.io, including its triggers, actions, and performance metrics.
`customerio.customerio_list_newsletters`	Read	none	List all newsletters in the Customer.io workspace. Newsletters are one-time broadcast messages sent to segments.
`customerio.customerio_get_current_user`	Read	none	Get the currently authenticated user and account information from Customer.io. Useful for verifying API credentials and checking workspace details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Customer.io CLI Pages

CI Customer.io CLI for CI. Cron Jobs Customer.io CLI for cron jobs. Shell Scripts Customer.io CLI for shell scripts. Coding Agents Customer.io CLI for coding agents.