Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
This node allows you to link a Change record in Ivanti with another business object by establishing a specified relationship between them. It is useful for automating the association of changes with related records, such as incidents, tasks, or custom objects, within the Ivanti ITSM platform.
Common scenarios:
- Linking a change request to an incident or problem record.
- Associating a change with a related task or custom business object.
- Automating cross-references between different Ivanti modules for better traceability.
Practical example:
When a new change is created due to an incident, this node can automatically link the change record to the originating incident using the appropriate relationship.
Properties
| Name | Meaning |
|---|---|
| Record ID (Change) | The unique RecId value of the change record in Ivanti that you want to link from. |
| Relationship Name | The name of the relationship to use for linking the two business objects. |
| Record ID (Related Object) | The unique RecId value of the related business object in Ivanti that you want to link to. |
Output
The node outputs the result of the link operation. Typically, this will be a JSON object containing the response from the Ivanti API after attempting to create the relationship reference. The exact structure depends on the API's response, but it usually includes status information and may include details about the linked records.
Dependencies
- External Service: Requires access to the Ivanti API.
- Credentials: Needs an n8n credential named
IvantiApiwith at least abaseUrlproperty configured. - n8n Configuration: Ensure the base URL in credentials does not end with a slash (
/).
Troubleshooting
- Missing or Invalid Record IDs: If either Record ID is incorrect or missing, the API will likely return a "Not Found" or "Invalid Reference" error. Double-check the RecId values.
- Incorrect Relationship Name: Using an invalid relationship name will cause the API to reject the request. Refer to your Ivanti documentation for valid relationship names.
- Authentication Errors: If credentials are missing or incorrect, you'll receive authentication errors. Make sure the
IvantiApicredential is set up properly. - SSL Certificate Issues: The node skips SSL certificate validation by default, but if the API endpoint requires strict SSL, you may need to adjust settings.