What is a workflow?

Writing a workflow down turns habits into something a team can inspect. Once the steps are visible, people can see where work waits, which step has no owner and which exception nobody handles. That holds even if nothing is ever automated: many workflows live happily as a checklist.

It is also the unit that automation tools work with. Before you can automate anything, you need the workflow: the trigger, the steps, the decisions and the ending. IBM's explainer describes a workflow as simpler and more repeatable than a full business process, usually drawn as a diagram or checklist, and that simplicity is what makes it automatable.

Every workflow has the same parts. A trigger starts it: a form submitted, a file uploaded, a date reached. Steps do the work, each with an input and an output. Conditions choose between paths, such as sending large orders one way and small ones another. An end state says the work is done, and ideally a record shows how it got there.

When software runs the workflow, a workflow engine holds the definition and executes one instance per piece of work. If ten purchase requests arrive, ten instances run, each with its own data and its own position in the steps. The engine moves an instance forward when a step completes, waits when a step needs a person, and retries or raises an alert when a step fails.

Workflows come in different shapes. A sequential workflow runs steps in a fixed order. A branching one takes different paths by condition. Some run steps in parallel and join the results. Long-running workflows may wait days for an approval, so the engine must store state rather than hold it in memory.

An employee submits a request for a new laptop through a form. That submission is the trigger. Step one checks the request against the hardware policy: model, cost and whether the employee's current laptop is due for replacement. A condition then splits the path. Requests inside policy go straight to IT; anything outside policy goes to the employee's manager to approve or decline.

Once approved, IT receives a task to order the device, and the workflow waits until IT marks it shipped. The final step tells the employee and updates the asset register. Each request carries its own history: when it arrived, who approved it, when it shipped. When the policy changes, the team edits the workflow once, and every new request follows the new rules.

Workflows are a core object in Swfte Studio. You build them on a visual canvas with branches and loops, connect tools through the integrations catalogue, and add an approval step that pauses an instance until a named person decides. A denial stops the run unless the workflow has a branch for it.

Studio also lets an agent act as one step inside a workflow, which helps when one step needs to read free text before the fixed steps continue. Workflows have versions with promote and rollback. The broader subject of automating workflows, and where Studio sits among other tools, is on the workflow automation page.

• Swfte Studio
• Governed workflows
• Workflow automation

Definitions on this page were read on the sources below on 7 October 2026. Where sources define the term differently, the page says so. The full glossary lists more terms.