The three parts of a workflow
Every automation in your demo org is the same three things arranged differently. Learn to see them and the whole catalogue stops being nineteen mysteries.
Your demo org runs 19 workflows. They cover a lead arriving, a call being made, a message being written, money being reported back to an ad platform. They look like 19 different things. They are one thing, built 19 times.
Three parts, and there is no fourth
- A trigger. The one event that starts it. Every workflow has exactly one, it is always the first box, and nothing runs until it happens.
- Nodes. Boxes that each do one job — look something up, ask an AI, write to the CRM, wait, send. A workflow is as many as the job needs.
- Connections. Lines from box to box. The order the lines run in is the logic; there is no separate flowchart kept in step with it.
If you can name those three on a canvas, you can read every automation in the org — including the ones nobody has explained to you, and including the ones a client asks you to build later.
The smallest one in your org
Open 8.1 · Tell Meta which leads were actually good. It is 3 nodes and it does something a finance business pays real money for: when an enquiry reaches a serious stage, it tells Meta that the ad which produced it was worth buying.
8.1 · Tell Meta which leads were actually good
A stage change starts it, one node fetches the person behind the deal, one node reports the event outward. Click any node to see what it is configured to do.
Scroll for all 3 steps →
Trigger, two nodes, two connections. That is a complete, working, production automation — and it is the whole grammar of the product on one screen.
The largest one in your org
6.1 · Send a 4-message follow-up over 21 days is the same grammar, 18 boxes deep. Do not read it yet. Just look at the shape and find the three parts.
6.1 · Send a 4-message follow-up over 21 days
One trigger, then a repeating pattern: wait, check whether they have replied, send the next message or stop. Four messages over three weeks.
Scroll for all 18 steps →
Nothing new appears at this size. The 18 boxes are the same kinds of box, and the 23 lines are the same kind of line. Complexity in this product is repetition, not a second language — which is the single most reassuring thing you can tell a client who has just seen a canvas like this one.
The word for a box, and the word for its name
| You will see | It means |
|---|---|
| A tile with a coloured icon | A node. The label on it — CRM Manager, Core Agent — is its type: what kind of job it does. |
| A short name under the tile | Its alias — find_contact, send_qualified. This one is unique inside the workflow, and it is how every other node refers to it. |
| Curly brackets in a field | One node reaching back for another node's answer, by that alias. Two lessons from here. |
A tile with a coloured icon
- It means
- A node. The label on it —
CRM Manager,Core Agent— is its type: what kind of job it does.
A short name under the tile
- It means
- Its alias —
find_contact,send_qualified. This one is unique inside the workflow, and it is how every other node refers to it.
Curly brackets in a field
- It means
- One node reaching back for another node's answer, by that alias. Two lessons from here.
Aliases are chosen by whoever built the workflow, and in this org they were chosen to be read: stage_change, find_contact, send_qualified. A workflow whose nodes are called crmmanager_1 and crmmanager_2 works exactly as well and is far harder to explain to a client.
Try it
- Open the workflows list in your org and read the 19 names without opening any of them. They are numbered in the order a customer meets them.
- Open three at random. For each, say out loud what starts it before you read anything else.
- Find the workflow with the fewest boxes and the one with the most. Confirm that the small one is not a toy and the big one is not a different product.
- Pick any node in any of them and say which single job it does. If you cannot, that is the next lesson's problem, not yours.
Next: Triggers: the six kinds this org uses — six answers to “what starts this?”, and which of your workflows uses each.
Related lessons
Base rates — what a piece of evidence is actually worth
A face-recognition system that is 99.9% accurate and almost entirely wrong, and a number that sent an innocent woman to prison. Both are the same arithmetic, and it is the arithmetic that decides what any piece of evidence is worth.
ReadConfirmation and survivorship — what you never looked for
Two questions about evidence you did not go looking for. One is a rule you have to discover, and one is a pattern in five famous people — and in both, the thing that would have told you the truth is the thing nobody checks.
ReadLoss aversion, sunk cost and regression — what it costs you
Four questions you answer about yourself rather than about a scenario, and your own answers are the finding. Then the pattern that makes praise look useless and criticism look like it works, whatever you actually do.
Read