Task Handle Soar icon

Task Handle Soar

Create a task in SOAR and wait for webhook callback

Task Handle Soar

AI-generated

Overview

This node creates a task in a SOAR (Security Orchestration, Automation, and Response) system and waits for a webhook callback to resume the workflow. It is useful for automating task creation in SOAR platforms and handling asynchronous responses via webhooks. For example, it can be used to create security incident tasks and wait for updates or resolutions from the SOAR system.

Use Case Examples

  1. Creating a security task with specific priority and SLA codes, then waiting for SOAR to send a webhook callback with task status updates.
  2. Automating task assignment to a user in a department with detailed task information and attachments, then resuming workflow upon webhook notification.

Properties

Name Meaning
Type Type of the task (number)
Name Name of the task (string)
Code Code of the task (string)
Department Code Department code for the task (string)
Case Code Case code associated with the task (string)
Username Username of the user assigned to the task (string, optional)
Catalog Priority Code Priority code for the task (string)
SLA Code Service Level Agreement code for the task (string)
Description Description of the task (string)
Status Status of the task (number)
Attachment IDs Array of attachment IDs in JSON format (string)
Tenancy Code Tenancy code for the task (string)
Information N8N Information fields in JSON format (JSON)
Timeout (Hours) How long to wait for webhook response before timing out (number)

Output

JSON

  • success - Indicates if the task creation or webhook handling was successful (boolean)
  • source - Source of the response, e.g., 'soar_webhook' for webhook data (string)
  • timestamp - Timestamp of the response or webhook reception (ISO string)
  • soarResponse - The full response payload received from the SOAR webhook (object)

Dependencies

  • Requires SOAR API credentials including an API token and API URL for authentication and communication.

Troubleshooting

  • Invalid JSON format in 'Attachment IDs' or 'Information N8N' fields may cause warnings and default to empty arrays.
  • Errors during task creation will log detailed error messages including HTTP status and response data.
  • If the webhook payload is empty, the node returns a 400 error and logs an error message.
  • Timeouts are handled by waiting for a specified number of hours before resuming the workflow; ensure the timeout is set appropriately.

Discussion