4.2 Flow Designer & Workflow Automation
Key Takeaways
- Flow Designer is the current low-code automation tool in ServiceNow; flows are built from a trigger, actions, and flow logic, and can call reusable subflows and actions from the Action Designer and Integration Hub spokes.
- A flow trigger fires on a record event (Created, Updated), a schedule, an inbound REST/email event, or a Service Catalog request, and only one trigger starts a given flow.
- The legacy Workflow editor (Graphical Workflow) uses a drag-and-drop canvas of activities on the wf_workflow table and remains in maintenance mode; ServiceNow positions Flow Designer as the strategic successor.
- Approvals can be modeled in Flow Designer with the Ask for Approval action or as approval activities in legacy workflow, generating sysapproval_approver records.
- Choose Flow Designer for new automation and natural-language maintainability; only extend an existing legacy workflow when a process is already built on it and migration is not yet feasible.
Why Automation Tooling Matters for the CSA Exam
Automation is the engine behind self-service. When a catalog item is ordered, when an incident is created, or when a record meets a condition, the platform should react without a human pushing it along. ServiceNow provides two automation builders, and the CSA exam expects you to know the difference, the parts of a flow, and which tool to choose.
Flow Designer is the modern, low-code tool. The legacy Workflow editor (also called Graphical Workflow) is the older drag-and-drop canvas. Both can run business logic, route work, and request approvals — but ServiceNow's strategic direction is Flow Designer.
Anatomy of a Flow
A flow in Flow Designer is composed of three building blocks. Knowing these by name is exam-critical.
| Component | Purpose | Example |
|---|---|---|
| Trigger | The single event that starts the flow | A record is Created on sc_req_item |
| Action | A reusable step that does work | Create a task, send a notification, look up a user |
| Flow Logic | Control structures that shape execution | If, Else, For Each, Do Until, Wait For |
A flow has exactly one trigger. Common trigger types:
- Record-based — fires when a record is Created, Updated, or Created or Updated on a table, with optional conditions.
- Scheduled — fires on a daily, weekly, monthly, or repeating schedule.
- Application / inbound — fires from a REST call, an inbound email, a Service Catalog request, or a Service Level Agreement (SLA) event.
Actions and the Action Designer
An action is a reusable, self-contained operation. ServiceNow ships hundreds of actions, and Integration Hub spokes add actions for external systems (Microsoft Teams, Slack, Active Directory). The Action Designer lets administrators build custom actions from steps such as REST, script, or record operations, with defined inputs and outputs.
Subflows
A subflow is a reusable sequence of actions and logic that accepts inputs and returns outputs, callable from many flows. Subflows promote reuse: build an "Onboard Employee" subflow once and call it from several catalog flows. The distinction between an action (a single operation) and a subflow (an orchestrated sequence) is a common exam point.
The Legacy Workflow Editor
The Workflow editor (Graphical Workflow) predates Flow Designer. Administrators drag activities — Approval, Run Script, Create Task, Notification, Timer, conditional branches — onto a canvas and connect them with transitions. Published workflow definitions are stored on the wf_workflow table, and a running instance is a workflow context on wf_context.
The legacy Workflow editor is in maintenance mode: it still runs and can be edited where it already exists, but ServiceNow is not investing in new feature development for it and positions Flow Designer as its replacement. Many older Service Catalog items still attach a legacy workflow as their fulfillment process; newer items attach a flow.
Modeling Approvals
Approvals gate automation until a person agrees. Both tools can request them, and both generate Approval records on sysapproval_approver.
- Flow Designer uses the Ask for Approval action. You specify approvers (users, groups, or via approval rules) and branch the flow on Approved or Rejected outcomes.
- Legacy Workflow uses Approval - User and Approval - Group activities, with transitions for the approval result.
For catalog requests, approval is typically driven from the flow or workflow attached to the catalog item, and the approver acts on the RITM.
Flow vs. Workflow: The Decision Rule
| Factor | Use Flow Designer | Use Legacy Workflow |
|---|---|---|
| New automation | Yes (strategic default) | No |
| Maintainability | Natural-language, low-code | Canvas; harder to read at scale |
| Existing process already on workflow | Plan migration over time | Extend only if migration is not yet feasible |
| Reusable logic across processes | Subflows and custom actions | Limited reuse |
| ServiceNow investment | Active development | Maintenance mode |
The CSA-level rule of thumb: build new automation in Flow Designer. Touch a legacy workflow only to maintain a process that is already implemented on it and cannot yet be migrated. Knowing this strategic direction — not just the mechanics — is what the exam rewards.
Which statement best describes the relationship between Flow Designer and the legacy Workflow editor in current ServiceNow?
In Flow Designer, which component is a reusable sequence of actions and logic that accepts inputs and returns outputs and can be called from multiple flows?
How many triggers can a single flow have in Flow Designer?
An administrator needs an approval step in a new catalog fulfillment flow. Which Flow Designer element should be used, and what record does it generate?