Part 1
Look How Far Communication Automation Took Us
The specialized communication tools are not inadequate. They solve their intended problems very well, and learning a broader capability later does not make them obsolete.
Notification / Triggered Custom Email
Record event → evaluation → communication
“When this happens to a record, tell somebody.”
Scheduled Custom Email
Schedule → current report information → communication
“At this scheduled time, communicate what is currently true.”
Subscription
Report → recurring delivery → recipients
“Send these people this report periodically.”
Reminder
Record date → temporal offset → criteria → recipient → communication
“Tell somebody when this record approaches its important date.”
Remember This
These are real automation
The fact that we are about to learn something more general does not reduce the value of specialized mechanisms that clearly solve a requirement.
Part 2
The Pattern We've Been Using
Something Happens
Quickbase Evaluates
A Communication Action Occurs
What if sending the communication isn't the end of the requirement?
Parts 3–4
Enter the Mind of the Builder
The requirement begins comfortably: “When a Task becomes Complete…” Then the business owner keeps talking.
“When a Task becomes Complete, find all of that person's other Open Tasks.”
WHEN
Task becomes Complete.
READ
Who is Assigned To?
FIND
Other records where Assigned To matches and Status = Open.
Find them how?
The requirement has changed from evaluating the triggering record to retrieving additional data.
Part 5
The Business Process Is Bigger Than the Email
Business Process
What the organization needs to happen.
Remaining obligations should be reviewed, overdue work addressed, tracking updated, and responsible people informed.
Workflow
The ordered sequence of activities used to carry out the business process.
Complete Task → find remaining Tasks → identify overdue work → create follow-up work → update tracking → notify supervisor.
Orchestration
The coordination of those activities, including data, decisions, dependencies, and resulting actions.
Part 6
Communication Is an Action, Not the Definition of Automation
COMMUNICATE
Send an email.
READ
Retrieve information.
FIND
Locate qualifying records.
CREATE
Create another record.
MODIFY
Change existing data.
DECIDE
Choose what happens next.
REPEAT
Perform an action for multiple results.
CONTINUE
Use one result to determine another action.
Remember This
Email is one possible automated action. It is not the boundary of automation.
Once a requirement coordinates data and actions, the architecture is no longer defined by whether an email appears somewhere in the sequence.
Part 7
Evaluation vs. Orchestration
Evaluation
Should this action occur?
- Did the record change?
- Which fields changed?
- Does Status equal Complete?
- Is this record three days from Due Date?
- Does this report contain records?
Orchestration
What happens next, and what does the next step need from the previous one?
- What information did that give us?
- What other records do we need?
- What did we find?
- Which path should we take?
- What should we change?
- What happens for each result?
Part 8
Revisit Our Automation Architecture
Earlier lessons concentrated on event detection and rule evaluation. Now we zoom outward toward the consumer/workflow and resulting actions.
SOURCE / REQUEST
DATA MUTATION
CHANGE / EVENT
RULE EVALUATION
CONSUMER / WORKFLOW
ACTION
RESULTING DATA / STATE
POSSIBLE NEW EVENTS
Parts 9–12
The Mind Benders Escalate
Mind Bender #2 — Read → Find → Decide
When a Task becomes Complete, find the same user's other Open Tasks and determine whether any are overdue.
The important question is now what the result of one operation causes us to do next.
Mind Bender #3 — Data Has to Travel
Step A discovers Assigned To = Bob. Step B needs that value to find Bob's other Open Tasks.
Step A Output
Assigned To = Bob
Step B Input
Find Tasks where Assigned To = Bob
Remember This
Multi-step automation requires a way to pass data between steps
We are not answering how yet. The important thing is recognizing why such a capability must exist.
Mind Bender #4 — One Record Becomes Many
The search returns 7 Open Tasks. Increase Priority for every overdue Task.
A workflow may need to iterate over a collection of results.
Mind Bender #5 — Don't Create Duplicates
For every overdue Task, create a Follow-Up record—but only if an active Follow-Up does not already exist.
For Each Overdue Task
Find Related Follow-Up
Does Active Follow-Up Exist?
YES → Skip
NO → Create Follow-Up
We now have retrieval, iteration, branching, creation, and duplicate prevention. This is no longer primarily a communication requirement.
Part 13
Boolean Logic Has Graduated
Earlier
IF conditions are true → send communication.
Now
IF condition A → Path A
ELSE IF condition B → Path B
ELSE → another path or stop.
Remember This
Boolean logic has moved from controlling whether a communication occurs to controlling how a workflow proceeds
This is transfer of earlier knowledge, not another Boolean lesson.
Part 14
Actions Can Cause More Events
If automation modifies another record, that mutation may itself be meaningful to other automation. We should start asking about secondary effects without overclaiming undocumented internals.
Event A
Workflow
Modify Record B
Record B Changes
Could This Become Another Event?
Part 15
The Full Business Requirement
Now combine everything into one process.
When a Task becomes Complete, identify the Assigned To user, find all of that user's other Open Tasks, determine which are overdue, create a Follow-Up for each overdue Task that does not already have one, update the user's tracking record with the number of overdue Tasks, and notify the supervisor with a summary.
TRIGGER
Task becomes Complete
READ
Assigned To
FIND
Other Open Tasks
FILTER / EVALUATE
Which are overdue?
ITERATE
For each overdue Task
CHECK
Does active Follow-Up exist?
BRANCH
Yes → skip / No → create
COUNT / RESULT
How many overdue Tasks?
UPDATE
Tracking record
COMMUNICATE
Supervisor summary
Can one Notification, Custom Email, Scheduled Custom Email, Subscription, or Reminder naturally represent this entire sequence?
No. We've crossed the line.
Part 16
The Line in the Sand
Communication Automation
The dominant requirement is that something should be communicated when a defined event, schedule, report delivery, or record-relative date condition occurs.
- Event → Email
- Schedule → Report briefing
- Report → Subscription
- Record Date → Reminder
Workflow Orchestration
A sequence of operations must coordinate data, decisions, and actions to advance a business process.
- Find other data
- Use output from one operation in another
- Create or modify records
- Process multiple results
- Repeat actions
- Branch into different paths
- Coordinate dependent steps
- Continue based on previous results
The line is not “simple versus complicated.”
The line is what kind of problem we're solving.
Part 17
Don't Reach for the Bigger Hammer
Discovering a more general automation capability should not tempt us to replace every specialized mechanism.
Status Complete → Email Supervisor
Use the appropriate native communication mechanism.
Send Open Tasks Report Weekly
Subscription may be ideal.
Three Days Before Due Date
Reminder naturally expresses record-relative timing.
Remember This
Use the simplest native mechanism that completely and clearly expresses the business requirement
Escalate when the requirement demands orchestration—not because a broader automation tool sounds more powerful.
Part 18
The Automation Escalation Ladder
This is a course mental model, not an official Quickbase scale.
Level 1 — Evaluate
Does this qualify?
Level 2 — Communicate
Tell somebody.
Level 3 — Retrieve
Find additional information.
Level 4 — Pass Data
Use one operation's result somewhere else.
Level 5 — Decide
Choose what happens next.
Level 6 — Act
Create, modify, or change something.
Level 7 — Iterate
Perform operations across multiple results.
Level 8 — Orchestrate
Coordinate the complete sequence.
Part 19
The Questions a Builder Starts Asking
We are not answering these in detail yet. They are no longer distractions—they are the questions the next phase of the curriculum must answer.
Remember This
Those questions are no longer distractions. They are our new curriculum.
We now have a reason to investigate a broader automation model.
Lesson 7 Boundary Quiz
Communication or Orchestration?
Every item tests architectural judgment rather than menu terminology.
Progress
0/12
Quiz Convention
TRUE = the requirement can naturally remain within the specialized communication mechanisms studied so far.
FALSE = the statement crosses into orchestration territory or claims escalation when it is not needed.
When Status changes to Complete, email the supervisor. This requirement alone gives us a reason to leave native communication automation and use workflow orchestration.
When Status changes to Complete, find all other Open Tasks assigned to the same user. This requirement still fits naturally inside communication automation.
Every Monday send management a composed briefing containing three current Quickbase reports. This necessarily requires workflow orchestration because multiple reports are involved.
Remind each Assigned To user three days before their Task's Due Date. We need workflow orchestration because every Task may have a different Due Date.
Find every overdue Task, modify each qualifying record, then use the results to determine what happens next. This still fits naturally within the communication mechanisms studied so far.
Every Friday send the Open Tasks report to everyone in the Participant role. Because this happens repeatedly, workflow orchestration is required.
If Status is Complete AND Assigned To is not empty, send a Custom Email. Because the requirement contains Boolean logic, workflow orchestration is required.
When a Task becomes Complete, create another Quickbase record using values from the completed Task. Because a familiar record event initiated it, this still belongs naturally to the same communication automation model.
Every Monday send a report, but don't send it when the report is empty. The conditional behavior means we need general workflow branching.
For each overdue Task, check whether a related Follow-Up exists. Create one only when none exists. This still fits naturally inside a Reminder because Due Date is involved.
Send an email when Status changes, and include the previous and current values. Because both old and current state are needed, workflow orchestration is required.
When a Task becomes Complete, find that user's remaining Open Tasks, identify the overdue ones, create missing Follow-Ups, update a tracking record, and finally email the supervisor. Because the workflow ends with an email, this is fundamentally communication automation.
Ready to draw the line?
Answer all 12 questions. The traps are deliberate: recurring ≠ orchestration, Boolean logic ≠ orchestration, multiple reports ≠ orchestration, and email at the end ≠ communication architecture.
Part 21 — Final Reveal
TRIGGER
RETRIEVE
PASS DATA
EVALUATE
BRANCH
ITERATE
CREATE / MODIFY
CONTINUE
COMMUNICATE
We know what we need.
We don't merely need another kind of email. We need a mechanism designed to move information through a workflow, carry data from one operation to another, make decisions, coordinate actions, and advance a business process.
The Door Opens
Enter Pipelines.
In Lesson 8, we finally open the mechanism Quickbase provides for this broader class of automation. But we will not begin by memorizing its interface.
We already have something much more useful: a reason for every major capability we're about to encounter.
We learned communication automation by asking when Quickbase should speak.
Now we're going to learn workflow automation by asking what Quickbase should do next.