Integration · Freshservice
Connect Freshservice to meinGPT
Read tickets, requesters, assets, and solution articles and update tickets, replies, and private notes in a controlled way.
The native Freshservice connector gives an assistant controlled access to tickets, requesters, assets, agents, groups, departments, and solution articles. It can create and update tickets and add public replies or private notes. Every action uses the permissions of the Freshservice user who owns the configured API key.
An administrator stores the Freshservice account domain and a personal API key. The assistant resolves human-readable values such as status, priority, group, department, and agent to the IDs required by the account before writing. Attachments are listed first and loaded only after an explicit request.
- Source
- Freshservice
- Capability
- Search and update tickets, read requesters and assets, find solution articles, and add replies or notes
- Connection
- Freshservice domain and personal API key; the key owner's Freshservice permissions apply
- Data residency
- Freshservice data is read or written through API v2 for a concrete tool call. Attachments are loaded into chat only when explicitly requested.
Source, permissions, and data residency are documented separately for each connector.
Typical workflows
- Search and prioritise tickets
- Create and maintain tickets
- Prepare replies from service knowledge
What the integration makes possible
01
Search and prioritise tickets
Find tickets by state, priority, requester, or time period and return a focused triage list.
02
Create and maintain tickets
Create a reviewed ticket or update status, priority, assignment, category, and description using valid account values.
03
Prepare replies from service knowledge
Read the ticket, selected attachments, asset context, and relevant solution articles before drafting a public reply or private note.
Clarify before starting
- 01Freshservice domain and dedicated API user are available.
- 02The role grants only the required ticket and asset access.
- 03Rules for public replies, private notes, and ticket updates are defined.
Review the prompt and result openly
Find open high-priority tickets assigned to Workplace IT. Summarise the three oldest and draft a private note for the ticket that has had no update for the longest time.
Result
**3 tickets require attention.** The oldest ticket is FS-1042. A private note draft was prepared from the ticket history and asset context; no reply or update was submitted.
Does this connection fit your use case?
We clarify the source, permissions, and connection required for the concrete use case. If the existing integration fits, you can move straight to setup afterwards.
Security and operations
Use a dedicated Freshservice user with the smallest role required for the intended workflows, store the API key centrally, and rotate it according to the organisation's credential policy.
Known limitations
- 01Available fields and values vary by Freshservice account and must be resolved before writing.
- 02The connector uses a personal API key rather than per-user OAuth.
- 03Attachments are not transferred automatically; they must be selected explicitly.
Frequently asked questions
Yes. The connector can create tickets and update supported fields, using the permissions of the configured API user.