communication
Wildix CLI for CI
Use the Wildix CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
6 functions 6 read 0 write Bearer token auth
Wildix 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 Wildix CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Wildix CLI for CI
kosmokrator integrations:configure wildix --set access_token="$WILDIX_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call wildix.wildix_list_calls '{"limit":1,"page":1,"date_from":"example_date_from","date_to":"example_date_to"}' --json Discovery Before Execution
Agents and scripts can inspect Wildix docs and schemas before choosing a function.
kosmo integrations:docs wildix --json
kosmo integrations:docs wildix.wildix_list_calls --json
kosmo integrations:schema wildix.wildix_list_calls --json
kosmo integrations:search "Wildix" --json
kosmo integrations:list --json Useful Wildix CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
wildix.wildix_list_calls | Read | limit, page, date_from, date_to | List call records from the Wildix PBX. Supports pagination and optional date range filtering to narrow results by period. |
wildix.wildix_get_call | Read | id | Get detailed information about a specific call record by its ID. |
wildix.wildix_list_extensions | Read | limit, page | List PBX extensions configured in the Wildix system. Supports pagination. |
wildix.wildix_get_extension | Read | id | Get detailed information about a specific PBX extension by its ID. |
wildix.wildix_list_users | Read | limit, page | List users configured in the Wildix PBX system. Supports pagination. |
wildix.wildix_get_current_user | Read | none | Get the profile of the currently authenticated Wildix user (the user associated with the configured access token). |
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.