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 Incidents.
For the Incident → Get Count operation, this node retrieves the count of incident records from the Ivanti system, optionally filtered by specific criteria.
This is useful in scenarios where you need to monitor the number of incidents matching certain conditions (e.g., unresolved incidents, incidents assigned to a particular team) or generate reports and dashboards based on incident statistics.

Practical examples:

  • Counting all open incidents for SLA monitoring.
  • Getting the number of resolved incidents in the last week.
  • Integrating incident counts into automated reporting workflows.

Properties

Name Meaning
Query Parameters A collection of additional query parameters to refine your request.
Result Filter An OData filter expression to limit which incidents are counted. Example: Status eq 'Resolved'.

Output

The output will be a JSON object containing the count of incidents that match the specified filter (if any).
Typical structure:

{
  "count": <number>
}
  • If no filter is provided, it returns the total count of all incidents.
  • If a filter is applied, it returns the count of incidents matching the filter.

Dependencies

  • External Service: Requires access to an Ivanti instance with the OData API enabled.
  • Credentials: Needs an n8n credential named IvantiApi with at least a baseUrl property configured.
  • Environment: The base URL must be set correctly in the credentials; SSL certificate validation is skipped by default.

Troubleshooting

Common issues:

  • Invalid Credentials: If the IvantiApi credentials are missing or incorrect, authentication errors will occur.
  • Malformed Filter Expression: If the OData filter syntax is invalid, the API may return an error indicating a bad request.
  • Network/SSL Issues: Since SSL certificate validation is skipped, ensure your network allows insecure connections if necessary.

Error messages and resolutions:

  • "401 Unauthorized": Check your Ivanti API credentials.
  • "400 Bad Request": Review your filter expression for correct OData syntax.
  • "ENOTFOUND" or "ECONNREFUSED": Verify the baseUrl and network connectivity to the Ivanti server.

Links and References

Discussion