IT Glue ExtendedInstall

Summary

Creates a new ticket in IT Glue via a JSON:API POST, optionally scoped to an organization, and returns the created ticket as a flattened record.

Inputs

• Name — Ticket name/title. Sent as the name attribute; omitted if left empty.
• Status — Ticket status as free text. Sent as the status attribute; omitted if empty.
• Priority — Ticket priority as free text. Sent as the priority attribute; omitted if empty.
• Organization Name or ID — Organization to create the ticket under, chosen from a list loaded from IT Glue or given as an ID via expression. If set, the request goes to organizations/{id}/relationships/tickets. If empty, it goes to tickets.

Output shape

A single item containing the created ticket. Attributes are converted from kebab-case to camelCase and placed at the top level, alongside id, type and relationships (when present).

Throws an error if IT Glue returns no data. Empty string fields are not sent, and none of the three ticket fields is marked required. HTTP 429 responses are retried up to 3 times. Other API errors surface as node errors with the IT Glue detail message. If 'Continue on Fail' is enabled, the failed item outputs {error: message}. The Ticket resource is defined in the source's gated registry folder, but the descriptor has no gated: true flag, so it is included in the node.

Examples

Example 1: Open a high-priority ticket for a specific client organization

Resource: Ticket, Operation: Create, Organization: pick the client, Name: 'VPN outage', Status: 'Open', Priority: 'High'.

Example 2: Create a ticket from an upstream alert, using the organization ID from earlier in the workflow

Set Organization to an expression such as {{ $json.orgId }}, Name to {{ $json.alertTitle }}, and Status to 'New'.

Links

• n8n community nodes installation guide