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
Contact → Create
AI-generatedSummary
Creates a new contact in IT Glue via a JSON:API POST, optionally scoped to an organization, and returns the created contact as a flattened record.
Inputs
- firstName (required) — Contact first name.
- lastName — Contact last name. Omitted from the request if empty.
- title — Contact job title. Omitted if empty.
- contactTypeId — Contact type, chosen from a list loaded from IT Glue's contact types (or an ID via expression). Omitted if empty.
- notes — Free-text notes about the contact. Omitted if empty.
- important — Boolean flag marking the contact as important. Defaults to false and is always sent.
- organizationId — Organization the contact belongs to, chosen from a list loaded from IT Glue (or an ID via expression). If set, the request goes to organizations/{id}/relationships/contacts; if empty, it goes to the top-level contacts endpoint.
Output shape
A single item containing the created contact: its attributes converted from kebab-case to camelCase (e.g. firstName, lastName, contactTypeId, organizationId), plus id, type, and relationships if IT Glue returns them.
Throws an error if IT Glue returns no data. HTTP 429 responses are retried up to 3 times with backoff. API errors (401, 403, etc.) surface as node errors. With Continue On Fail enabled, a failed item yields an item with an error message instead.
Examples
Example 1: Add a new employee contact to a specific client organization.
Organization = the client org, First Name = 'Jane', Last Name = 'Doe', Title = 'Office Manager', Contact Type = 'Employee'.
Example 2: Create a flagged VIP contact from upstream data using expressions.
First Name = {{$json.first}}, Last Name = {{$json.last}}, Important = true, Organization ID set via expression.