Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti node for n8n allows you to interact with the Ivanti API, specifically to create new Event records. The "Event: Create" operation is used to log or register a new event in your Ivanti system, which can be useful for tracking incidents, changes, alerts, or other noteworthy occurrences within your IT environment.

Common scenarios:

  • Automatically logging monitoring alerts (e.g., from Zabbix) as events.
  • Creating events based on incoming emails or external triggers.
  • Integrating with automation tools (like ImmyBot) to record operational events.

Practical example:
When a server outage is detected by Zabbix, this node can automatically create an event in Ivanti, including details such as severity, affected CI, and notes for the support team.

Properties

Name Meaning
Description Short title of the event. (Required)
Notes More information about the event. (Required)
Source In which source the event originated. Options: ImmyBot, Mail, Zabbix. You may also specify an ID using an expression. (Required)
Use Predefined Fields Whether object creation requires more predefined parameters. If enabled, additional fields become available.
Predefined Fields Collection of optional predefined fields:
- CI Name: Which CI is related to the event
- Outage: Whether the event causes an outage
- Owner Team: Which team should investigate the event
- Severity: How severe is this event (Low, Medium, High)
- Start Date Time: When the event started
- Support Hours: 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 add custom fields.
Custom Fields List of custom fields to set on the event. Each field has:
- Field Name or ID
- Field Value

Output

The node outputs a JSON object representing the created event as returned by the Ivanti API. The structure typically includes all submitted fields (Description, Notes, Source, any predefined/custom fields), along with system-generated identifiers and metadata from Ivanti.

Example output:

{
  "Description": "Server Down",
  "Notes": "Zabbix detected outage at 2am.",
  "Source": "Zabbix",
  "CIName": "WebServer01",
  "IsOutage": true,
  "Severity": "High",
  "EventStartDateTime": "2024-06-10T02:00:00Z",
  "SupportHours": "24x7",
  "IsUnRead": true,
  "CustomerLink_RecID": "0014960452EE44259E8149C715B24DEF",
  "CustomField1": "Value1",
  "id": "1234567890",
  "createdAt": "2024-06-10T02:01:00Z"
}

Note: Actual output fields depend on the Ivanti API response.

If binary data is supported, it would represent file attachments or similar, but this node primarily returns structured JSON.

Dependencies

  • External Service: Requires access to an Ivanti instance with API enabled.
  • Credentials: Must configure an n8n credential named IvantiApi with appropriate base URL and authentication.
  • n8n Configuration: No special configuration beyond credentials.

Troubleshooting

Common issues:

  • Authentication errors: Ensure the IvantiApi credential is correctly configured.
  • Missing required fields: Both "Description", "Notes", and "Source" are mandatory; omitting them will cause errors.
  • Invalid field values: For options like "Severity" or "Support Hours", only allowed values are accepted.
  • API endpoint errors: If the base URL is incorrect or Ivanti API is unavailable, requests will fail.

Error messages and resolutions:

  • "401 Unauthorized": Check your API credentials.
  • "400 Bad Request": Verify all required fields are provided and valid.
  • "404 Not Found": Confirm the base URL and endpoint path are correct.
  • "SSL certificate error": The node skips SSL validation by default, but network issues may still occur.

Links and References

Discussion