CSA Guide

Introduction to Flow Designer for Admins

Introduction

Flow Designer is ServiceNow's low-code/no-code process automation tool. It replaces legacy Workflow (the classic visual workflow editor) with a more modern, maintainable, and administrator-friendly interface. With Flow Designer, you can automate multi-step processes—routing approvals, sending notifications, creating records, calling APIs—using a guided, step-by-step canvas.

This guide is written for Administrators who are new to Flow Designer and want to build their first flows confidently.

Flow Designer Concepts

Flows

A Flow is the top-level automation object. It defines a complete end-to-end process with a single trigger and a sequence of steps (actions and logic).

Subflows

A Subflow is a reusable block of steps that can be called from multiple flows. Build common patterns (like "Send Approval + Wait") as a Subflow and reference it everywhere.

Actions

An Action is a reusable step that performs a single task—creating a record, sending an email, looking up a value, or calling an external API. ServiceNow includes hundreds of out-of-the-box Actions, and you can create custom Actions for specialized needs.

Triggers

The Trigger is what starts the flow. Common trigger types:

Trigger	When It Fires
`Record Created`	When a new record is inserted
`Record Updated`	When a record's field changes to a specific value
`Record Deleted`	When a record is deleted
`Scheduled`	On a time-based schedule (daily, hourly, CRON)
`SLA Breach`	When an SLA metric reaches a threshold
`Inbound Email`	When an email arrives matching conditions
`Spoke Trigger`	Custom trigger from an IntegrationHub spoke

Building Your First Flow

Scenario: Auto-assign a high-priority incident

When a P1 incident is created, automatically assign it to the Major Incident team and send a Slack notification.

Step 1: Open Flow Designer

Process Automation > Flow Designer

Step 2: Create a New Flow

Click New > Flow

Name: Auto-Assign P1 Incidents
Application: Global (or your scoped app)
Description: Automatically assigns P1 incidents to Major Incident team and notifies Slack

Step 3: Set the Trigger

Click Add a Trigger:

Trigger: Record Created or Updated
Table: Incident [incident]
Condition: Priority | is | 1 - Critical

Step 4: Add a Look Up Records Action

Click Add an Action:

Action: Look Up Records
Table: Group [sys_user_group]
Conditions: Name | is | Major Incident Team
Output Variable name: Major Incident Group

Step 5: Add an Update Record Action

Action: Update Record
Record: Trigger → Incident Record
Field: Assignment Group → Major Incident Group > Records > First Record > Sys ID
Field: Assigned to → (leave blank — let the team decide)

Step 6: Add a notification

Action: Send Email
To: major.incident@company.com
Subject: [P1 Alert] + Trigger → Incident Record → Number
Body: A new P1 incident requires immediate attention: + short_description data pill

Step 7: Activate

Click Activate (top right). The flow is now live.

Data Pills: Passing Data Between Steps

Data Pills are Flow Designer's way of referencing outputs from previous steps. They appear as teal pills in text fields and action inputs.

Trigger
  └─ Incident Record
       ├─ Number              → [Trigger → Incident Record → Number]
       ├─ Short description   → [Trigger → Incident Record → Short Description]
       └─ Caller
            └─ Email          → [Trigger → Incident Record → Caller → Email]

You can chain data pills multiple levels deep to reach related record fields.

Flow Logic: If, For Each, Wait

If/Else Conditions

[Trigger]
  ↓
[If: Priority is 1]
  ↓ Yes
  [Assign to Major Incident Team]
  ↓
[Else If: Priority is 2]
  ↓ Yes
  [Assign to Service Desk Lead]
  ↓
[End If]

For Each: Iterating Over Lists

[Look Up All Open P1 Incidents]
↓
[For Each Incident in Results]
  ↓
  [Send reminder notification to assigned user]

Wait: Pause Until a Condition is Met

[Create Approval Record]
↓
[Wait for Approval | Condition: Approval State = Approved OR Rejected | Timeout: 48 hours]
↓
[If: Approved]
  → [Proceed with change]
[If: Rejected / Timeout]
  → [Notify requester]

Approvals in Flow Designer

Flow Designer has a built-in Ask For Approval action:

Action: Ask For Approval
- Table: Change Request [change_request]
- Record: [Trigger record]
- Approval type: One of the following users/groups
- Approvers: [Lookup → Change Advisory Board group]
- Due date: [now + 5 days]

The flow pauses until the approval is resolved, then branches based on the outcome.

Flow Designer vs. Legacy Workflow

Feature	Flow Designer	Legacy Workflow
Interface	Modern, step-based	Drag-and-drop canvas
Reusability	Subflows, Actions	Activities
Testing	Built-in test mode	Limited
Debugging	Execution detail log	Basic
IntegrationHub	Full support	Limited
Recommended for new work	✅ Yes	❌ No

ServiceNow recommends migrating all new automation to Flow Designer. Legacy Workflow continues to work but receives no new investment.

Best Practices

Always add a clear Description to your flow explaining what it does and why
Use Subflows for any logic used in more than one flow
Test flows in a PDI or sub-prod using Flow Designer's built-in Test feature
Use Wait for Condition with a timeout to prevent flows from running indefinitely
Annotate complex flows with comments (right-click steps)
Set a meaningful Run As user (usually a service account)
Monitor the Execution Log for errors after activating

Conclusion

Flow Designer democratizes process automation in ServiceNow. Admins who previously needed a developer to write Business Rules can now build sophisticated, multi-step workflows through a guided visual interface. Start with simple flows, master data pills and conditionals, and gradually introduce Subflows for reusable logic. The investment pays off in faster delivery and easier maintenance.