Opening
Pick Up Exactly Where Lesson 7 Ended
Communication automation asks whether Quickbase should communicate. Pipeline automation gives us a workflow to orchestrate.
Native Communication Automation
Something happens / time arrives → criteria are evaluated → communication occurs.
Pipeline Workflow Automation
Something happens / time arrives / someone initiates → a workflow executes → data can be retrieved → logic evaluated → values passed → systems contacted → actions performed.
Remember This
The Big Change
With Pipelines, starting the automation and what the automation eventually does become explicitly composable parts of a workflow.
Part 1
Where Does a Pipeline Live?
A field belongs to a table. A table belongs to an app. A report belongs to a table. So where does a Pipeline belong?
DOCUMENTED
Pipelines exist at Quickbase realm scope
A Pipeline is not contained inside one application. It can orchestrate work involving App A, App B, and an external service without any one of them owning the Pipeline.
REALM
Pipeline
Remember This
Orchestration is coordination, not ownership
Prefer “realm-level workflow orchestrator” over “master controller.” The Pipeline coordinates work involving independent resources; it does not own them.
Part 2
Workflow vs. Pipeline vs. Step
Workflow
The overall process we want accomplished.
Pipeline
Quickbase's configured executable implementation of that workflow.
Step
One defined unit of work or control within the Pipeline.
Bus-trip analogy
Workflow: get students to the museum. Pipeline: the executable plan. Steps: bus arrives → check attendance → determine readiness → notify museum → record departure.
Remember This
A step does not necessarily change data
A step can detect, retrieve, evaluate/control, perform an action, stop, or redirect execution.
Parts 3–4
What Wakes a Pipeline Up?
Triggered
Something happened.
EVENT → EXECUTION
Scheduled
A time arrived.
TIME → EXECUTION
Manual
Someone explicitly initiates execution.
HUMAN INITIATION → EXECUTION
Initiation
Why did this execution begin?
Workflow Actions
What happens after it begins?
Remember This
Triggered / Scheduled / Manual describe initiation—not eventual purpose
All three initiation models can lead to similar downstream work. Starting the workflow and defining its work are separate concepts.
Part 5
Pipeline Definition vs. Pipeline Execution
Pipeline Definition
Persistent instructions/configuration that remain when nothing is running.
Runtime Execution
One particular occurrence of that definition actually executing.
Monday
Task #17 qualifies → Runtime Instance A
Tuesday
Task #42 qualifies → Runtime Instance B
Wednesday
No qualifying event → No runtime instance
Remember This
“Didn't run” is not the same as “ran and found nothing”
No qualifying event means no execution. A query returning zero records means an execution existed and produced an empty result.
Part 6
The Trigger Does More Than Say GO
If Task #17 starts the Pipeline, later steps need to know which Task caused the event. The trigger can introduce runtime context.
| Record ID# | 17 |
|---|---|
| Task Name | Prepare November Reports |
| Status | Complete |
| Due Date | 11/10/2026 |
Event
Trigger
Starts execution + introduces context
Runtime Instance
Contains particular values
Workflow Uses Those Values
Bus analogy
Bus arrival does not merely yell GO. It also hands the coordinator useful context: Bus #142, Driver Susan, Arrival 7:36 AM.
Part 7
Definition-Time References vs. Runtime Values
Definition
Use Status from the trigger.
Runtime #1
Status → Complete
Runtime #2
Status → Open
Remember This
Same definition. Different execution. Different runtime values.
Definition is structure and instructions. Runtime is the particular data encountered during one execution.
Interactive Classification
Definition, Runtime, or No Execution?
Pipeline listens for modified Tasks.
Record ID# = 17.
Pipeline contains a Find Records step.
Monday's search returned Record #83.
Pipeline contains an Update Record action.
Monday's update changed #83 to Complete.
No qualifying event occurred Wednesday.
Part 8
Pipelines Are Also Data Flows
Two flows exist at once: what happens next and what information becomes available next.
Execution Flow
Step A
Step B
Step C
Data Flow
Output A
Input B → Output B
Input C
Remember This
Earlier steps can produce runtime output that later steps consume
This is the foundation for references, mapping, queries, loops, later Jinja work, and debugging. Do not begin with syntax before understanding the data relationship.
Parts 9–10
Channels and Accounts Solve Different Problems
Channel
What capabilities exist for interacting with this system?
A Channel gives steps system/service-specific operations. The Pipeline orchestrates; the Channel supplies capabilities.
Account / Connection
What authenticated connection are we using?
The target system determines what that authenticated identity can actually do.
Account
Authenticated connection / identity
Target System
Target System Evaluates Authorization
Remember This
Pipeline management permission and step authentication are separate questions
Do not reduce Account to “permission.” Authentication supplies identity/connection; authorization is evaluated by the target system.
Part 11
How Does Data Move Between Steps?
Trigger
Task #17 modified → output includes Record ID# = 17
Find Records
Consumes earlier Record ID# → produces a result
Later Step
Consumes values produced earlier
Remember This
Teach step outputs and references before variables
First understand that one step produces output and another step can consume a reference to it. Later lessons can add variables, Jinja, and transformation syntax.
Part 12
One Record vs. a Collection
Interactive Scenario
One Record vs. a Collection
Query Result
Child #101
Downstream Shape
A later operation expecting one record can work directly with one item.
Loop / Iteration
Process #101, then #102, then #103.
Bulk Operations
Operate on a set/batch when individual step-by-step processing is unnecessary.
Staging / Helper Table
Some architectures write intermediate data to a dedicated helper/staging table before later processing.
Not Yet
Lesson 8 acknowledges loops, bulk processing, and staging strategies. It does not teach them. A staging/helper table is a design pattern, not a special native “temporary table” object.
Part 13
Why the Activity Log Matters
The definition tells us what was supposed to happen. Runtime evidence tells us what actually happened.
Pipeline Definition
What was supposed to happen?
Activity Log
What actually happened?
Detailed Activity Log work comes later, but this becomes our primary runtime evidence source.
Remember This
Evidence outranks assumption
Future experiments follow DOCUMENTED → PREDICTION → EXECUTION → OBSERVED → ACTIVITY LOG EVIDENCE → EXPLANATION. If evidence disagrees with our theory, investigate.
Part 14
Assemble the Whole Machine
REALM
Pipeline lives at realm scope.
PIPELINE
Persistent executable workflow definition.
INITIATION
Triggered / Scheduled / Manual.
EXECUTION
One runtime instance begins.
STEPS
Units of work or control.
CHANNELS
System-specific capabilities.
ACCOUNTS
Authenticated connections where required.
RUNTIME DATA
Earlier outputs become later inputs.
COLLECTION DECISIONS
Single item? Collection? Loop? Bulk? Staging?
ACTIVITY LOG
Runtime evidence of what actually occurred.
A Pipeline is a realm-level workflow orchestrator whose executions proceed through defined steps, use channels to interact with systems, authenticate through appropriate connections, and move runtime data from earlier work into later work.
Part 15
Communication Automation vs. Pipelines
| Concept | Native Communication Automation | Pipelines |
|---|---|---|
| Event-driven | Yes | Yes |
| Time-driven | Yes | Yes |
| Manual initiation | Not part of communication mechanisms studied | Yes |
| Primary destination | Communication | General workflow execution |
| Explicit workflow composition | Specialized feature configuration | Yes |
| Multiple kinds of work | Limited to communication feature purpose | Core capability |
| Cross-system orchestration | Not the fundamental model | Core capability |
| Runtime step outputs | Not exposed as a general workflow-building mechanism | Fundamental |
| Queries / loops / transformations | Not the model studied | Available in Pipelines |
| Activity evidence | Communication-specific history/results | Pipeline Activity Log |
Not Yet
Detailed Jinja, loops, bulk processing, staging architecture, queries, YAML, schema refresh, error handling, and deep Activity Log work are intentionally deferred.
Part 16 — Knowledge Check
Do You See the Machine Yet?
The point is not merely whether you guessed True or False. Every item explains why the mental model is right or wrong after grading.
A Pipeline interacting with App A and App B must belong to whichever app contains its trigger.
Workflow and Pipeline are best treated as identical concepts.
Every Pipeline step must change data.
Triggered, Scheduled, and Manual describe how execution begins rather than what the Pipeline eventually does.
If no qualifying trigger event occurs, a triggered Pipeline still creates an empty runtime execution.
A trigger may contribute runtime information associated with the event that started an execution.
The Quickbase Channel and a Quickbase Account mean the same thing.
A Channel supplies capabilities for interacting with a particular system or service.
An Account should be understood simply as the Pipeline's permission level.
Data produced by an earlier step can become input to a later step.
A query returning three records and a query returning one record always create the same downstream design problem.
Loops are the only valid way a workflow can deal with collections of records.
If a Pipeline did not update anything, that proves no Pipeline execution occurred.
The Pipeline definition describes intended behavior; runtime evidence describes what happened during a particular execution.
Part 17
Lesson 8 Exit Challenge
A Pipeline begins when a Task changes. It receives information about that Task, finds three related records, evaluates each one, updates qualifying records in another Quickbase app, and eventually contacts an external service.
Where does the Pipeline live?
Realm.
What initiates this example?
Trigger / event.
What is one occurrence called?
Execution / runtime instance.
Where does original Task data enter?
Trigger output / event context.
What are the units of work/control?
Steps.
What supplies system-specific capabilities?
Channels.
What supplies authentication where required?
Accounts / connections.
What happens when three records are returned?
The result is a collection requiring an appropriate processing strategy.
What evidence helps determine what actually happened?
Activity Log.
Remember This
You have not yet learned how to build this workflow
You have learned what kind of machine would be required to execute it. That is Lesson 8.
Lesson 8 Complete
You Can See the Machine.
Buttons can move. Labels can evolve. Realm scope, execution, runtime context, steps, Channels, Accounts, data flow, collections, and runtime evidence are the durable ideas that make the Pipeline designer understandable.