Self Service & Automation · Topic 3 of 4
Workflow Studio
ServiceNow Workflow Studio: flows, triggers, actions, subflows, flow logic, approvals, testing, publishing and executions explained for the CSA exam.
- 4 min
- A flow is trigger plus actions plus flow logic.
- Triggers include record, schedule and application triggers.
- Subflows and actions are the reusable pieces.
What it is
Workflow Studio is the low-code tool for building automation on the platform. You assemble a flow from a trigger and a series of actions, with no scripting needed for most tasks.
A flow runs whenever its trigger fires, such as a record being created, a schedule coming due, or a catalog item being ordered.
How it works
The parts of a flow
| Part | What it does |
|---|---|
| Trigger | Starts the flow: a record created or updated, a schedule, or an application event such as the Service Catalog |
| Condition | Limits the trigger to matching records, for example Priority is 1 |
| Action | One step, such as Create Record, Update Record, Look Up Record, Send Email, Create Task or Ask For Approval |
| Flow logic | Controls the path: If, Else, For Each, Wait, and similar |
| Data pills | References to values from the trigger or earlier steps, passed into later steps |
Flows, subflows and actions
| Item | Purpose |
|---|---|
| Flow | Has a trigger and runs on its own |
| Subflow | A reusable sequence of steps with inputs and outputs, started by a flow or another subflow, with no trigger of its own |
| Action | A reusable single step with inputs and outputs |
Build a subflow when the same group of steps is needed in many flows. Build a custom action when a single operation will be reused. Actions are grouped in spokes for integrations, some of which need additional licensing, so the exam stays on the core actions.
Approvals inside a flow
The Ask For Approval action sends an approval request and waits. The approval rule says when the request counts as approved, for example any one approver or all approvers.
The action completes as soon as the approval is decided either way. The flow then simply continues unless you add an If step that branches on the approval outcome. Always branch on the result when rejection must stop the work.
Testing, publishing and running
A flow starts as a draft. Test lets you run it against a chosen record before it goes live. Publish makes it live so the trigger can run it.
If you save changes to a published flow without publishing them, the previously published version keeps running. Changes only take effect after you publish again.
Each run is recorded. Open the flow's executions in Workflow Studio to see which steps ran and where a failure happened. This is the first place to look when a flow did not do what you expected.
Flows compared with business rules
| Need | Better fit |
|---|---|
| Multi-step process: approvals, tasks, notifications | Flow |
| Immediate logic when a record is saved, such as setting a field before insert | Business rule |
| Process maintained by non-developers | Flow |
| Logic that must run before the record is saved | Business rule (before) |
Older workflows built in the legacy workflow editor may still exist, but new automation is built in Workflow Studio.
How the exam asks about this
- "When a high priority incident is created, notify the group and open a task." A record triggered flow.
- "The same steps are needed in five flows." Create a subflow.
- "A flow always continues after an approval, even when it is rejected." Ask For Approval completes on any response, so add an If step on the outcome.
What to remember for the exam
- A flow is trigger plus actions plus flow logic.
- Triggers include record, schedule and application triggers.
- Subflows and actions are the reusable pieces.
- Ask For Approval finishes on any decision; branch on the result.
- A published flow keeps running its published version until you publish again.
- Executions show what each run did.
Older material may use a previous name for this tool. If a question describes the current low-code automation tool, the name is Workflow Studio.
Common mistakes
Assuming a rejection stops the flow. Without a branch on the approval result, the next actions run regardless.
Saving but not publishing. The change looks complete in the editor, yet the old published version is still what runs.
Using a flow for an instant field default. Logic that must run as the record is saved belongs in a business rule.
Check yourself
What starts a flow?
A trigger, such as a record event, a schedule or an application trigger like the Service Catalog.
What happens to the published version when you save edits without publishing?
The previously published version keeps running until the edits are published.
Why does a flow continue after a rejected approval?
Ask For Approval completes on any response, so the flow needs an If step on the outcome to stop work.
Topic 3 of 4 in Self Service & Automation
Test yourself on Self Service & Automation
The full ServiceNow CSA question bank has 600 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by ServiceNow. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.