communication
OneSignal CLI for Cron Jobs
Use the OneSignal CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.
7 functions 6 read 1 write API key auth
OneSignal CLI for Cron Jobs
Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.
Use the headless CLI from cron when an operation should run without an interactive agent session. The OneSignal CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# OneSignal CLI for Cron Jobs
kosmokrator integrations:configure one-signal --set api_key="$ONE_SIGNAL_API_KEY" --set app_id="$ONE_SIGNAL_APP_ID" --enable --read allow --write ask --json
kosmo integrations:call one-signal.onesignal_list_notifications '{"app_id":"example_app_id","limit":1,"offset":1}' --json Discovery Before Execution
Agents and scripts can inspect OneSignal docs and schemas before choosing a function.
kosmo integrations:docs one-signal --json
kosmo integrations:docs one-signal.onesignal_list_notifications --json
kosmo integrations:schema one-signal.onesignal_list_notifications --json
kosmo integrations:search "OneSignal" --json
kosmo integrations:list --json Useful OneSignal CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
one-signal.onesignal_list_notifications | Read | app_id, limit, offset | List push notifications sent through OneSignal. Returns notification details including delivery stats, click counts, and outcomes. Use limit and offset for pagination. |
one-signal.onesignal_get_notification | Read | id, app_id | Get details of a specific OneSignal push notification by its ID. Returns full notification data including content, delivery stats, and targeting. |
one-signal.onesignal_create_notification | Write | app_id, contents, headings, included_segments, url, data | Send a new push notification via OneSignal. Specify message contents (per language), optional headings, target segments, a click URL, and a custom data payload. |
one-signal.onesignal_list_devices | Read | app_id, limit, offset | List devices (players) registered in a OneSignal app. Returns device identifiers, platform, session counts, and tags. Use limit and offset for pagination. |
one-signal.onesignal_get_device | Read | id, app_id | Get details of a specific OneSignal device (player) by its ID. Returns push token, platform, session data, tags, and more. |
one-signal.onesignal_list_apps | Read | none | List all OneSignal apps accessible with the configured REST API key. Returns app names, IDs, player counts, and configuration. |
one-signal.onesignal_get_current_app | Read | app_id | Get details of a specific OneSignal app by its ID. Returns app configuration, player counts, and platform settings. |
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.