scheduling
Cal.com CLI for CI
Use the Cal.com CLI for CI with headless JSON commands, schema discovery, credentials, and permission controls.
6 functions 5 read 1 write Bearer token auth
Cal.com 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 Cal.com CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Cal.com CLI for CI
kosmokrator integrations:configure cal --set access_token="$CAL_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call cal.cal_list_event_types '{"limit":1,"page":1,"teamId":1}' --json Discovery Before Execution
Agents and scripts can inspect Cal.com docs and schemas before choosing a function.
kosmo integrations:docs cal --json
kosmo integrations:docs cal.cal_list_event_types --json
kosmo integrations:schema cal.cal_list_event_types --json
kosmo integrations:search "Cal.com" --json
kosmo integrations:list --json Useful Cal.com CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
cal.cal_list_event_types | Read | limit, page, teamId | List available event types (booking link templates) from Cal.com. Supports filtering by team and pagination. |
cal.cal_get_event_type | Read | id | Get detailed information about a specific event type from Cal.com by its ID. |
cal.cal_list_bookings | Read | limit, page, status, eventTypeId | List bookings from Cal.com with optional filtering by status, event type, and pagination. |
cal.cal_get_booking | Read | id | Get detailed information about a specific booking from Cal.com by its ID. |
cal.cal_create_booking | Write | eventTypeId, start, end, responses | Create a new booking in Cal.com for a specific event type. Provide the event type, start/end times, and attendee information. |
cal.cal_get_current_user | Read | none | Get the authenticated Cal.com user's profile information, including name, email, and time zone. |
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.