other
Freshservice CLI for Coding Agents
Use the Freshservice CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.
10 functions 7 read 3 write API key auth
Freshservice CLI for Coding Agents
Let coding agents discover schemas and execute integration functions through CLI commands or MCP.
Use this pattern when another coding agent needs exact commands and schema discovery. The Freshservice CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# Freshservice CLI for Coding Agents
kosmokrator integrations:configure freshservice --set api_key="$FRESHSERVICE_API_KEY" --set domain="$FRESHSERVICE_DOMAIN" --enable --read allow --write ask --json
kosmo integrations:call freshservice.freshservice_list_tickets '{"page":1,"per_page":1,"filter":"example_filter"}' --json Discovery Before Execution
Agents and scripts can inspect Freshservice docs and schemas before choosing a function.
kosmo integrations:docs freshservice --json
kosmo integrations:docs freshservice.freshservice_list_tickets --json
kosmo integrations:schema freshservice.freshservice_list_tickets --json
kosmo integrations:search "Freshservice" --json
kosmo integrations:list --json Useful Freshservice CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
freshservice.freshservice_list_tickets | Read | page, per_page, filter | List support tickets from Freshservice. Supports pagination and predefined filters (e.g., new_and_my_open, watching, spam, deleted). Returns ticket summaries including subject, status, priority, and requester. |
freshservice.freshservice_get_ticket | Read | ticket_id | Get full details of a specific Freshservice ticket by its ID, including description, status, priority, requester, assigned agent, and custom fields. |
freshservice.freshservice_create_ticket | Write | subject, description, email, priority | Create a new support ticket in Freshservice. Requires a subject and description. Optionally specify the requester email and priority (1=Low, 2=Medium, 3=High, 4=Urgent). |
freshservice.freshservice_update_ticket | Write | ticket_id, subject, description, priority, status, responder_id, tags | Update an existing Freshservice ticket. You can change status, priority, assigned agent, add tags, or modify any writable field. |
freshservice.freshservice_delete_ticket | Write | ticket_id | Delete a support ticket from Freshservice. This action permanently removes the ticket and its conversations. |
freshservice.freshservice_list_agents | Read | page | List all agents (support staff) in the Freshservice account. Returns agent profiles including name, email, and availability. |
freshservice.freshservice_get_agent | Read | agent_id | Get details of a specific Freshservice agent by their ID, including name, email, role, and availability status. |
freshservice.freshservice_list_assets | Read | page | List IT assets from Freshservice. Supports pagination. Returns asset summaries including name, asset type, and state. |
freshservice.freshservice_get_asset | Read | asset_id | Get full details of a specific Freshservice asset by its display ID, including name, type, state, location, and custom fields. |
freshservice.freshservice_get_current_user | Read | none | Get the profile of the currently authenticated Freshservice agent. Useful for identifying which agent is performing actions. |
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.