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 to update existing Change records. The "Change: Update" operation is used to modify details of a change request in your Ivanti system. This is useful in IT service management workflows where changes to tickets or requests need to be automated, such as updating status, assigning owners, or adding additional information.

Practical examples:

  • Automatically update the status of a change when an approval is received.
  • Assign a change to a different owner or team based on workflow logic.
  • Add resolution notes or other custom fields after a process step completes.

Properties

Name Meaning
Record ID RecId value of the change in Ivanti. (Required)
Use Predefined Fields Whether object creation requires more predefined parameters. If enabled, you can set standard Ivanti change fields below.
Predefined Fields Collection of standard Ivanti change fields to update. Includes:
- Description: More information about the change
- Owner: Person to implement the change
- Owner Team: Team to implement the change
- Private: Whether change is private
- Resolution: Resolution details
- Service (ID): Related service by ID
- Service (Name): Related service by name
- Service Level Agreement (ID): SLA by ID
- Service Level Agreement (Name): SLA by name
- Status: Status of the change
- Subject: Short title
- Type Of Change: Type of the change (Normal, Operational, Standard)
- Unread: Whether change was read
- Customer User (ID): Related customer user (employee)
Send Custom Fields Whether creating object requires more custom parameters. If enabled, you can set custom fields below.
Custom Fields List of custom field name/value pairs to set on the change record. Each entry includes:
- Field Name or ID: Name of the custom field
- Field Value: Value to set

Output

  • The output will contain the JSON response from the Ivanti API after updating the change record.
  • The structure typically reflects the updated change object, including all fields that were modified and any additional data returned by the API.
  • No binary data is produced by this operation.

Example output:

{
  "RecId": "00123456789ABCDEF",
  "Status": "Closed",
  "Owner": "John Doe",
  "Resolution": "Issue resolved and verified.",
  ...
}

Dependencies

  • External Service: Requires access to an Ivanti instance with API enabled.
  • Credentials: You must configure the IvantiApi credential in n8n, which should include at least the base URL and authentication details.
  • n8n Configuration: Ensure the Ivanti node is installed and credentials are set up in your n8n environment.

Troubleshooting

  • Missing or Invalid Record ID: If the "Record ID" is missing or incorrect, the API will likely return a "Not Found" or similar error. Double-check the ID value.
  • Authentication Errors: If credentials are not set up correctly, you may receive authentication or authorization errors. Verify your IvantiApi credentials.
  • Field Validation Errors: If required fields are missing or have invalid values, the API may reject the request. Review the field requirements in Ivanti documentation.
  • SSL Certificate Issues: The node skips SSL certificate validation by default, but if your Ivanti server enforces strict SSL, you may need to adjust settings.

Links and References

Discussion