Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
This node allows you to link an Event record in Ivanti to another business object by establishing a relationship between them. It is useful when you need to associate events with related records (such as incidents, tasks, or custom objects) within the Ivanti platform, ensuring data integrity and traceability across your ITSM processes.
Common scenarios:
- Linking an event to a related incident for better context.
- Associating an event with a specific employee or task.
- Automating relationships between business objects during workflow execution.
Practical example:
When a new event is created in Ivanti, this node can be used to automatically link it to a corresponding incident or other business object, streamlining your service management workflows.
Properties
| Name | Meaning |
|---|---|
| Record ID (Event) | RecId value of the event in Ivanti. This uniquely identifies the event to be linked. |
| Relationship Name | The name of the relationship to use for linking business objects. |
| Record ID (Related Object) | RecId value of the related business object in Ivanti. This is the target object to link to. |
Output
The output will contain the result of the linking operation. Typically, this includes confirmation that the relationship was established. The structure may include:
- A status indicator (e.g., success/failure)
- Any response data returned by the Ivanti API
- If there is an error, details about the failure
No binary data is output by this operation.
Dependencies
- External Service: Requires access to the Ivanti API.
- Credentials: n8n credential named
IvantiApimust be configured, including thebaseUrlfor 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 Event or Related Object Record ID is incorrect, the link will fail.
- Incorrect Relationship Name: Using a non-existent or misspelled relationship name will cause errors.
- Authentication Errors: Missing or invalid Ivanti API credentials will prevent the node from working.
Error messages and resolutions:
"404 Not Found": Check that both Record IDs and the Relationship Name are correct and exist in Ivanti."401 Unauthorized": Verify that your IvantiApi credentials are set up correctly in n8n."400 Bad Request": Ensure all required fields are filled and formatted properly.