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 the "Incident" resource in this context. The Get Many (getAll) operation retrieves multiple incident records from your Ivanti system, supporting advanced filtering, sorting, and field selection. This is useful for automating reporting, monitoring incident queues, or integrating incident data into other workflows.

Example scenarios:

  • Fetching a list of recent incidents for dashboard display.
  • Exporting filtered incidents to a spreadsheet.
  • Triggering alerts based on specific incident statuses.

Properties

Name Meaning
Limit Max number of results to return (1–100). Controls how many incidents are fetched in one request.
Send Sort Parameters Whether the request has sorting parameters or not. If enabled, you can specify how results are ordered.
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 options:
- Result Filter: OData filter expression to limit results (e.g., Status eq 'Resolved').
- Select Fields: Comma-separated list of fields to include.
- Skip Records: Number of records to skip (for pagination, 1–100).

Output

The output is an array of JSON objects, each representing an incident record retrieved from Ivanti. The structure of each object depends on the selected fields and filters, but typically includes standard incident properties such as:

{
  "IncidentNumber": "...",
  "RecId": "...",
  "Status": "...",
  "Owner": "...",
  // ...other fields as specified in "Select Fields"
}
  • If binary data is returned (not typical for this operation), it would represent file attachments or similar content related to incidents.

Dependencies

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

Troubleshooting

Common issues:

  • Authentication errors: Ensure the IvantiApi credentials are correctly configured.
  • Invalid filter expressions: Malformed OData queries in "Result Filter" may cause errors; refer to OData filter documentation.
  • Limit/Skip out of range: Values outside allowed ranges (1–100) will be rejected.
  • Missing fields: If "Select Fields" omits required properties, some automation steps may fail.

Error messages:

  • 401 Unauthorized: Check your API credentials.
  • 400 Bad Request: Likely due to invalid query parameters or filter syntax.
  • 500 Internal Server Error: May indicate server-side issues or misconfiguration.

Links and References

Discussion