Steps & logic
A workflow is a sequence of steps. There are three kinds.
Actions
Section titled “Actions”Actions do something. Common actions include:
- Create / update a record — create the item being processed, or change its data and status.
- Create a task — assign work to a person or role, and (optionally) wait for them to complete it.
- Assign a user — route the record to an owner.
- Request approval — pause for a human approve/reject decision.
- Send email / send SMS — notify customers or staff.
- Create a payment link — collect a payment (requires the Stripe integration).
- Set a due date — put an SLA/target date on the record.
- AI steps — classify, prioritise, or make a decision automatically based on the record’s data.
Decisions
Section titled “Decisions”A decision step branches the workflow down different paths based on the data — for example, routing a request one way if an amount is over a threshold, or handling an approval’s approved and rejected outcomes differently.
- Each decision has one or more conditions plus a default path.
- assess.one adds decisions automatically when your description implies different outcomes (“if…”, “when…”, “depending on…”, “escalate if…”).
A wait step pauses the workflow for a fixed amount of time (for example, a 24-hour cooling-off period) before continuing.
Approvals and rework loops
Section titled “Approvals and rework loops”A very common pattern is do work → request approval → branch on the outcome:
- Approved → continue to the next stage.
- Rejected → either close the record, or send it back for revision and resubmission (a rework loop).
assess.one wires these patterns for you when your process needs them.
