Workflow Execution

This page explains how workflows execute when triggered, including the processing pipeline, error handling, and execution monitoring.

Execution Flow

When a workflow is triggered:

1. Event Reception — The trigger (webhook, manual) receives the incoming data.
2. Payload Validation — If a JSON schema is defined, the payload is validated.
3. Event Storage — The raw event is stored for debugging and replay.
4. Node Traversal — Starting from the trigger, each connected node is executed in topological order.
5. Data Propagation — Each node's output is passed as input to downstream nodes via edges.
6. Action Execution — Action nodes (Template, Email) perform their operations.
7. Completion — The workflow reports success or captures errors.

Execution Order

Nodes are executed following the directed graph of edges:

• Nodes with no upstream dependencies execute first.
• A node executes only after all its upstream nodes have completed.
• Parallel branches execute concurrently when possible.

Manual Execution

You can trigger a workflow manually from the Workflow Builder:

1. Open the workflow in the Builder.
2. Click Run or Test.
3. Optionally provide a test payload.
4. Watch the execution proceed through each node.

Monitoring

Webhook Events Tab

Each workflow has a Webhook Events tab showing:

• All received events (payload, timestamp, event ID).
• The most recent event data in detail.
• Processing status for each event.

Dashboard Metrics

The admin dashboard shows:

• Total webhook events processed.
• Events over time (trend chart).
• Workflow creation trends.

Error Handling

When a node fails during execution:

Scenario	Behavior
Invalid payload	Webhook returns 400 Bad Request, workflow does not execute
Template not found	Template Node fails, downstream nodes skip
Missing field mapping	Field is left blank in output PDF
Action limit exceeded	Stamping halts, error reported
Internal error	Node reports error status, other branches may continue

tip

Always test your workflow with a sample payload before activating it. Use the Latest Event viewer on the Webhook Trigger node to verify data structure.

Replaying Events

If a workflow fails due to a transient issue (e.g., a template was temporarily unavailable), you can replay the original event:

1. Go to the Webhook Events tab on the workflow.
2. Find the failed event.
3. Click Replay to re-trigger the workflow with the same payload.