Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

This node allows you to retrieve a specific Incident from the Ivanti API by either its Incident Number or Record ID. It is useful in workflows where you need to fetch detailed information about a particular incident for further processing, reporting, or integration with other systems. For example, you might use this node to look up an incident's status and owner based on a ticket number provided by a user.

Properties

Name Meaning
ID Type Choose how you want to identify the incident:
- Number (IncidentNumber)
- Record ID (RecId)
Number The IncidentNumber value of the incident in Ivanti. Required if "ID Type" is set to "Number".
Record ID The RecId value of the incident in Ivanti. Required if "ID Type" is set to "Record ID".
Query Parameters Additional query options:
- Select Fields: Specify which fields to include in the response (e.g., IncidentNumber, RecId, Status, Owner). This helps limit the data returned to only what you need.

Output

The output will be a JSON object containing the details of the requested incident. The structure depends on the selected fields (if any) and the data available in Ivanti. Typical fields may include:

{
  "IncidentNumber": "12345",
  "RecId": "abcde-12345",
  "Status": "Open",
  "Owner": "John Doe",
  ...
}

If binary data is present (unlikely for this operation), it would represent file attachments or similar content related to the incident.

Dependencies

  • Ivanti API: Requires access to the Ivanti API endpoint.
  • API Credentials: You must configure the IvantiApi credential in n8n, including the base URL and authentication details.
  • n8n Configuration: Ensure that SSL certificate validation is handled as per your environment (the node skips SSL validation by default).

Troubleshooting

  • Invalid Credentials: If credentials are incorrect or missing, you may receive authentication errors. Double-check your IvantiApi configuration.
  • Incorrect ID Type/Value: Supplying the wrong type or value for the incident identifier will result in no data found or an error from the API.
  • Field Selection Errors: If you specify invalid field names in "Select Fields", the API may return an error or omit those fields.
  • Connection Issues: Network problems or incorrect base URL can cause connection failures.

Common error messages:

  • "Authentication failed": Check your API credentials.
  • "Resource not found": Verify the IncidentNumber or RecId.
  • "Invalid field name": Review the fields listed in "Select Fields".

Links and References

Discussion