Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
The Ivanti Incident Update node allows you to update an existing incident record in the Ivanti system via its API. This is useful for automating IT service management workflows, such as updating ticket statuses, assigning incidents to users or teams, changing priorities, or adding resolution details. Typical scenarios include integrating Ivanti with other systems (e.g., monitoring tools, communication platforms) to automatically update incidents based on external events.
Example use cases:
- Automatically update the status and resolution of an incident when a related workflow completes.
- Assign incidents to specific users or teams based on business logic.
- Add custom fields or additional information to incidents from other integrated systems.
Properties
| Name | Meaning |
|---|---|
| Record ID | RecId value of the incident in Ivanti. Required to identify which incident to update. |
| Use Predefined Fields | Whether object creation requires more predefined parameters. If enabled, you can set standard incident fields below. |
| Predefined Fields | Collection of standard fields you can update on the incident, including: - Customer User (ID): Related customer user. - First Call Resolution: Whether resolved on first call. - Impact: Low, Medium, High. - Master Incident: Whether this is a master incident. - Owner: Person responsible. - Owner Team: Responsible team. - Private: Whether the incident is private. - Resolution: Details of the resolution. - Service (ID/Name): Related service. - Service Level Agreement (ID/Name): Related SLA. - Source: AutoTicket, Chat, Email, Phone, Self Service. - Status: Current status. - Subject: Short title. - Symptom: More info. - Unread: Whether the incident was read. - Urgency: Urgent, Not Urgent. |
| Send Custom Fields | Whether creating object requires more custom parameters. If enabled, you can add custom fields below. |
| Custom Fields | List of custom fields to set on the incident. Each entry includes: - Field Name or ID: Name of the custom field. - Field Value: Value to set. |
Output
The node returns the updated incident's data as a JSON object. The structure typically mirrors the Ivanti API response for an incident update, containing all relevant fields of the incident after the update.
If binary data is returned (not typical for this operation), it would represent file attachments or similar content associated with the incident.
Example output:
{
"RecId": "0014960452EE44259E8149C715B24DEF",
"Subject": "Printer not working",
"Status": "Resolved",
"Resolution": "Replaced toner cartridge",
"Owner": "John Doe",
"Impact": "High",
// ...other fields as returned by Ivanti
}
Dependencies
- External Service: Requires access to the Ivanti API endpoint.
- API Credentials: You must configure the
IvantiApicredential in n8n, including the base URL and authentication details. - n8n Configuration: Ensure the node is connected to the main workflow and that credentials are properly set up.
Troubleshooting
- Missing or Invalid Record ID: If the "Record ID" is missing or incorrect, the node will fail to find the incident and may return a "Not Found" or similar error.
- Authentication Errors: Incorrect or missing API credentials will result in authentication failures.
- Field Validation Errors: Providing invalid values for certain fields (e.g., using an unsupported value for "Impact" or "Urgency") may cause the API to reject the request.
- Custom Field Issues: If a custom field name or value is incorrect or does not exist in Ivanti, the update may fail or be ignored.
Common error messages:
"Incident not found": Check the Record ID."Unauthorized"or"Invalid credentials": Verify your IvantiApi credentials."Invalid field value": Review the options and ensure correct values are provided.