ServiceNow Flow Designer

Flow Designer is ServiceNow's modern automation builder. It replaced the older Workflow Editor for most new development work. Flow Designer uses a clear step-by-step interface that both technical users and business analysts can read and edit. It connects to Integration Hub, enabling automation that reaches outside ServiceNow into third-party systems like Slack, Microsoft Teams, and Jira.

Flow Designer vs. Workflow Editor

Feature           │ Workflow Editor    │ Flow Designer
──────────────────────────────────────────────────────
Interface         │ Canvas/flowchart   │ Step list
Readability       │ Complex at scale   │ Clean and linear
Integrations      │ Limited            │ Full Integration Hub
Reusability       │ Low                │ High (Subflows, Actions)
Code required     │ Sometimes          │ Rarely
Recommended for   │ Legacy workflows   │ All new automation
──────────────────────────────────────────────────────

Accessing Flow Designer

Navigate to Process Automation > Flow Designer in the left navigation menu. Flow Designer opens in a full-screen browser experience separate from the main ServiceNow interface. The left panel shows existing flows, subflows, and actions. The main area shows the steps of the currently open flow.

Core Building Blocks

Trigger

Every flow starts with a trigger — the event that causes the flow to run. Common triggers include:

• Record Created: Flow runs whenever a new record is created in a table.
• Record Updated: Flow runs when a specific field changes on a record.
• Schedule: Flow runs at a set time — daily, weekly, or monthly.
• Service Catalog: Flow runs when a specific catalog item is submitted.
• Inbound API: An external system calls ServiceNow and triggers the flow.

Action

An action is one step inside a flow. Each action does one specific thing — creates a record, updates a field, sends an email, or calls an API. Actions are reusable building blocks. One action built for "Create Incident" works in every flow that needs to create an incident.

Flow: New Hire Setup
──────────────────────────────────────────────────────
TRIGGER: Service Catalog → "New Employee Onboarding" submitted
  │
  STEP 1: Ask for Approval → Manager of requester
  │         ├── Approved → Continue
  │         └── Rejected → Send notification → End Flow
  │
  STEP 2: Create Record → Incident [Configure workstation]
  │
  STEP 3: Update Record → RITM State = "In Progress"
  │
  STEP 4: Send Email → New employee + IT Team
  │
  STEP 5: Wait → Until Incident is Closed
  │
  STEP 6: Update Record → RITM State = "Fulfilled"
──────────────────────────────────────────────────────

Subflow

A subflow is a reusable flow that other flows can call. Instead of rebuilding a complex approval sequence in every flow, one subflow handles approvals. Any flow that needs approval calls this subflow — maintaining consistency and reducing maintenance. Updating the subflow once applies the change everywhere it is used.

Action (Custom Action)

Custom actions wrap reusable logic — often API calls or complex scripts — into a labeled step that non-developers can use. A developer builds a "Send Slack Message" action once. Any flow builder can then drag that action into their flow and configure it with a simple form, without understanding the underlying API code.

Data Pills: Passing Data Between Steps

Flow Designer uses data pills to pass information from one step to the next. A data pill represents a value from an earlier step — like the incident number created in Step 2 or the approval status from Step 1. When configuring Step 4's email, the builder drags the data pill for "Incident Number" into the email subject field. ServiceNow fills in the real value when the flow runs.

Data Pill Example:
Step 2 creates an incident → Incident record data pill generated
Step 4 email subject: "Your incident [incident.number] is ready"
                                         ↑
                        This data pill fills in INC0001234 at runtime

Flow Logic: If/Else and For Each

Flow Designer supports conditional logic and loops:

• If/Else: The flow takes different paths based on a condition. If Priority = Critical, send an alert. Otherwise, continue normally.
• For Each: The flow repeats a set of steps for every item in a list. If an approval request goes to five group members, the For Each loop sends a notification to each one individually.

Flow Testing and Activation

Flow Designer includes a built-in test mode. Administrators run a flow against a specific test record without affecting production data. The test run shows each step's execution, the data passed between steps, and whether each action succeeded. After testing passes, the administrator activates the flow — it runs automatically for all matching triggers from that moment forward.

Integration Hub Spokes

Flow Designer connects to Integration Hub, which provides pre-built action packs (called "spokes") for third-party services. Installing the Slack spoke adds ready-made actions for sending Slack messages. Installing the Jira spoke adds actions for creating and updating Jira issues. Spokes eliminate the need to build custom API integrations from scratch for common third-party tools.