Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

This n8n node allows you to update an existing Event record in the Ivanti system. It is designed for scenarios where you need to modify event details, such as updating status, severity, or adding additional information to an event already present in Ivanti. Typical use cases include automating incident management workflows, synchronizing event data from monitoring tools, or enriching events with new information as part of a larger automation process.

Practical examples:

  • Automatically update the severity and status of an event when a related alert is resolved.
  • Add notes or resolution details to an event after manual investigation.
  • Change the owner or team responsible for an event based on business logic.

Properties

Name Meaning
Record ID RecId value of the event in Ivanti. This uniquely identifies which event record will be updated. (Required)
Use Predefined Fields Whether object creation requires more predefined parameters. If enabled, you can specify additional standard fields to update.
Predefined Fields Collection of standard event fields you can update:
- CI Name: Which CI is related to the event
- Description: Short title of the event
- Notes: More information about the event
- Outage: Whether the event causes an outage
- Owner: Which person should investigate the event
- Owner Team: Which team should investigate the event
- Resolution: Resolution details of the event
- Severity: How severe is this event (Low, Medium, High)
- Source: In which source the event originated (ImmyBot, Mail, Zabbix)
- Start Date Time: Date and time when the event started
- Status: Status of the task
- Support Hours: Support coverage (9x5, 24x7)
- Unread: Whether event was read
- Customer User (ID): Which customer user (employee) is related to event
Send Custom Fields Whether creating object requires more custom parameters. If enabled, you can specify custom fields to update.
Custom Fields List of custom fields to set on the event. 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 updating the event. The structure of this output will typically reflect the updated event record, including all fields that were modified and any other relevant event data as provided by the Ivanti API.

Note: The exact structure depends on the Ivanti API's response format.

Dependencies

  • External Service: Requires access to an Ivanti instance with the HEAT API enabled.
  • API Credentials: You must configure the IvantiApi credentials in n8n, including the base URL and authentication details.
  • n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common Issues:

  • Invalid Record ID: If the provided "Record ID" does not exist, the API will likely return a "not found" error.
  • Missing Required Fields: Omitting required fields may result in validation errors from the API.
  • Authentication Errors: Incorrect or missing credentials will cause authentication failures.
  • Field Value Errors: Providing invalid values (e.g., unsupported options for Severity or Source) may result in API errors.

Error Messages & Resolutions:

  • "404 Not Found": Check that the "Record ID" is correct and exists in Ivanti.
  • "401 Unauthorized": Verify your IvantiApi credentials in n8n.
  • "400 Bad Request": Review the input fields for missing or invalid data, especially for required or option-type fields.

Links and References

Discussion