Portal Community

What Is a Pipeline?

A Template is a single saved input+options set for one workflow — you already know it as the thing you configure and click Execute on. A Pipeline is a step above that: an ordered list of Templates that run one after another, as a single unit. You build the list once, and every time you (or, in a later phase, a schedule) trigger the Pipeline, it walks the list from top to bottom.

A simple example: a monthly close process might need three Templates run back-to-back — Generate Report, then Email It, then Archive It. Without Pipelines you'd click Execute three times and watch each one finish before starting the next. With a Pipeline, you set this up once as an ordered list of three steps, and one Execute click runs the whole chain.

Step 1: Generate Report   ──▶  Step 2: Email It   ──▶  Step 3: Archive It
   (runs, waits to finish)        (runs, waits)           (runs, waits)
                                                                 │
                                                                 ▼
                                                        Pipeline Completed

Guide Pages

# Page What You'll Learn
1 Creating a Pipeline The Pipelines menu, Add Pipeline, naming your pipeline and setting the per-step wait time
2 Adding Items & Template Lookup Adding steps with the Template Lookup picker, On-Failure Behavior, Configuration overrides, Refresh from template
3 Executing & Run History The Execute button, watching a run step through, the run-history list, and what Cancel actually does
4 Searching Pipelines The Pipelines search screen, row actions, and the reused Templates menu in the same app
5 FAQ & Troubleshooting Common questions about concurrent runs, editing Templates in use, and shared workflows
Tip: Flow Pipelines is a newer, lower-priority addition to Flow Studio. Templates remain the primary building block for day-to-day work — reach for a Pipeline only when you need more than one Template to run in sequence as a single, repeatable unit.