Ivanti icon

Ivanti

Interact with Ivanti API

Overview

This node allows you to retrieve a specific "Change" record from the Ivanti API using either its Change Number or Record ID. It is useful in scenarios where you need to fetch detailed information about a particular change request for further processing, reporting, or integration with other systems. For example, you might use this node to look up the status and owner of a change ticket by its unique identifier.

Properties

Name Meaning
ID Type Choose how you want to identify the change:
- Number (ChangeNumber)
- Record ID (RecId)
Number The ChangeNumber value of the change in Ivanti. Used when "ID Type" is set to "Number".
Record ID The RecId value of the change in Ivanti. Used when "ID Type" is set to "Record ID".
Query Parameters Additional query options:
- Select Fields: Specify which fields to include in the response (e.g., ChangeNumber, RecId, Status, Owner)

Output

The output will be a JSON object containing the details of the requested change record. The structure of the output depends on the fields selected via "Query Parameters > Select Fields", but typically includes properties such as:

{
  "ChangeNumber": "...",
  "RecId": "...",
  "Status": "...",
  "Owner": "...",
  // ...other fields as specified
}

No binary data is returned by this operation.

Dependencies

  • External Service: Requires access to an Ivanti API endpoint.
  • Credentials: You must configure n8n with valid Ivanti API credentials (IvantiApi), including the base URL.
  • Environment: Ensure network connectivity to the Ivanti instance.

Troubleshooting

  • Invalid Credentials: If your credentials are incorrect or missing, the node will fail to connect. Double-check your API key and base URL.
  • Record Not Found: If the provided ChangeNumber or RecId does not exist, the node may return an empty result or a "not found" error.
  • Field Selection Errors: If you specify invalid field names in "Select Fields", the API may return an error indicating unknown fields.
  • SSL Issues: The node skips SSL certificate validation by default, but if your Ivanti instance enforces strict SSL, you may encounter connection errors.

Links and References

Discussion