Five concepts explain almost everything in BreezThru: workflows, runs, steps, automation levels, and targets.
A workflow is a reusable recipe of steps that produces a known outcome. The platform ships with one:
assess_offer
Gather a target → verify it → draft a client-facing offer.
A workflow defines, for each step, what it needs, what it produces, and how automated it can be.
A run is one execution of a workflow: one pass through its steps, end to end. A run has:
open, running, blocked, failed, completed, or cancelled.You create a run from the Runs screen, and follow it on the run's own page.
A step is one task inside a run. Each step is a Job with its own status (pending, processing, awaiting_approval, completed, failed, and more).
A step:
The run page shows the whole pipeline: completed steps, the step currently waiting on you, and steps that haven't started yet.
Every step runs at one of three levels:
| Level | Name | Who does it | Human approval |
|---|---|---|---|
| L1 | Autonomous | An automation | None |
| L2 | Automation + approval | An automation | A human must approve the output |
| L3 | Manual | A human | N/A (fully manual) |
Each step also has a ceiling, the maximum level it's allowed to reach, so client-facing work is never fully automated without a human.
Read Automation levels for the full picture.
A target is the company or person a run is about: the CRM record behind every run. A target holds its name, domain, website, Companies House number, LinkedIn, a summary, contacts (emails, phones, addresses), notes, and the full history of runs done for it.
See Targets.