Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
This node allows you to create a new "Change" record in the Ivanti system via its API. It is designed for IT service management workflows where tracking, managing, and automating change requests is essential. Typical use cases include:
- Automating the creation of change requests when certain conditions are met (e.g., after an incident or as part of a deployment pipeline).
- Integrating Ivanti with other systems to ensure changes are logged and tracked consistently.
- Enriching change records with custom or predefined fields based on business requirements.
Example:
Automatically create a "Normal" change request with a subject, description, and related user whenever a deployment pipeline completes successfully.
Properties
| Name | Meaning |
|---|---|
| Subject | Short title of the change. Required. |
| Description | More information about the change. Required. |
| Type Of Change | Type of the change. Options: Normal, Operational, Standard. You can also specify an ID using an expression. |
| Customer User (ID) | Which customer user (employee) is related to the change. Required. Accepts a user ID. |
| Use Predefined Fields | Whether object creation requires more predefined parameters. If enabled, additional predefined fields can be set. |
| Predefined Fields | Collection of additional fields to set if "Use Predefined Fields" is enabled. Includes: • Owner Team: Which team should implement the change • Private: Whether change is private • Service (ID/Name): Related service • Service Level Agreement (ID/Name): Related SLA • Unread: Whether change was read |
| Send Custom Fields | Whether creating the object requires more custom parameters. If enabled, you can add custom fields. |
| Custom Fields | List of custom fields to set if "Send Custom Fields" is enabled. Each field includes: • Field Name or ID: Name of the custom field • Field Value: Value to set on the custom field |
Output
The node returns the JSON response from the Ivanti API after creating the change record. The structure typically includes details of the newly created change, such as its unique identifier and any fields returned by the API.
Note:
If binary data is ever output, it would represent file attachments or similar content associated with the change, but this node primarily outputs structured JSON data.
Dependencies
- External Service: Requires access to the Ivanti API endpoint.
- API Credentials: Needs an IvantiApi credential configured in n8n, including at least the
baseUrland authentication details. - n8n Configuration: Ensure that SSL certificate validation is handled according to your environment (the node skips SSL validation by default).
Troubleshooting
Missing Required Fields:
- Error: "Subject", "Description", or "Customer User (ID)" is required.
Resolution: Ensure all required fields are provided.
- Error: "Subject", "Description", or "Customer User (ID)" is required.
Invalid Credentials or Endpoint:
- Error: Authentication failed or cannot reach Ivanti API.
Resolution: Check your IvantiApi credentials and base URL configuration.
- Error: Authentication failed or cannot reach Ivanti API.
Field Mapping Issues:
- Error: "Invalid field name" or "Unknown property".
Resolution: Double-check custom and predefined field names/IDs against your Ivanti instance.
- Error: "Invalid field name" or "Unknown property".
SSL Certificate Errors:
- Error: SSL certificate validation failed.
Resolution: The node skips SSL validation by default, but network/firewall issues may still block access.
- Error: SSL certificate validation failed.