Skip to content
Tutorials Center
My learning

Topics

Lesson 19 of 39 ยท Workflows and Flow Designer

Flow Designer: Low-Code Automation in ServiceNow

Learn how ServiceNow Flow Designer automates work with flows, triggers, actions and execution logs, and how it replaced the older Workflow Editor.

Every company repeats the same chains of steps: a new hire is created, so an account is requested, a laptop is ordered and a manager is notified. In ServiceNow you build these chains in Flow Designer, a low-code editor where you pick a trigger, then add steps one after another without writing code. The result is called a flow, and the platform runs it for you each time the trigger fires.

This lesson explains what Flow Designer is made of and how a flow runs. The next lessons go deeper into triggers, data and subflows.

ServiceNow is a commercial cloud product, so Flow Designer cannot run on this site. The lessons describe menus and behavior precisely, and each one includes a small stand-in written in JavaScript that models the same idea. Every stand-in is labelled. To try the real thing, request a free Personal Developer Instance (PDI) from the ServiceNow developer site.

Where to find it

In the navigator (the left menu), type Flow Designer in the filter box and open Process Automation > Flow Designer. The home page lists your flows, subflows, actions and executions. Use the New button to start a flow, a subflow or an action.

The parts of a flow

A flow has three kinds of building blocks:

  • Trigger: the one event that starts the flow. There is exactly one per flow.
  • Actions: steps that do something, such as Create Record, Update Record, Send Email or Ask For Approval.
  • Flow logic: steps that control the path, such as If, Else, For Each, Wait For Condition and Do The Following In Parallel.

Between steps, data travels as data pills. A pill is a draggable chip that stands for a value, such as the trigger record's short description. You will meet pills properly in a later lesson.

flowchart TD
    T["Trigger: record created on Incident"] --> I{"If priority is 1"}
    I -->|yes| A["Action: Send email to on-call"]
    I -->|no| B["Action: Update record, set assignment group"]
    A --> E["Flow ends"]
    B --> E

One trigger, then ordinary steps and a branch. Flow Designer draws exactly this tree on screen.

Flow, subflow, action, playbook

ServiceNow offers several automation containers, and beginners often mix them up.

Item Starts from Reusable by others Typical use
Flow A trigger No Run automatically when something happens
Subflow A call from another flow Yes A routine you call from many flows
Action A call from a flow or subflow Yes One step, possibly with a script inside
Playbook A record, with human steps Yes Guided processes with tasks and people

Rule of thumb: build a flow for the event, a subflow for a routine used in more than one place, and an action when you need a new kind of step.

Flow Designer and the older Workflow Editor

Before Flow Designer, ServiceNow had the Workflow Editor, a canvas of boxes joined by lines. Many older instances still contain workflows, and they keep running. New work should be built in Flow Designer, because it is easier to read, supports testing, and has execution logs per step. Workflows can be called from a flow through a legacy action, and you can migrate them gradually instead of rewriting everything at once.

How a flow runs

When the trigger condition is met, the platform creates a context: a record of that one run, holding every step's inputs and outputs. If you open Flow Designer > Executions, you see a list of contexts with their state (Queued, In Progress, Complete, Error, Cancelled). Opening one shows, step by step, what the flow received and produced. This is the first place to look when an automation does something unexpected.

Flows run as a user. By default a record-triggered flow runs as the system, so it can update records the triggering user could not. You can switch a flow to run as the user who started it, which is the safer choice when the automation should respect that person's permissions.

Draft, test, publish

A flow starts in Draft. You can use the Test button to run it against a chosen record, without publishing. Test results appear in the same execution view. Only a published flow reacts to real events. If you change a published flow, you edit a new draft, then publish again. Activating and deactivating are separate steps.

A model of how a flow executes

The stand-in below is not ServiceNow code. It is a few lines of JavaScript that behave like a tiny flow engine: each step receives the context, may add outputs, and the engine records a log you can read afterward. The point is the shape: trigger data goes in, steps run in order, every step leaves an execution record.

JS Stand-in: a tiny flow engine with an execution log

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Change the priority to 3 and notice that this simple engine still runs every step. Real flows put the later steps inside the If block, so they are skipped. The next stand-in adds that behavior.

JS Stand-in: steps inside an If block

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Good habits from day one

  1. Name every step. Rename "Update Record 3" to "Set assignment group". The execution log uses your names.
  2. Keep flows small. If a flow grows past about fifteen steps, move a routine into a subflow.
  3. Test with real records on a non-production instance before publishing.
  4. Check the executions after publishing: an automation you never look at is a silent risk.
  5. Prefer Flow Designer to scripts. Use a script step only when no built-in action does the job.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. How many triggers does a flow have?

    A flow starts from exactly one trigger. If you need the same steps from several events, put them in a subflow.
  2. 2. Which item can be called from many different flows?

    A subflow is a reusable routine that other flows and subflows call.
  3. 3. Where do you look to see what a flow did on a particular run?

    Each run creates an execution with per-step inputs and outputs.
  4. 4. A flow is in Draft. What happens when a matching record is created?

    Draft flows can be tested manually but do not respond to real events until published.

Summary

  • Flow Designer builds automations from one trigger followed by actions and flow logic.
  • Data pills carry values between steps; flows, subflows and actions are the reusable containers.
  • Executions show every step's inputs and outputs, which is the main debugging tool.
  • Draft, test, then publish; new work belongs in Flow Designer instead of the legacy Workflow Editor.

Next: Flow Triggers and Conditions