Ation Service Agent Trigger icon

Ation Service Agent Trigger

Receive task status updates from the Ation Service Agent

Overview

This node acts as a webhook trigger for receiving task status updates from the Ation Service Agent. It listens for HTTP POST requests at a configurable webhook path and processes incoming callback data related to task statuses. This node is useful for workflows that need to react to real-time updates from the Ation Service Agent, such as monitoring task progress or triggering subsequent automation steps based on task completion or status changes.

Use Case Examples

  1. A project management workflow that updates task statuses in a database when the Ation Service Agent sends status updates.
  2. An alerting system that triggers notifications when a task reaches a specific status reported by the Ation Service Agent.

Properties

Name Meaning
Webhook Path The path segment appended to the base webhook URL where the node listens for incoming POST requests from the Ation Service Agent. This defines the endpoint to receive callbacks.

Output

JSON

  • name - Name associated with the task status update received from the Ation Service Agent.
  • project_id - Numeric project identifier parsed from the incoming data.
  • project_name - Name of the project related to the task status update.
  • report - Report data included in the callback payload.
  • status - Current status of the task as reported by the Ation Service Agent.
  • task_id - Numeric identifier of the task.
  • template_id - Numeric identifier of the template used for the task.
  • version - Version information related to the task or report.

Troubleshooting

  • Ensure the webhook path configured in the node matches the path used by the Ation Service Agent to send callbacks; mismatches will cause the node not to receive data.
  • Verify that the incoming POST requests contain all expected fields; missing or malformed data may result in incomplete or null output properties.
  • Check that the node is properly deployed and accessible via the webhook URL to avoid connectivity issues.

Discussion