messaging
Gotify CLI for CI
Use the Gotify CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
5 functions 3 read 2 write API token auth
Gotify CLI for CI
Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.
Use this shape when a pipeline needs to read or update an external service. The Gotify CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Gotify CLI for CI
kosmokrator integrations:configure gotify --set app_token="$GOTIFY_APP_TOKEN" --set hostname="$GOTIFY_HOSTNAME" --enable --read allow --write ask --json
kosmo integrations:call gotify.gotify_list_messages '{"limit":1,"since":1}' --json Discovery Before Execution
Agents and scripts can inspect Gotify docs and schemas before choosing a function.
kosmo integrations:docs gotify --json
kosmo integrations:docs gotify.gotify_list_messages --json
kosmo integrations:schema gotify.gotify_list_messages --json
kosmo integrations:search "Gotify" --json
kosmo integrations:list --json Useful Gotify CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
gotify.gotify_list_messages | Read | limit, since | List messages from the Gotify application. Returns the most recent messages, with optional pagination using "since" to fetch messages newer than a given ID. |
gotify.gotify_create_message | Write | title, message, priority | Send a notification message via Gotify. The message body supports Markdown formatting. Use priority 0–4 for low, 5 for normal, and 6–10 for high priority. |
gotify.gotify_delete_message | Write | id | Delete a message from Gotify by its ID. Use the list_messages tool to find message IDs. |
gotify.gotify_get_health | Read | none | Check the health status of the Gotify server. Returns server health information including database status. |
gotify.gotify_get_current_user | Read | none | Get information about the currently authenticated Gotify user, including username and admin status. |
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.