Actions34
- Configuration Actions
- Contact Actions
- Domain Actions
- Flexible Asset Actions
- Organization Actions
- Password Actions
Overview
This node integrates with the IT Glue API to create a new contact within a specified organization. It is useful for automating the addition of contacts into IT Glue, especially when managing client or internal contact information programmatically. For example, you could use this node in workflows that onboard new employees or clients by automatically creating their contact records in IT Glue.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The unique identifier of the organization under which the contact will be created. |
| First Name | The first name of the contact. |
| Last Name | The last name of the contact (optional). |
| Additional Fields | Optional extra details about the contact: |
| - Contact Type ID: Identifier for the type/category of the contact. | |
- Email: JSON array of email objects, each with value (email address), label (e.g., Work), and primary flag. Example: [{"value": "email@example.com", "label": "Work", "primary": true}] |
|
| - Notes: Free text notes about the contact. | |
- Phone Numbers: JSON array of phone objects, each with value (phone number), label, and primary flag. Example: [{"value": "+1234567890", "label": "Work", "primary": true}] |
|
| - Title: Job title of the contact. |
Output
The node outputs JSON data representing the newly created contact as returned by the IT Glue API. This typically includes the contact's ID, attributes such as names, emails, phones, notes, and any other fields set during creation.
If binary data were involved (not indicated here), it would represent attachments or files related to the contact, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the IT Glue API using an API key credential configured in n8n.
- The node depends on the IT Glue API being accessible and the provided organization ID being valid.
- No additional external dependencies are required beyond the API authentication.
Troubleshooting
- Invalid Organization ID: If the organization ID does not exist or is incorrect, the API will return an error. Verify the organization ID before running the node.
- Malformed JSON in Emails or Phones: The email and phone fields expect JSON arrays. Improperly formatted JSON will cause errors. Use valid JSON syntax.
- Missing Required Fields: The node requires at least Organization ID and First Name. Omitting these will result in validation errors.
- API Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to create contacts.
- Network Issues: Connectivity problems with the IT Glue API endpoint can cause timeouts or failures.