other
Sendy CLI for Shell Scripts
Use the Sendy CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.
5 functions 2 read 3 write API key auth
Sendy CLI for Shell Scripts
Call integration functions from shell scripts with stable JSON input and output.
Use shell scripts for small local automations that need one or more integration calls. The Sendy CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Sendy CLI for Shell Scripts
kosmokrator integrations:configure sendy --set api_key="$SENDY_API_KEY" --set hostname="$SENDY_HOSTNAME" --enable --read allow --write ask --json
kosmo integrations:call sendy.sendy_subscribe '{"list":"example_list","email":"example_email","name":"example_name"}' --json Discovery Before Execution
Agents and scripts can inspect Sendy docs and schemas before choosing a function.
kosmo integrations:docs sendy --json
kosmo integrations:docs sendy.sendy_subscribe --json
kosmo integrations:schema sendy.sendy_subscribe --json
kosmo integrations:search "Sendy" --json
kosmo integrations:list --json Useful Sendy CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
sendy.sendy_subscribe | Write | list, email, name | Subscribe an email address to a Sendy mailing list. Optionally provide a name and custom fields. |
sendy.sendy_unsubscribe | Write | list, email | Unsubscribe an email address from a Sendy mailing list. |
sendy.sendy_list_subscribers | Read | list_id | Get the total number of subscribers for a Sendy mailing list. |
sendy.sendy_create_campaign | Write | from_name, from_email, reply_to, title, subject, html_text, list_ids, plain_text, send_campaign, brand_id, query_string | Create a new email campaign in Sendy. You can create a draft or send immediately. Requires a list ID, subject, HTML content, and sender details. |
sendy.sendy_get_current_user | Read | none | Get the current brand/account information from Sendy. Useful for verifying credentials and retrieving brand details. |
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.