Actions34
- Configuration Actions
- Contact Actions
- Domain Actions
- Flexible Asset Actions
- Organization Actions
- Password Actions
Overview
The node provides integration with the IT Glue API, specifically supporting a "Bulk Update" operation for contacts. This operation allows users to update multiple contact records in one execution by specifying their IDs and the fields to modify.
This node is beneficial when managing large sets of contact data within IT Glue, enabling batch updates such as changing email addresses, phone numbers, or other contact details efficiently without manual edits for each record.
Practical example:
A user wants to update the job titles and phone numbers of several contacts after an organizational restructure. Instead of updating each contact individually, they prepare a list of contact IDs with new titles and phones, then use this node's bulk update operation to apply all changes at once.
Properties
| Name | Meaning |
|---|---|
| Updates | A collection of contact updates to perform. Each update requires: |
| - Contact ID (required): The unique identifier of the contact to update. | |
| - Contact Type ID: The ID representing the type/category of the contact. | |
| - Email: The contact's email address. | |
| - First Name: The contact's first name. | |
| - Last Name: The contact's last name. | |
| - Notes: Additional notes about the contact. | |
| - Phone: The contact's phone number. | |
| - Title: The job title of the contact. |
Users can add multiple such updates in one execution, each specifying different contacts and fields to update.
Output
The node outputs JSON data representing the result of the bulk update operation. Typically, this includes confirmation of updated contacts or error information if any updates failed.
If the node supports binary data output, it would relate to attachments or files associated with contacts, but for this bulk update operation, the primary output is structured JSON reflecting the update results.
Dependencies
- Requires an API key credential for authenticating with the IT Glue API.
- The node expects the IT Glue API to be accessible from the environment where n8n runs.
- No additional external dependencies are indicated beyond the IT Glue API access.
Troubleshooting
Common issues:
- Invalid or missing Contact IDs will cause update failures for those entries.
- Providing invalid field values (e.g., malformed email) may result in API errors.
- Network or authentication errors if the API key is incorrect or expired.
Error messages:
- Errors indicating "Contact not found" suggest that the provided Contact ID does not exist.
- Authentication errors imply issues with the API key credential setup.
- Validation errors on fields like email or phone indicate improper formatting.
Resolutions:
- Verify all Contact IDs before running the bulk update.
- Ensure the API key credential is correctly configured and has necessary permissions.
- Validate input data formats according to IT Glue API requirements.