Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
This n8n node allows you to create a new Incident in the Ivanti system via its API. It is designed for automating IT service management workflows, such as logging support tickets, tracking issues, or integrating incident creation into broader business processes. Typical use cases include:
- Automatically creating incidents from monitoring alerts.
- Logging user-reported problems from forms or chatbots.
- Integrating with other systems (e.g., CRM, helpdesk) to centralize incident management.
Properties
| Name | Meaning |
|---|---|
| Subject | Short title of the incident. (Required) |
| Symptom | More information about the incident. (Required) |
| Service (Name) | Which Service is related to the incident. (Required) |
| Customer User (ID) | Which customer user (employee) is related to the incident. (Required) |
| Use Predefined Fields | Whether object creation requires more predefined parameters. If enabled, additional fields become available. |
| Predefined Fields | Collection of optional fields: - First Call Resolution: Whether incident is resolved by first call. - Impact: Impact of the incident ( Low, Medium, High).- Master Incident: Whether this is a master incident. - Owner Team: Which team should resolve the incident. - Private: Whether incident is private. - Service (ID): Related service ID. - Service Level Agreement (ID/Name): SLA related to the incident. - Source: Source of the incident ( AutoTicket, Chat, Email, Phone, Self Service).- Unread: Whether incident was read. - Urgency: Urgency of the incident ( Urgent, Not Urgent). |
| Send Custom Fields | Whether creating the object requires more custom parameters. If enabled, "Custom Fields" becomes available. |
| Custom Fields | List of custom field name/value pairs to set on the incident. Each entry includes: - Field Name or ID: Name of the custom field. - Field Value: Value to set on the custom field. |
Output
- The node outputs the JSON response returned by the Ivanti API after creating the incident.
- The structure typically includes details of the created incident, such as its unique identifier and all properties set during creation.
- If binary data is ever output (not typical for this operation), it would represent file attachments or similar content associated with the incident.
Dependencies
- External Service: Requires access to an Ivanti instance with API enabled.
- Credentials: You must configure the
IvantiApicredential in n8n, including the base URL and authentication details. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
- Missing Required Fields: If required fields like "Subject", "Symptom", "Service (Name)", or "Customer User (ID)" are not provided, the node will fail with an error indicating missing parameters.
- Invalid Credentials: Errors related to authentication (e.g., 401 Unauthorized) indicate incorrect or missing Ivanti API credentials.
- API Connection Issues: Network errors or timeouts may occur if the Ivanti instance is unreachable or the base URL is misconfigured.
- Field Validation Errors: Providing invalid values (e.g., wrong option names, empty required fields) may result in API errors specifying which field is problematic.