GLPI Rest API V2 (Fork)Install

Summary

Updates a GLPI Management sub-resource (e.g., Budget, Contact, Contract) via the REST API.

Inputs

• subresource (required) — Select the Management sub-resource to update (Budget, Cluster, Contact, Contract, DataCenter, Database, Document, Domain, License, Line, or Supplier).
• itemid (required) — ID of the item to update. Must be a positive number.
• data — A collection of fields to update. Each field is a key-value pair (e.g., Name, Value, Additional Data). This is parsed and sent as a JSON object.
• input — Raw JSON payload string. When 'Send raw body' is enabled, this is sent exactly as-is; otherwise, it is combined with the 'data' collection.
• sendRawBody — When enabled, the 'input' string is sent as the request body directly. When disabled, the 'data' collection is sent as a JSON object named 'input'.
• showCredentials — If true, the node outputs the configured credentials and skips the API request.

Output shape

One item per processed input containing the GLPI API response for the updated resource.

The API response may be a single object or an array, depending on the GLPI endpoint. Errors are returned as JSON objects with an 'error' field.

Examples

Example 1: Update a Contact's name and value

Sub-resource: Contact, Item ID: 123, Data: Name='John Doe', Value='New Value'

Example 2: Update a Document using raw JSON body

Sub-resource: Document, Item ID: 456, Send raw body: true, Input: '{"name": "Updated Doc", "content": "New content"}'

Example 3: Update a License using the data collection

Sub-resource: License, Item ID: 789, Data: Name='License Key 2', Additional='expiry: 2025-12-31'

Links

• n8n community nodes installation guide