Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti node for n8n allows you to interact with the Ivanti API, specifically targeting various business objects such as Change, Incident, Task, Employee, Event, and Custom Business Objects.
For the Change → Get Many operation, this node retrieves a list of change records from Ivanti, supporting filtering, sorting, field selection, and pagination.

Common scenarios:

  • Fetching a list of changes for reporting or dashboard purposes.
  • Filtering changes by status (e.g., only "Closed" changes).
  • Retrieving only specific fields for each change to optimize data flow.
  • Paginating through large sets of change records.

Practical example:
You might use this node in an automation that pulls all open changes created in the last week, sorts them by creation date, and sends a summary email to your IT team.

Properties

Name Meaning
Limit Max number of results to return (1–100). Controls how many change records are fetched in one request.
Send Sort Parameters Whether the request has sorting parameters or not. If enabled, you can specify how to sort the results.
Sort Sorting options (shown if "Send Sort Parameters" is true):
• Sort Key Name or ID: Choose between "Creation Time" or "Last Modification Time".
• Sort Order: Ascending or Descending.
Query Parameters Additional query parameters:
• Result Filter: OData filter expression (e.g., Status eq 'Closed').
• Select Fields: Comma-separated list of fields to include.
• Skip Records: Number to skip.

Output

The output is a JSON array where each item represents a change record retrieved from Ivanti.
The structure of each item depends on the selected fields and filters, but typically includes properties such as:

{
  "ChangeNumber": "...",
  "RecId": "...",
  "Status": "...",
  "Owner": "...",
  // ...other fields as specified in "Select Fields"
}

If no "Select Fields" are specified, all default fields for a change record are returned.

Note: This node does not output binary data.

Dependencies

  • External Service: Requires access to an Ivanti instance with the API enabled.
  • Credentials: Needs an n8n credential named IvantiApi with at least a baseUrl property.
  • n8n Configuration: No special environment variables required beyond credentials.

Troubleshooting

Common issues:

  • Invalid Credentials: If the IvantiApi credentials are incorrect or missing, authentication errors will occur.
  • API URL Misconfiguration: Ensure the baseUrl in credentials does not have a trailing slash; the node removes it automatically.
  • OData Query Errors: Incorrect syntax in "Result Filter" or "Select Fields" may result in API errors.
  • Limit Exceeded: Setting "Limit" above 100 will be rejected.

Error messages and resolutions:

  • 401 Unauthorized: Check your Ivanti API credentials.
  • 400 Bad Request: Review your filter expressions and field names for typos or invalid values.
  • 404 Not Found: Verify the base URL and resource name.

Links and References

Discussion