AITEZA Progress icon

AITEZA Progress

Reports workflow progress back to Aiteza while the workflow is running. Reads the callback details from the upstream Aiteza Trigger node automatically.

AITEZA Progress

AI-generated

Summary

Sends workflow progress updates to an external Aiteza instance via HTTP callback, using configuration from an upstream Aiteza Trigger.

Inputs

  • step (required) — Short label describing the current step shown to the user.
  • stepIndex — Position of the current step (1-based).
  • totalSteps — Total number of steps in this workflow.
  • detail — Optional longer description of what is currently happening.
  • additionalFields — Optional JSON object merged into the progress payload (e.g. percent complete, items processed).
  • options.callbackUrlOverride — Override the callback URL read from the Aiteza Trigger (without trailing slash).
  • options.callbackTokenOverride — Override the callback token read from the Aiteza Trigger.
  • options.executionIdOverride — Override the execution ID read from the Aiteza Trigger.
  • options.failOnError — Whether to stop the workflow if the progress callback cannot be delivered.
  • options.timeout — Maximum time in milliseconds to wait for the callback to complete.

Output shape

The original input items with an additional _progressReport property added to each item's JSON object.

If a callback URL and execution ID are not found in the upstream Aiteza Trigger, the node logs the failure but continues execution by default. If failOnError is true, the workflow fails. The report metadata includes a sent boolean, callbackUrl, executionId, and any error details.

Examples

Example 1: Basic progress reporting for a multi-step import process

Set 'Step' to 'Importing Data', 'Step Index' to 5, and 'Total Steps' to 10.

Example 2: Reporting completion with additional context

Set 'Step' to 'Complete', 'Detail' to 'Processed 1000 records', and 'Additional Fields' to { "percent": 100, "records": 1000 }.

Example 3: Ensuring the workflow stops if callbacks fail

Set 'Fail Workflow on Callback Failure' to true and ensure the upstream Aiteza Trigger provides a valid callback URL and execution ID.

Links

Discussion