Claude Freshservice connectorWhat Claude can do in your Freshservice account.
The Claude Freshservice connector exposes 35 tools. 22 of them read your service desk, 11 create or update something in it, and 2 are documented nowhere. Below: what Claude finds, what it can log or change, what it asks before acting, and the limits.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach your service desk
Your IT service desk becomes something you can talk to. Ask Claude for the open tickets assigned to you, the details of one laptop in the asset list, or the knowledge article about VPN issues, and it answers from Freshservice. When something needs logging, a ticket, a note or a catalog request, it can do that too.
Triage without clicking through queues. fetchTickets and fetchTicket pull the tickets, fetchAgents lists the agents on the account, and createTicketNote adds a note to the right ticket once a cause is found.
Answer the question before it becomes a ticket. fetchSolutionArticleSearch finds the knowledge base article that already explains the fix, and fetchServiceCatalogItemSearch finds the catalog item someone should request.
Handle people moves. createOnboardingRequest and createOffboardingRequest open the requests when someone joins or leaves, and placeRequestServiceCatalogItem orders a catalog item, such as a software installation for a colleague.
What the connector does not do: run on its own. No tool fires when a ticket arrives or breaches a deadline; Claude only calls them while it answers you. Freshworks also documents no delete tool in the list. If tickets should be routed or created automatically from another system, that belongs to automation, covered on our Freshservice n8n integration and Freshservice Make integration pages. A different job, not a competing one.
Five words to know before you connect
The vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named action a connector gives Claude. Claude picks the tools it needs by itself, and the directory lists them by name.
- Authorization
- Freshservice's own sign-in page, where you complete the authentication that gives Claude its access. Per person, and revocable.
- Approval
- The confirmation Claude waits for in the conversation before it changes something in your service desk, such as a ticket.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Freshservice.
Connect Freshservice to Claude in three steps
- 01
Find Freshservice in your connectors
Open Claude's settings, go to Customize then Connectors, and look up Freshservice. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before members can each sign in.
- 02
Start the connection
Click Connect on the Freshservice row. You are redirected to the Freshservice authorization page, opened by Freshservice itself, to complete the sign-in. If the link breaks later, Disconnect and connect again.
- 03
Check the authorization screen
Read what the Freshservice screen grants before you accept: that screen, not Claude, sets the scope. If it announces wider permissions than Claude uses day to day, remember it is the service's own screen, and Claude still asks before each action by default.
The 35 tools, split by what they do
Freshservice gives Claude 35 tools: 22 that read your account, 11 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it creates or changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 22 read
- 11 write
- 2 not documented
What Claude reads (22)
22 toolsTwenty-two tools that look up tickets, assets, people, catalog items and knowledge articles without changing them.
fetchSolutionCategories
Returns the list of all categories in your knowledge base, the top level under which folders and articles are filed.
fetchSolutionCategory
Brings back one knowledge base category with its details, so Claude knows what it covers before going deeper.
fetchOnboardingRequestForm
Shows the fields of the onboarding request form, so Claude knows what information a new starter request expects.
fetchOffboardingRequestTickets
Returns the details of all the tickets attached to offboarding requests, the concrete tasks that follow a departure.
fetchServiceCatalogItemSearch
Searches the service catalog for items matching a term, so Claude can point to the right thing to request.
fetchOffboardingRequests
Lists every offboarding request with its details: the departures the service desk is currently handling.
fetchSolutionArticles
Pulls all the articles available in one knowledge base folder, a whole section of documentation in one go.
fetchSolutionArticleSearch
Searches knowledge base articles for a term, the quickest way to find whether a fix is already written down.
fetchServiceCatalogItem
Gives the details of one service catalog item, so Claude can explain what it includes before anyone requests it.
fetchServiceCatalogItems
Brings back every service catalog item with its details, the full menu of what employees can ask IT for.
fetchTicket
Opens a single ticket by its identifier and returns its details, so Claude reads the actual request rather than guessing.
fetchTickets
Gets the existing tickets, the base for any question about your queue, from open tickets assigned to you to trends over a period.
fetchAgent
Looks up one agent, the IT staff member who works tickets in Freshservice, and returns their details.
fetchAgents
Gets the agents associated with the account, the full roster of people who can work on tickets.
fetchAssets
Gets all the existing assets in Freshservice, the inventory of hardware and other items IT keeps track of.
fetchAsset
Retrieves a single asset by its identifier, with its details.
fetchSolutionFolder
Describes one knowledge base folder, the level between a category and its articles, with its details.
fetchSolutionArticle
Reads one knowledge base article in full, so Claude can quote or summarize the actual procedure.
fetchRequesters
Returns the requesters associated with the account, the employees who raise tickets and requests.
fetchRequester
Pulls up one requester, the person behind a ticket or a request, with their details.
fetchWorkspaces
Shows every workspace in your Freshservice account with its details, useful when several teams run their own service desk.
fetchSolutionFolders
Lists all the folders of one knowledge base category with their details, the map of one branch of your documentation.
What Claude changes (11)
11 toolsEleven tools that create or update records in your service desk. No source details a default confirmation per tool, so the general rule applies.
updateSolutionArticle
Approval: see the ruleUpdates an existing knowledge base article, for example to correct a procedure that changed.
createOnboardingRequest
Approval: see the ruleOpens an onboarding request in Freshservice, the starting point of everything IT prepares for a new hire.
createOffboardingRequest
Approval: see the ruleOpens an offboarding request, which starts the tasks that follow someone's departure.
placeRequestServiceCatalogItem
Approval: see the rulePlaces a request for a service catalog item, as an employee would from the portal.
createSolutionArticle
Approval: see the ruleAdds a new article to the knowledge base, so a fix found in a conversation becomes documentation the team can reuse.
createTicket
Approval: see the ruleOpens a new ticket in Freshservice, the classic entry point of any IT request or incident.
updateTicket
Approval: see the ruleChanges a ticket that already exists, for instance to set its status to resolved.
createAsset
Approval: see the ruleRegisters a new asset in the Freshservice inventory, so a piece of equipment is tracked from day one.
updateAsset
Approval: see the ruleEdits the record of an asset that already exists, so the inventory reflects what really happened to a device.
createTicketNote
Approval: see the ruleAdds a note to a ticket, for example an internal explanation of the cause found by the team.
createSolutionFolder
Approval: see the ruleCreates a new folder in the knowledge base, to give a set of articles a home.
Undocumented (2)
2 toolsThese two names are on the directory sheet, but no official source describes what they do.
fetchOnboardingRequests
The directory sheet lists this name and nothing else: no official source describes it, so this page does not guess what it does. Freshworks' help article is the only other source for this connector, and it has no line for this exact name either.
fetchServiceCatalogCategories
The directory lists this name, but no official source says what it returns, so this page says nothing more. Reading a capability into a tool name is exactly what we refuse to do here.
What Claude asks before it changes your service desk
Eleven tools write to Freshservice, and no source documents a confirmation specific to any of them.
By default, Claude asks for your confirmation before any action it takes on an account for you, shown in the conversation. No source says which permission level, Always allow, Needs approval or Blocked, each Freshservice tool starts on. On a Team or Enterprise workspace, owners decide what members may let through and can restrict the connector for the whole organization. Claude also works with your Freshservice rights and nothing beyond them.
Which plans include the Freshservice connector
None of the 819 directory sheets states availability by plan, so there is no official connector-by-connector answer from Anthropic.
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members sign in. Your Freshservice plan matters separately, since it sets your action allowance. For the Claude side, only the Freshservice sheet in the directory shows the current state.
What the connector will not do
This connector is documented by its publisher only: no Claude help article or Anthropic developer page covers it, so the limits below come from Freshworks.
A connector does not watch your queues: its tools only run while Claude answers you, never when a ticket arrives. The directory's verification badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools. Here the publisher is Freshworks, whose tool table describes each tool in one line. That is why all but two of the 35 tools have a clear sense on this page.
Need help connecting Freshservice to Claude?
A person reads every message.
