Automations (Webhooks)

Connect GLPI to any system with webhooks and automations

The Automations module connects GLPI to other systems through flows, each with a trigger, a data mapping and an action. The trigger can be a webhook called by another system, a ticket event in GLPI (created, updated or status changed) or a schedule; the action can open, update, assign or close tickets, among others, or call the API of an external system such as n8n, Power Automate, Jira or ServiceNow.

On-demandGLPI 11 and 12

View plans

Features

On the inbound side, each flow gets its own URL, protected by an HMAC SHA-256 signature, a per-minute request limit and a lockout after invalid attempts. The received JSON is mapped to GLPI fields, with built-in conversions: an email becomes a user, a name becomes a category or entity and a written priority becomes GLPI's, and the action runs as a service user. On the outbound side, connectors store each system's URL and encrypted credential, and the call builds its body from the ticket data.

A chain runs several actions in sequence, with if and else conditions. When a call to an external system fails in a webhook flow, the module tries again up to 3 times, at increasing intervals. Every run is logged, with filters by date, status, flow and action.

Inbound webhook with its own URL per flow, HMAC SHA-256 signature and a per-minute request limit

Trigger on ticket events: created, updated or status changed, with filters by entity, category and type

Scheduled flows, from every 5 minutes up to once a day

Mapping of the JSON to GLPI fields, converting an email into a user and a name into a category or entity

Actions in GLPI: open, update, assign and close tickets, add a follow-up, task, document or approval request, and create a Problem or Change

Connectors for n8n, Power Automate, Jira, ServiceNow, Zendesk, Slack, Teams and more, plus a custom one for any REST API

Connector credentials encrypted in the database and masked on screen

Chain of actions in sequence, with if and else conditions

Log of every run, with filters by date, status, flow and action

How it works

Step 1

Create the flow

In the visual wizard, choose the trigger (webhook, ticket event or schedule), map the fields and set the action.

Step 2

Connect the other system

To receive data, use the URL and the HMAC secret the flow generates when saved. To send data, register a connector with the system's base URL and credential.

Step 3

Test without risk

The Test tab generates a temporary URL that only stores the last payloads received, without running actions, so you can check what arrives before using the flow.

Step 4

Follow the runs

Every run is logged with flow, action, status, duration and error. A flow can be deactivated without losing its configuration.

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.

Start using Automations (Webhooks)

View available plans or read the full article about this module.

View plans Read full article