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 various business objects such as Employees.
For the Employee → Link operation, this node enables you to create a relationship (link) between an Employee record and another related business object within Ivanti.
This is useful in scenarios where you need to associate employees with other entities (e.g., departments, incidents, tasks) programmatically as part of your workflow automation.
Practical Example:
- Automatically link a new employee to their department or manager after onboarding.
- Associate an employee with a specific incident or task for tracking purposes.
Properties
| Name | Meaning |
|---|---|
| Record ID (Employee) | RecId value of the employee in Ivanti. This uniquely identifies the employee to be linked. |
| Relationship Name | The name of the relationship to use when linking business objects (e.g., "Department"). |
| Record ID (Related Object) | RecId value of the related business object in Ivanti. This is the target object to link. |
Output
- The output will contain the result of the link operation. Typically, this includes confirmation that the relationship was created.
- The structure of the
jsonoutput field will reflect the response from the Ivanti API, which may include status information or details about the linked records. - No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Ivanti API.
- Credentials: You must configure the
IvantiApicredential in n8n, including the base URL (baseUrl) for your Ivanti instance. - n8n Configuration: Ensure SSL certificate validation settings match your environment (the node skips SSL validation by default).
Troubleshooting
Common Issues:
- Invalid Record IDs: If either the Employee or Related Object RecId is incorrect, the link operation will fail.
- Incorrect Relationship Name: Using a non-existent or misspelled relationship name will result in errors from the API.
- Authentication Errors: Missing or invalid credentials will prevent the node from connecting to Ivanti.
Error Messages & Resolutions:
"Resource not found": Check that both Record IDs are correct and exist in Ivanti."Unauthorized": Verify that your IvantiApi credentials are set up correctly in n8n."Relationship does not exist": Double-check the Relationship Name for typos or mismatches with your Ivanti configuration.