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 custom business objects. The Link operation under the "Custom Business Object" resource is used to create a relationship (link) between two records of business objects in Ivanti. This is useful when you need to associate or relate different entities within your Ivanti environment, such as linking a custom asset record to a user or another custom object.
Practical Example:
Suppose you have a custom business object representing "Assets" and another representing "Departments." You can use this node to link a specific asset to a department, establishing a relationship that can be leveraged in reporting or workflow automation.
Properties
| Name | Meaning |
|---|---|
| Business Object Name | The name (ID) of the custom business object you want to work with in Ivanti. |
| Record ID (This Object) | The unique RecId value of the primary custom object record you wish to link from. |
| Relationship Name | The name of the relationship in Ivanti that defines how the two business objects are linked together. |
| Record ID (Related Object) | The unique RecId value of the related business object record you wish to link to the primary object. |
Output
- The output will typically be a JSON object reflecting the result of the link operation.
- It may include status information or confirmation that the relationship was successfully created.
- No binary data is produced by this operation.
Example Output:
{
"status": "success",
"message": "Objects linked successfully"
}
Note: Actual output structure may vary depending on the Ivanti API response.
Dependencies
- External Service: Requires access to an Ivanti instance with API enabled.
- API Credentials: Needs valid Ivanti API credentials configured in n8n under the credential type
IvantiApi. - Environment Variables: The base URL for the Ivanti API must be set in the credentials.
Troubleshooting
Common Issues:
- Invalid Record IDs: If either Record ID is incorrect or does not exist, the link operation will fail.
- Relationship Name Errors: Providing an invalid or misspelled relationship name will result in errors from the Ivanti API.
- Authentication Failures: Incorrect or missing API credentials will prevent the node from connecting to Ivanti.
Common Error Messages & Resolutions:
"404 Not Found": Check that both Record IDs and the Relationship Name are correct and exist in Ivanti."401 Unauthorized": Verify that your Ivanti API credentials are correctly configured in n8n."400 Bad Request": Ensure all required fields are filled and formatted properly.