Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
The Ivanti node for n8n allows you to interact with the Ivanti API, specifically targeting business objects such as Tasks. The Task → Link operation is designed to create a relationship (link) between a Task record and another related business object within Ivanti. This is useful in scenarios where you need to associate tasks with other entities (e.g., incidents, changes, or custom objects) to maintain relational data integrity or workflow automation.
Practical examples:
- Linking a task to an incident so that progress on the task is reflected in the incident's lifecycle.
- Associating a task with a change request to track implementation steps.
- Connecting a task to a custom business object for specialized workflows.
Properties
| Name | Meaning |
|---|---|
| Record ID (Task) | RecId value of the task in Ivanti. This uniquely identifies the task to be linked. |
| Relationship Name | Relationship name which will be used to link business objects. Specifies the type of link. |
| Record ID (Related Object) | RecId value of the related business object in Ivanti. Identifies the object to link to. |
Output
The node outputs a json field containing the response from the Ivanti API after attempting to create the link between the specified Task and the related object. The exact structure of this output depends on the API's response, but typically it will include status information or details about the created relationship.
Dependencies
- External Service: Requires access to the Ivanti API endpoint.
- API Credentials: Needs an n8n credential named
IvantiApiwith at least abaseUrlproperty configured. - n8n Configuration: Ensure SSL certificate validation settings and base URL are correctly set in the credentials.
Troubleshooting
Common issues:
- Invalid Record IDs: If either the Task or Related Object Record ID is incorrect or does not exist, the API may return a "Not Found" or similar error.
- Incorrect Relationship Name: Using an invalid or misspelled relationship name can result in errors indicating the relationship does not exist.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures.
Error messages and resolutions:
"404 Not Found": Check that both Record IDs and the Relationship Name are correct and exist in your Ivanti instance."401 Unauthorized": Verify that your IvantiApi credentials are valid and have sufficient permissions."400 Bad Request": Ensure all required fields are filled and formatted correctly.