Ivanti icon

Ivanti

Interact with Ivanti API

Overview

The Ivanti node for n8n allows you to interact with the Ivanti API, specifically targeting various business objects such as Events. The Event: Get operation retrieves a specific event from Ivanti based on either its Event Number or Record ID. This is useful in scenarios where you need to fetch detailed information about a particular event for further processing, reporting, or integration with other systems.

Practical examples:

  • Fetching an event's details by its unique number to display in a dashboard.
  • Retrieving an event record by its Record ID for automated incident management workflows.
  • Pulling selected fields of an event for use in downstream automation steps.

Properties

Name Meaning
ID Type Choose how to identify the event:
- Number (EventNumber)
- Record ID (RecId)
Number The EventNumber value of the event in Ivanti. Required if "ID Type" is set to "Number".
Record ID The RecId value of the event in Ivanti. Required if "ID Type" is set to "Record ID".
Query Parameters Additional query options:
- Select Fields: Comma-separated list of fields to include in the response (e.g., EventNumber, RecId, Status, Owner).

Output

  • The output is a JSON object containing the event data retrieved from Ivanti.
  • The structure of the output will reflect the fields returned by the Ivanti API, which can be customized using the "Select Fields" property.
  • If binary data is present (not typical for this operation), it would represent file attachments or similar content associated with the event.

Example output:

{
  "EventNumber": "12345",
  "RecId": "abcde-12345",
  "Status": "Open",
  "Owner": "John Doe"
}

Fields included depend on the "Select Fields" parameter and the underlying Ivanti schema.

Dependencies

  • External Service: Requires access to the Ivanti API endpoint.
  • Credentials: An n8n credential named IvantiApi must be configured, including at least the baseUrl.
  • n8n Configuration: No special environment variables are required, but SSL certificate validation is skipped by default.

Troubleshooting

Common issues:

  • Invalid credentials: Ensure the IvantiApi credential is correctly set up with valid base URL and authentication details.
  • Incorrect ID Type or missing ID: If the wrong ID type is selected or the corresponding field is left empty, the node may return no results or an error.
  • Field selection errors: Specifying non-existent fields in "Select Fields" may result in API errors or empty responses.
  • Network/SSL issues: Since SSL validation is skipped, ensure your network allows connections to the Ivanti API endpoint.

Error messages and resolutions:

  • "401 Unauthorized" – Check your API credentials.
  • "404 Not Found" – Verify the EventNumber or RecId exists in Ivanti.
  • "400 Bad Request" – Review the query parameters, especially the filter syntax and selected fields.

Links and References

Discussion