Connect GLPI to Persyst: API, tickets and access
Prepare the GLPI API, connect a technical account and share tickets by entity and group from your AI assistant.
Persyst lets authorized members consult GLPI tickets from ChatGPT, Claude or an MCP-compatible assistant. An administrator connects a shared technical account and defines the scopes and tools available to each recipient.
The connector reads GLPI 10 and 11 through the legacy REST V1 API. It does not create or update tickets or download attachments. Connecting the account alone does not share any tickets.
Prepare GLPI
Ask your GLPI administrator to prepare the following:
- In Setup → General → API, enable the legacy REST API and external token authentication. On GLPI 11, this is V1, not the OAuth V2 API.
- Create an API client dedicated to Persyst and copy its App-Token. If IP restrictions are configured, ask your Persyst operator for the deployment’s outbound addresses and allow them.
- Prepare an active technical account with a dedicated read profile and only the required entities and data. Obtain its user API token from personal preferences or its user record, depending on the available permissions.
- Check the timezone configured in GLPI, such as
Europe/ParisorUTC.
The GLPI account and profile limit which data can be read. Persyst permissions then determine what each member can consult using that shared connection; reads do not use the member’s personal GLPI identity.
Publisher references: API configuration and legacy REST V1 API.
Connect the account in Persyst
- As an organization administrator, open Data sources → Add a source → GLPI.
- Enter the instance’s HTTPS URL, for example
https://glpi.example.org/support, a connection name, timezone and both tokens. Use the instance URL; Persyst handles theapirest.phppath. - Click Test connection. If several profiles are available, explicitly select the read profile and test again to check the accessible entities.
- Click Connect GLPI, then choose the scopes to share.
Tokens are encrypted on the server. Enter them only in the Persyst form, never in a conversation with your assistant. The HTTPS URL must be reachable from Persyst. An instance on a private network requires explicit configuration by your Persyst operator; entering its URL is not enough.
Choose scopes and access
A scope covers one specific entity, using one of these modes:
| Mode | Included tickets |
|---|---|
| Tickets assigned to selected groups | Tickets in this entity assigned to at least one selected group |
| All tickets in this entity, including unassigned | Tickets in this entity that the technical account can read |
Select the entity, mode and any groups, name the scope, then click Add scope and Finish. Child entities and new groups are not added automatically. A requester or observer group is not an assigned group.
In Access management, grant the scopes and tools to the relevant people, teams or clients. Adding a scope alone does not grant access. See Members and access for this step.
Choose allowed tools
| Tool | Purpose |
|---|---|
list_glpi_sources | Identify authorized scopes and their Persyst identifiers |
search_glpi_tickets | Search and filter tickets within those scopes |
read_glpi_ticket | Read an authorized ticket’s content |
read_glpi_ticket_timeline | Read public follow-ups and tasks, and accessible solutions |
read_glpi_ticket_private_timeline | Read private follow-ups and tasks with a separate permission |
get_glpi_ticket_stats | Count and group tickets within the covered results |
The private timeline is disabled by default. It requires explicit enablement and a grant in Persyst, plus the corresponding GLPI permissions for the technical account. Granting the public timeline does not grant access to private notes.
Ask your assistant
After connecting your assistant, start with a question about an authorized scope:
In GLPI, find high-priority tickets still open for the Network group over the last seven days. Give their references and statuses, then summarize the ticket I choose.
The assistant starts with list_glpi_sources and uses the returned Persyst identifiers to search and read. These differ from GLPI entity or ticket identifiers. Search supports text, statuses, priority, assigned groups and a date range with timezone information, among other filters.
A search returns up to 50 tickets per page. If a continuation cursor is present, follow the required pages. A response marked partial, truncated, or statistics with exact: false, is not an exhaustive total. Long content may also require continuation. The connector does not expose a complete asset inventory, attachments or unrestricted API access.
Check and maintain the connection
- Check a known ticket with an authorized member, then confirm that a member without access cannot see the scope. Tool calls are logged in Persyst.
- If no tickets appear, check the GLPI account’s profile and entity, the scope mode and assigned groups, then the scope and tool grants in Persyst.
- If the test fails, check the legacy API, both tokens, profile, HTTPS certificate and network or IP restrictions.
- To rotate tokens, open Source connection → Replace tokens using the same account and profile. Scopes and grants are preserved; secrets are never displayed again.
- To change the instance, account, profile or timezone, create a new connection, reassign access and remove the old one.