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 Employees.
For the Employee → Get Many operation, this node retrieves a list of employee records from the Ivanti system, supporting advanced filtering, sorting, and field selection.
This is useful in scenarios where you need to synchronize employee data, generate reports, or automate HR-related workflows by fetching multiple employee entries based on specific criteria.

Example use cases:

  • Fetching all active employees for onboarding/offboarding automation.
  • Retrieving a paginated list of employees for reporting.
  • Filtering employees by status or department.

Properties

Name Meaning
Limit Max number of results to return (1–100). Controls how many employee records are fetched in one request.
Send Sort Parameters Whether the request has sorting parameters or not. If enabled, additional sort options can be specified.
Sort Allows specifying sorting details if "Send Sort Parameters" is enabled:
• Sort Key Name or ID: Choose between "Creation Time" or "Last Modification Time".
• Sort Order: Ascending or Descending.
Query Parameters Additional query parameters to refine results:
• Result Filter: OData filter expression (e.g., Status eq 'Active').
• 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 employee records, each represented as a JSON object.
Each object contains the fields returned by the Ivanti API, which may include (but are not limited to):

[
  {
    "PrimaryEmail": "jane.doe@example.com",
    "RecId": "12345",
    "Status": "Active",
    "LoginID": "jdoe",
    // ...other fields depending on Select Fields and API response
  }
]
  • The structure and included fields depend on the "Select Fields" property and the Ivanti API schema.
  • No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the Ivanti API endpoint.
  • Credentials: An n8n credential named IvantiApi must be configured, including at least the baseUrl.
  • n8n Configuration: Ensure network access to the Ivanti instance and proper authentication setup.

Troubleshooting

Common Issues:

  • Invalid Credentials: If credentials are missing or incorrect, authentication errors will occur. Double-check your IvantiApi credential configuration.
  • API Endpoint Errors: If the base URL is misconfigured, requests may fail with connection or 404 errors.
  • Query Parameter Errors: Invalid OData filter expressions or field names in "Select Fields" can cause API errors.
  • Limit/Skip Out of Range: Setting "Limit" or "Skip Records" outside allowed range (1–100) may result in validation errors.

Error Messages & Resolutions:

  • "401 Unauthorized": Check your API credentials.
  • "400 Bad Request": Review your filter expressions, selected fields, or sort options for typos or unsupported values.
  • "404 Not Found": Verify the base URL and resource path.

Links and References

Discussion