Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti node for n8n allows users to interact with the Ivanti API, specifically targeting various business objects such as Change, Custom Business Object, Employee, Event, Incident, and Task.
For the Change resource with the Get Count operation, this node retrieves the count of change records from the Ivanti system, optionally filtered by user-defined criteria.

Common scenarios:

  • Quickly determine how many change requests match certain conditions (e.g., all closed changes).
  • Use in automation workflows to trigger actions based on the number of changes meeting specific filters.
  • Monitor trends or thresholds in change management processes.

Practical example:
You might use this node to check how many change requests are currently open or have a particular status, and then send an alert if the count exceeds a threshold.

Properties

Name Meaning
Query Parameters A collection of additional query parameters to refine the count request.
Result Filter An OData filter expression to limit which change records are counted. Example: Status eq 'Closed'.

Output

  • The output will be a JSON object containing the count of change records that match the specified filter (if any).
  • Typical structure:
{
  "count": 42
}
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to an Ivanti instance with the OData API enabled.
  • API Credentials: Needs an n8n credential named IvantiApi with at least a baseUrl property configured.
  • n8n Configuration: No special environment variables required, but SSL certificate validation is skipped by default.

Troubleshooting

Common issues:

  • Invalid Filter Expression: If the OData filter syntax is incorrect, the API may return an error. Double-check your filter string.
  • Authentication Errors: Ensure the IvantiApi credentials are correctly set up in n8n.
  • Network/SSL Issues: Since SSL validation is skipped, ensure your Ivanti server is accessible and not blocking requests.

Error messages you might see:

  • "Invalid filter expression": Check the syntax of your filter in the "Result Filter" field.
  • "401 Unauthorized": Verify your API credentials.
  • "404 Not Found": Make sure the base URL is correct and the API endpoint exists.

Links and References

Discussion