Freshservice
for LuumenAI
Read Freshservice tickets for context, then make the queue changes you approve.
Connect Freshservice and Luumen can read your service desk directly from the terminal: ticket details, open queues, locations, service catalog items, and form field metadata for problems and releases. When you want a change — a new ticket, a service request, a batch of updates across a queue — Luumen shows the plan first and waits for your approval. Authentication is by API key.
The Freshservice toolbox
12 tools: 6 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Problem Form Fields by WorkspaceList problem form fields.
- ReadList Release Form FieldsList release form fields metadata.
- ReadGet Freshservice TicketRetrieve detailed information about a specific ticket by ID.
- ReadList Freshservice LocationsList all locations in Freshservice.
- ReadList Service Catalog ItemsList all service catalog items in Freshservice.
- ReadList Freshservice TicketsList all tickets in Freshservice with optional filtering and pagination.
- WriteBulk Update TicketsBulk update multiple Freshservice tickets by sequential update calls. Approval by default
- WriteCreate Service RequestCreate a service request for a catalog item in Freshservice using the v2 API. Approval by default
- WriteCreate TicketCreate a new ticket. Approval by default
- WriteDelete ReleaseDelete a release from Freshservice. Approval by default
- WriteDelete Solution ArticleDelete a solution article from the knowledge base by its ID. Approval by default
- WriteDelete Solution CategoryDelete a solution category in Freshservice. Approval by default
One prompt, start to finish
What a governed Freshservice run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — bulk update tickets, create service request, create ticket, delete release, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Freshservice — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Put Freshservice to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.