Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti Employee Get operation node allows you to retrieve detailed information about a specific employee (user) from the Ivanti system using various identifiers such as Login ID, Primary Email, or Record ID. This is useful in scenarios where you need to fetch user details for automation workflows, such as onboarding, offboarding, access management, or integrating employee data with other systems.

Practical examples:

  • Fetching an employee's profile by their email to update records in another HR system.
  • Retrieving user details based on Login ID for audit or reporting purposes.
  • Integrating Ivanti employee data into custom dashboards or notification flows.

Properties

Name Meaning
ID Type Choose the type of identifier to use for fetching the employee. Options: Login ID, Primary Email, Record ID.
Login ID The LoginID value of the employee in Ivanti. Required if "ID Type" is set to "Login ID".
Record ID The RecId value of the employee in Ivanti. Required if "ID Type" is set to "Record ID".
Primary Email The PrimaryEmail value of the employee in Ivanti. Required if "ID Type" is set to "Primary Email".
Query Parameters Additional query parameters to refine the request. Includes:
- Select Fields: Comma-separated list of fields to include in the response (e.g., PrimaryEmail, RecId, Status, LoginID).

Output

  • The output is a JSON object containing the employee's details as returned by the Ivanti API.
  • The structure of the output depends on the selected fields and the underlying Ivanti schema, but typically includes properties like PrimaryEmail, RecId, Status, LoginID, etc.
  • No binary data is produced by this operation.

Example output:

{
  "PrimaryEmail": "jane.doe@example.com",
  "RecId": "12345",
  "Status": "Active",
  "LoginID": "jdoe"
}

Dependencies

  • External Service: Requires access to the Ivanti API endpoint.
  • API Credentials: You must configure valid Ivanti API credentials (IvantiApi) in n8n.
  • Environment Variable: The base URL for the Ivanti instance must be set in the credentials.

Troubleshooting

  • Invalid Credentials: If the API credentials are incorrect or missing, authentication errors will occur. Ensure the IvantiApi credential is properly configured.
  • Incorrect ID Type/Value: Supplying an invalid or non-existent identifier (Login ID, Primary Email, or Record ID) will result in no data being returned or an error from the API.
  • Field Selection Errors: Specifying non-existent fields in "Select Fields" may cause the API to return errors or incomplete data.
  • Network Issues: Connectivity problems between n8n and the Ivanti API endpoint can lead to timeouts or connection errors.

Links and References

Discussion