IT Glue Extended
Actions153
- Attachment Actions
- Checklist Actions
- Checklist Template Actions
- Configuration Actions
- Configuration Interface Actions
- Configuration Status Actions
- Configuration Type Actions
- Contact Actions
- Contact Type Actions
- Country Actions
- Document Actions
- Domain Actions
- Expiration Actions
- Export Actions
- Flexible Asset Actions
- Flexible Asset Field Actions
- Flexible Asset Type Actions
- Group Actions
- Location Actions
- Log Actions
- Manufacturer Actions
- Model Actions
- Operating System Actions
- Organization Actions
- Organization Status Actions
- Organization Type Actions
- Password Actions
- Password Category Actions
- Platform Actions
- Region Actions
- Related Item Actions
- SSL Certificate Actions
- Ticket Actions
- User Actions
- User Metric Actions
Ticket → Update
AI-generatedSummary
Updates an existing IT Glue ticket by ID, sending a PATCH to the tickets endpoint with any of name, status, or priority, and returns the updated ticket as a flattened record.
Inputs
- Ticket ID (required) — ID of the ticket to update. The operation throws an error if it is empty.
- Name — New ticket name/title. Empty values are omitted from the request, so the existing name is left unchanged.
- Status — New ticket status as free text. Omitted from the request if empty.
- Priority — New ticket priority as free text. Omitted from the request if empty.
Output shape
One item holding the updated ticket. Attribute keys are converted from kebab-case to camelCase, and the item also includes id, type, and relationships when IT Glue returns them.
If no fields are filled in, the PATCH is still sent with empty attributes. There is no check for that case. Because empty strings are skipped, you cannot clear a field by setting it to an empty string. If IT Glue returns no data, the operation errors. Requests that hit a 429 are retried up to 3 times. Other API errors are raised as node errors, or returned as an item with an error message when Continue On Fail is enabled.
Examples
Example 1: Close a ticket after an upstream event
Resource: Ticket, Operation: Update, Ticket ID: {{$json.ticketId}}, Status: Closed
Example 2: Escalate a ticket's priority and rename it
Ticket ID: 12345, Name: 'Server outage - escalated', Priority: High