GLPI Sync
Tickets in sync between GLPI instances, in both directions
GLPI Sync connects two or more GLPI instances through the native REST API, with no middleware or scripts. Each remote instance has its own direction: outbound (a ticket opened here is created on the remote), inbound (every minute the module fetches new tickets from the remote and creates the mirror ticket here) or both. Followups, tasks, solutions and status follow the ticket, and the correlation between both sides prevents duplicates.
LicensedGLPI 11 and 12
Features
Filters decide what goes across: outbound, by category, entity, requester and group; inbound, by category, entity and assigned group of the remote ticket, with a cutoff date to import only from a given day. Default values for each side (entity, requester, category, groups, technician, location, type, urgency and more) and the mapping of requester, technician, groups and location complete the ticket on the other side. On import, the requester is matched by email.
A synced reply shows who answered on the other side. The Test Connection and Permissions button checks the token's profile on the remote GLPI and points out the missing permission. The connection verifies the remote GLPI's HTTPS certificate (with an option for self-signed certificates on internal networks). Credentials are encrypted (AES-256-GCM), temporary failures go back to a retry queue, and the Correlations and Logs tabs show every linked ticket and every run. With the Smart Notify module, the bell warns when a remote GLPI goes down, when a failure will not be retried and when synchronization stops running. A run interrupted midway resumes on its own.
How it works
Step 1
Enable the module
Enable GLPI Sync in the NexTool catalog. GLPI automatic actions must run through the command-line cron.
Step 2
Register the remote instance
Enter the URL and credentials of the remote GLPI, choose the direction (outbound, inbound or both) and use Test Connection and Permissions. If the remote GLPI uses a self-signed certificate (internal network), tick Accept self-signed certificate.
Step 3
Set filters, defaults and mappings
Choose what is sent or imported, the default values for each side and how entity, category, requester, technician, groups and location match.
Step 4
Done: tickets in sync
New tickets that match the filters are sent to the remote or imported from it, depending on the direction. Replies, solutions and status follow the ticket, with no duplicates.
See it in action
A quick tour of what the plugin does in practice.
Video demo coming soon.
Image gallery
Screenshots for this section are coming soon.