What automation actually means in Expedify
Open any Expedify workflow and you're looking at three things wearing different names: something that starts it, boxes that do things, and lines connecting them. That's it. This lesson is you learning to see those three things everywhere — then never un-seeing them.
The three pieces
A trigger is the one thing that starts a workflow — a new lead, an incoming WhatsApp message, a clicked button, a changed database row. Every workflow has exactly one.
After the trigger, everything else is a node. A node does one job — send a message, ask an AI a question, update a record — and hands its output to whatever comes next.
The order nodes run in is just the order they're connected. There's no separate flowchart to keep in sync — the connections are the logic.
- Database Change Trigger — a CRM record is created, updated or deleted
- User Message Trigger — someone messages your web chat or WhatsApp
- Webhook Trigger — another system sends you an HTTP request
- Scheduler — a clock, not an event
- Click Trigger — a person presses a button in the CRM
See it in one real workflow
Here's a real four-node Expedify workflow — the kind a lot of businesses run on day one. Click any node to see exactly what it's configured to do — the same panel you'd see in the builder itself.
New lead → welcome email → AI qualifies → CRM updated
A new contact gets the welcome email, an AI agent decides how warm the lead is, and the CRM record is updated with its answer — nobody on the team touches this by hand.
Scroll for all 4 steps →
Notice what didn't need a developer. Every one of these four nodes is a form, not code. That's the whole premise of Expedify workflows — the logic is code-shaped (trigger → node → node → node), but the authoring isn't.
Key takeaways
- A workflow is a trigger, one or more nodes, and the connections between them.
- Every workflow has exactly one trigger, and as many nodes as the job needs.
- A node's output is available to every node after it — that's how “the AI's answer” becomes “the value the CRM update uses.”
- Clicking a node always shows the same shape: what it's configured to do, in plain fields — nothing hidden.
Try it yourself
Before the next lesson, open the workflow above one more time and find the node whose output the welcome email actually depends on. (It's the trigger — the Send Template Message node's Contact Input Variable reads the contact id from there.) That question — where did this value come from — is the one you'll be asking constantly once you start building your own.
Next: Triggers — the five ways a workflow can start, and how to pick the right one for what you're automating.
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