Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti node for n8n, when configured with the Event resource and the Get Many (getAll) operation, retrieves a list of event records from the Ivanti API. This node is useful for automating workflows that require fetching multiple events, such as monitoring system changes, aggregating event data for reporting, or integrating Ivanti event information with other systems.

Practical examples:

  • Fetching recent events to trigger alerts in case of specific statuses.
  • Exporting filtered event lists for compliance or auditing purposes.
  • Synchronizing Ivanti events with external ticketing or incident management tools.

Properties

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

Output

The node outputs an array of event objects in the json field. Each object represents an event record retrieved from the Ivanti API. The structure of each event object depends on the selected fields and filters but typically includes properties such as event number, status, owner, creation time, etc.

Example output:

[
  {
    "EventNumber": "EVT12345",
    "Status": "Open",
    "Owner": "John Doe",
    "CreatedDateTime": "2024-06-01T12:34:56Z",
    ...
  },
  ...
]

Note: The actual fields depend on the "Select Fields" property and the Ivanti API schema.

Dependencies

  • External Service: Requires access to the Ivanti API endpoint.
  • Credentials: Must configure the IvantiApi credential in n8n, including the base URL and authentication details.
  • n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

  • Common Issues:

    • Invalid Credentials: If credentials are incorrect or missing, the node will fail to connect to the Ivanti API.
    • API Limits: Exceeding the maximum allowed limit (100) or using invalid query parameters may result in errors.
    • Incorrect Filters/Fields: Using non-existent field names in filters or select statements can cause API errors.

  • Error Messages & Resolutions:

    • 401 Unauthorized: Check your IvantiApi credentials in n8n.
    • 400 Bad Request: Review your query parameters, especially custom filters and selected fields.
    • Connection Timeout: Ensure the Ivanti API endpoint is reachable from your n8n instance.

Links and References

Discussion