What is Flow Designer in ServiceNow?
Flow Designer is ServiceNow’s low-code tool for automating processes. You build a flow from a trigger and a series of actions written in plain language, without needing to write code.
Triggers, actions and logic
Every flow starts with a trigger: a record being created or updated, a schedule, an inbound email, a Service Catalog request, or another application event. After the trigger come actions, such as Create Record, Ask for Approval, Send Email or Look Up Records, plus flow logic like If, For Each and Wait for Condition. Data from earlier steps is dragged in as data pills.
Subflows and reusable actions
Subflows are reusable sequences of steps that several flows can call, like a function in code. Custom actions package your own logic, including REST calls or scripts, into a building block that non-developers can use. IntegrationHub adds hundreds of prebuilt actions for external systems.
A practical example
A flow triggered by a new laptop request asks the requester’s manager for approval, creates a catalog task for the hardware team, waits until it is closed, then updates the requested item and notifies the user. The whole process is readable on one screen.
Flow Designer vs. legacy workflow
ServiceNow recommends Flow Designer for new automation instead of the legacy Workflow Editor. Flows are easier to read, test and maintain, and they appear alongside playbooks and other automation in Workflow Studio in recent releases.
Best practices
Keep flows short and move repeated parts into subflows. Name flows and steps clearly so others can follow them. Use the Test button and execution details to debug, and avoid scripts inside flows where a standard action exists.
Frequently asked questions
Do I need to code to use Flow Designer?
No. Most flows can be built entirely with standard actions. Scripting is available when you need it.
Should I migrate legacy workflows to Flow Designer?
For processes you are actively changing, yes. Stable legacy workflows can usually be migrated gradually.
What is the difference between a flow and a subflow?
A flow has its own trigger. A subflow has inputs and outputs and is called from flows or other subflows.
Related ServiceNow terms
Need help with Flow Designer or anything else in ServiceNow? We’re here with practical solutions that fit your organization and your teams.
Browse all 100 ServiceNow terms
ServiceNow is a trademark of ServiceNow, Inc. This glossary is an independent resource by Sequal Consultancy and is not affiliated with or endorsed by ServiceNow, Inc.