Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
This node allows you to create a new Task in Ivanti by interacting with the Ivanti API. It is designed for scenarios where you need to automate the creation of tasks related to various business objects (such as Incidents, Changes, Events, or Service Requests) within your Ivanti environment. Typical use cases include:
- Automatically generating follow-up tasks when an incident is logged.
- Creating tasks as part of a change management workflow.
- Assigning tasks to specific teams based on incoming service requests.
Example:
When a new Incident is created in your ITSM system, this node can be used to automatically create a related Task assigned to the appropriate team, with all necessary details and custom fields.
Properties
| Name | Meaning |
|---|---|
| Subject | Short title of the task. (Required) |
| Details | More information about the task. (Required) |
| Parent Type | Which type of business object the task should be related to. Options: Change, Event, Incident, Service Request. (Required) |
| Parent Record ID | RecId value of the parent record in Ivanti. (Required) |
| Parent Link | ParenLink value of the task in Ivanti. Defaults to null if not specified. |
| Use Predefined Fields | Whether object creation requires more predefined parameters. If enabled, additional fields become available. |
| Predefined Fields | Collection of extra fields shown if "Use Predefined Fields" is true: - Owner Team: Which team should complete the task - Unread: Whether task was read - Service (ID): Related Service ID - Service (Name): Related Service name |
| Send Custom Fields | Whether creating the object requires more custom parameters. If enabled, "Custom Fields" becomes available. |
| Custom Fields | Collection of custom fields (name-value pairs) to set on the task. Each entry includes: - Field Name or ID - Field Value |
Output
The node outputs a JSON object representing the newly created Task in Ivanti. The structure typically includes:
- All standard and custom fields sent in the request (e.g., Subject, Details, ParentLink_Category, ParentLink_RecID, etc.).
- Any additional metadata returned by the Ivanti API, such as unique identifiers or status information.
Note:
If binary data is supported by the node, it would represent file attachments or similar content associated with the task, but this is not indicated in the provided properties.
Dependencies
- External Service: Requires access to the Ivanti API endpoint.
- API Credentials: You must configure n8n with valid Ivanti API credentials (
IvantiApi). - n8n Configuration: The base URL for the Ivanti instance must be set in the credentials.
Troubleshooting
Common Issues:
- Missing Required Fields: If required fields like Subject, Details, Parent Type, or Parent Record ID are missing, the node will fail to create the task.
- Invalid Parent Type or Record ID: Providing an incorrect Parent Type or a non-existent Parent Record ID may result in errors from the Ivanti API.
- Authentication Errors: Incorrect or expired API credentials will prevent the node from connecting to Ivanti.
- Custom/Predefined Fields: Supplying invalid field names or values in custom/predefined fields may cause the API to reject the request.
Error Messages & Resolutions:
- 401 Unauthorized / 403 Forbidden: Check your Ivanti API credentials in n8n.
- 400 Bad Request: Review the input fields for missing or invalid data, especially required fields and custom field names/values.
- 404 Not Found: Ensure the Parent Record ID exists in Ivanti.