‹ All interview questions

Core Concepts

What is Flow Designer in ServiceNow?

The question

What is Flow Designer in ServiceNow? How is it different from a Workflow, and when would you use each?

The Real Question

ServiceNow has two automation engines — the legacy Workflow Editor and the modern Flow Designer. Interviewers ask this to see if you know the platform's direction and can make the right choice for new projects.

Flow Designer (Modern — Recommended)

  • Low-code, drag-and-drop automation builder
  • Trigger: record created/updated, scheduled, inbound email, REST call, or custom
  • Actions: create/update records, send notifications, make REST calls, approvals, subflows
  • Supports error handling (try/catch), parallel execution, and loops
  • Can call Integration Hub spokes (pre-built connectors for Slack, Teams, Jira, etc.)
  • ServiceNow's strategic direction — all new features ship here first

Workflow Editor (Legacy — Still Supported)

  • Older drag-and-drop engine with a more visual canvas
  • Graphical state-machine approach — boxes and arrows
  • Well-established, millions of existing workflows in production
  • No longer receiving new features or significant investment
  • Still works, still supported, but new projects should use Flow Designer

A Simple Flow Example

// Flow: Auto-Escalate Unassigned P1 Incidents
//
// TRIGGER: Record Updated → incident table
//   Condition: Priority = 1 AND Assignment Group is empty
//              AND State = New AND Created > 15 minutes ago
//
// ACTION 1: Look Up Record
//   Table: sys_user_group
//   Condition: name = 'Critical Incident Team'
//
// ACTION 2: Update Record
//   Target: Trigger → Incident Record
//   Set Assignment Group = Step 1 result
//   Set Comments = 'Auto-escalated: P1 unassigned for 15+ min'
//
// ACTION 3: Send Notification
//   To: Critical Incident Team members
//   Subject: 'P1 Escalation: ' + Incident Number
//
// No code needed. All configured through the Flow Designer UI.

When to Use Each

  • New project? → Flow Designer. Always.
  • Maintaining existing workflow? → Keep it in Workflow Editor unless you have a reason to migrate.
  • Complex multi-system integration? → Flow Designer + Integration Hub spokes.
  • Need reusable automation? → Build a Subflow in Flow Designer — callable from other flows (like a function).
💡 Interview Tip

Never say 'I'd use the Workflow Editor for a new project.' That signals outdated knowledge. The safe answer: 'Flow Designer for anything new. Workflow Editor only if we're maintaining legacy automations that haven't been migrated yet.' If asked about Process Automation Designer (PAD), mention it's for complex multi-stage processes that orchestrate multiple flows — like an end-to-end employee onboarding journey.