NextoraPipeline, workflow, form or template: choosing the right automation for the job
Four tools that look interchangeable and are not. A rule for picking between them in one question, the full list of events a workflow can start from, and why a generated automation should always be saved switched off.
"Can we automate this?" almost never has one answer, because most business systems ship four different tools that all qualify. In Nextora they sit on one screen — pipelines, workflows, forms and email templates — and mixing them up costs more than learning the difference once.
| Tool | What it does | Reach for it when |
|---|---|---|
| Pipeline | Moves deals through named stages | The process is a sequence a human walks through |
| Workflow | Reacts to an event and does the work | Something must happen by itself |
| Form | Collects enquiries from outside | The trigger is a stranger, not a record |
| Template | Stores text you send repeatedly | Nothing needs to be automatic; you are tired of retyping |
The one question that picks the tool
Where does the event come from?
- From outside — a visitor filled in a form, an email arrived, a webhook knocked. Start with the form or the channel, then hang a workflow off the result.
- From inside — a deal changed stage, a task went overdue, a field changed. That is a pure workflow.
- Nowhere — nothing needs to happen automatically, you just want the text ready. That is an email or document template.
A worked example: the website form creates a lead; a "when a lead is created" workflow assigns a task to a manager and sends a welcome email from a template; the pipeline carries the deal from First contact to Paid. Four tools, one loop, each doing the job it is shaped for.
A trigger decides two things
The trigger is the first node of a workflow, and it fixes both when the automation wakes up and what data it starts with. In Nextora it cannot be changed afterwards — so it is worth knowing the catalogue.
On CRM records
| Trigger | When it fires |
|---|---|
| On create | A record appeared — typed in, from a form, from an import, or from another workflow |
| On field change | The named field's value changed |
| On delete | The record was deleted |
| No activity | Nothing happened on the record for longer than the period you set |
| Enters / leaves a stage | Deals only: the card arrived at a stage, or left it |
| Time in stage / deal stuck | The deal has been sitting in a stage longer than you allow |
| Deal value changed | The amount changed — after a quote was recalculated, say |
Conversations and tasks add their own: a message received on any connected channel, an email received, and the task events. The catalogue is grouped by object with a module rail — CRM, communication, productivity, marketing, automation — and a count beside each, which is itself informative: deals have nine events, chat has one.
Conditions are a filter at the door
Record events carry a Conditions block: the event happened, but the workflow starts only if the record matches. "When a lead is created" plus Status equals Qualified leaves every other lead alone. Conditions read the entity's own columns under the same names as the table, custom fields included, joined by AND or OR. An empty list means "always fire".
One subtlety worth knowing in any system: conditions are evaluated against the record at the moment of the event. For a deletion, that is the record as it was just before it went.
Describing an automation in words — and the guardrails around it
Above the workflow list there is a field where you describe the rule in a plain sentence — "if a deal sits in negotiation for over a week, task its owner" — and the automation is assembled step by named step. Three details make that safe rather than alarming:
- It looks around first. The builder reads your real pipelines, stages, fields and people, so it points at things that exist instead of inventing plausible ones. If a stage or a person is missing, that step simply does not appear — and a line at the bottom says what the automation does not do.
- It builds on the server. Close the page and the work still finishes; Cancel build discards the draft and writes nothing; Try again redoes the failed step rather than everything.
- It is saved switched off. Deliberately. An automaton that starts sending mail and moving deals before anyone has read it is not a gift. You switch it on from the card once you agree with every step.
The number that tells you an automation is lying to you
An active workflow with 0 runs in 30 days is a signal, not a null: either the event never happens or the trigger is watching the wrong thing. Pair it with the success share — the proportion of the month's runs that finished without an error — and you can audit a whole workspace of automations in a minute.
Read the run history, not the config
A workflow card in Nextora shows the state badge, the trigger, how many times it fired in the last month, the share of runs that finished cleanly, and a strip of the last fourteen runs — green for success, red for failure, amber for running, grey for cancelled. The error line appears only when the latest run failed; an old failure followed by successes does not linger.
That is the honest version of automation reporting. A decorative chart that is not counting real rows is worse than nothing, because it makes people stop checking.
Four rules of thumb
- Automate the handoff, not the thinking. Assignment, notification, task creation and follow-up sequences pay off immediately; a rule that decides who is worth calling rarely survives contact with reality.
- One trigger, one job. Two small workflows are easier to audit than one with a branch nobody understands.
- Put the condition on the trigger, not in a step. Filtering at the door keeps the run log meaningful — you see the runs that mattered.
- Check zero-run workflows monthly. They are how automation quietly stops matching the process.
Where the events themselves come from is the other half of the story: the record model decides what a trigger can even watch, and forms decide whether an enquiry arrives as a record at all. The tools themselves live on the automation page.
See it on your own process.
Nextora is in private alpha: CRM, projects, ERP, omnichannel conversations and AI employees on one record model. Bring the process you want to fix and we will shape the workspace around it.