Job Pipelines
Pipelines chain multiple workflows into a single, ordered execution flow. Each stage can pass data to the next, and conditional logic controls whether downstream stages run on success, failure, or always.
Creating a Pipeline
Navigate to Dashboard → Pipelines → New Pipeline.
Click Add Stage for each step. Stages execute top-to-bottom.
Stage Run Conditions
Set each stage (except the first) using the Run When dropdown:
| Condition | Behaviour |
|---|---|
| OnSuccess | Stage runs only if the previous stage completed successfully |
| OnFailure | Stage runs only if the previous stage failed — ideal for error-handling or notification stages |
| Always | Stage runs regardless of the previous stage's outcome — useful for cleanup |
Passing Data Between Stages
In the Map Outputs section, map an output variable from one stage to an input variable of the next. Example:
| From Stage | Output Variable | To Stage | Input Variable |
|---|---|---|---|
| 1 — Extract Orders | extractedData | 2 — Process Orders | inputData |
| 2 — Process Orders | processedCount | 3 — Send Report | totalProcessed |
Running a Pipeline
Two ways to start a pipeline:
| Method | How |
|---|---|
| Manual | Pipelines list → Run Now button |
| Scheduled | Schedules page → create a new schedule → select Pipeline instead of Workflow |
Monitoring
Click a pipeline run row to expand it. Each stage shows its own status in real time: Pending → Running → Success / Failed. Click a stage to see its activity-by-activity log, just like a regular job.
Error Handling PatternAdd a final Always stage that runs a notification workflow (e.g., send an email or Slack message with the pipeline status). This ensures you are always notified, regardless of whether earlier stages succeeded or failed.