ServiceNow Workflow Editor

The Workflow Editor is a visual drag-and-drop tool that lets administrators and developers automate multi-step business processes. Instead of writing complex scripts, users connect workflow activities on a canvas — like drawing a flowchart that ServiceNow actually executes. Workflows power approvals, notifications, task creation, and system updates across the platform.

What a Workflow Does

A workflow runs automatically when triggered by an event — a record being created, updated, or reaching a specific state. Once triggered, the workflow executes each activity in sequence, branching based on conditions, waiting for approvals, sending notifications, and updating records — all without human intervention.

Example: New Employee Onboarding Workflow
─────────────────────────────────────────────────────
Start (New RITM created for onboarding)
  │
  ├── Activity: Create Active Directory account
  │
  ├── Activity: Create email mailbox
  │
  ├── Activity: Request approval from IT Security
  │         │
  │         ├── Approved → Continue
  │         └── Rejected → Notify requester → End
  │
  ├── Activity: Provision laptop
  │
  ├── Activity: Notify employee "Your setup is ready"
  │
  └── End
─────────────────────────────────────────────────────

Accessing the Workflow Editor

Navigate to Workflow > Workflow Editor in the left navigation menu. The editor opens in a full-screen canvas view. Existing workflows appear as diagrams. Click any workflow to open and edit it. Click "New" to build a workflow from scratch.

The Workflow Canvas

The canvas is the visual workspace where workflow activities connect. Activities appear as colored boxes. Lines (called transitions) connect them, showing the flow of execution. The canvas supports zoom, pan, and alignment tools — making complex workflows readable at a glance.

Canvas Layout:
┌─────────────────────────────────────────────────────┐
│                   WORKFLOW CANVAS                   │
│                                                     │
│  [Begin] ──→ [Approval] ──→ [Notification] ──→ [End]│
│                   │                                 │
│                   └──→ [Rejection Path] ──→ [End]   │
│                                                     │
│  Left panel: Activity library (drag onto canvas)    │
└─────────────────────────────────────────────────────┘

Core Workflow Activities

Approval Action

Creates an approval record and pauses the workflow until an approver acts. The approval can go to a specific user, a group, or a manager determined dynamically from the record. The workflow branches based on the approval outcome — approved continues one path, rejected takes another.

Notification Activity

Sends an email or in-platform notification. The notification can target the record's caller, a specific group, or any user. Template variables populate dynamically from the record's data — so the email automatically includes the incident number, description, and assigned agent's name.

Set Field Values

Updates field values on the record. This activity changes the state, priority, assigned group, or any other field without writing script code. For example, after a manager approves a request, the Set Field Values activity changes the RITM state from "Pending Approval" to "Approved" automatically.

Wait for Condition

Pauses the workflow until a specific condition becomes true. A workflow waiting for an SLA to breach, a field to change, or a related record to close uses this activity. The workflow stays suspended — consuming no processing — until the condition triggers it to continue.

Create Task

Generates a new task record while the workflow runs. Onboarding workflows use this to create multiple catalog tasks — one for each team involved in setting up the new employee. Each task routes to the appropriate group independently.

Run Script

Executes custom JavaScript for logic that built-in activities cannot handle. Script activities give developers full control over complex decisions, calculations, or external API calls within the workflow.

Transitions and Conditions

Transitions are the lines connecting activities. Each transition can carry a condition — the transition only fires if the condition is true. After an approval activity, one transition fires on "Approved," another fires on "Rejected." The workflow follows only the path whose condition matches the outcome.

Workflow Versions and Publishing

ServiceNow keeps a version history of every workflow. Editing a workflow creates a draft version. Administrators publish the draft when ready — at which point the new version becomes active and all future workflow instances use it. Existing in-progress workflow instances continue on the version that started them, ensuring no disruption to ongoing work.

Workflow Editor vs. Flow Designer

ServiceNow provides two workflow tools. The Workflow Editor is the older, canvas-based tool. The Flow Designer (covered in the next topic) is the newer, step-based tool with a cleaner interface and more modern integration capabilities. ServiceNow recommends Flow Designer for new automations. Understanding both tools matters because many organizations still run workflows built years ago in the Workflow Editor.