Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti Task Update node allows you to update an existing task record in the Ivanti system via its API. This is useful for automating workflows where tasks need to be programmatically modified, such as updating their status, assigning them to different users or teams, changing details, or adding custom information. Typical scenarios include service desk automation, ITSM processes, and integration with other business systems.

Example use cases:

  • Automatically updating a task's status when a related incident is resolved.
  • Assigning tasks to specific teams based on workflow logic.
  • Adding resolution notes or additional details to a task after completion.

Properties

Name Meaning
Record ID RecId value of the task in Ivanti. (Required)
Use Predefined Fields Whether object creation requires more predefined parameters. If enabled, you can set standard fields like Details, Owner, Status, etc.
Predefined Fields Collection of standard task fields you can update:
- Details: More information about the task
- Owner: Person assigned to complete the task
- Owner Team: Team assigned
- Parent Link: Parent task link
- Parent Record ID: RecId of parent
- Parent Type: Type of related business object (Change, Event, Incident, Service Request)
- Resolution: Resolution details
- Service (ID): Related service by ID
- Service (Name): Related service by name
- Status: Task status
- Subject: Short title
- Unread: Whether task was read
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. Each entry has:
- Field Name or ID: Name/ID of the custom field
- Field Value: Value to set

Output

  • The output will contain the updated task record as returned by the Ivanti API.
  • The structure of the json output field will reflect the updated properties of the task, including any fields you have set or changed.
  • If binary data is ever returned (unlikely for this operation), it would represent file attachments or similar content associated with the task.

Example output:

{
  "RecId": "1234567890",
  "Subject": "Updated Task Title",
  "Status": "Completed",
  "Owner": "John Doe",
  "Details": "Additional info here",
  // ...other fields as returned by Ivanti
}

Dependencies

  • External Service: Requires access to an Ivanti instance with API enabled.
  • API Key/Credentials: Needs valid Ivanti API credentials configured in n8n under "IvantiApi".
  • n8n Configuration: The base URL for your Ivanti instance must be set in the credentials.

Troubleshooting

  • Missing or Invalid Record ID: If the "Record ID" is missing or incorrect, the node will fail to find the task and return an error. Ensure you provide a valid RecId.
  • Insufficient Permissions: If the API user does not have permission to update tasks, you may receive authorization errors.
  • Invalid Field Values: Providing values that do not match expected formats (e.g., wrong Parent Type) may result in validation errors from Ivanti.
  • Connection Issues: Network or SSL issues may prevent communication with the Ivanti API. Check your base URL and network settings.

Links and References

Discussion