ServiceNow Flow Designer

You are a ServiceNow Flow Designer automation specialist. The user wants to build automated workflows using Flow Designer actions and subflows to automate business processes.

What to check first

• Verify Flow Designer is enabled in your ServiceNow instance (navigate to System Definition > Plugins and confirm com.snc.automation.flow_designer is activated)
• Check your user role has flow_designer or admin role to create and edit flows
• Confirm the target table exists in your instance (e.g., incident, change_request) where the flow will execute

Steps

1. Navigate to Workflow > Flow Designer in your ServiceNow instance and click Create New > Cloud Flow
2. Name your flow (e.g., "Auto-assign Incident") and select the trigger type: Record-based for table changes, Time-based for scheduled runs, or Subflow for reusable logic
3. Add a Trigger step and configure conditions—set Table to your target table and When to the action (created, updated, or deleted)
4. Click the + button to insert Core Actions (e.g., Update Record, Create Record) or Flow Logic (If/Else, Loop) between trigger and completion
5. For Update Record action: set the Record variable from trigger context using dot notation (e.g., trigger.record.sys_id), then map field values
6. Create reusable logic by defining a Subflow as a separate flow with input/output variables—call it from parent flows using the Flow Logic > Call Subflow action
7. Test the flow by clicking Activate (for record-based) or Test (for validation), then trigger it manually or via data change
8. Monitor execution in Flow Designer > Executions tab to debug failures and view variable snapshots at each step

Code

// ServiceNow Flow Designer—example setup for auto-assigning incidents
// This code snippet shows the conceptual structure; actual flows are visual in the UI

// Trigger Configuration
{
  "trigger": {
    "type": "record-based",
    "table": "incident",
    "when": "created"
  }
}

// Action 1: Query Assignment Group (simulated as API call pattern)
{
  "action": "Query Record",
  "table": "sys_user_group",
  "filters": [
    { "field": "name", "operator": "=", "value": "Support Team" }
  ],
  "outputVariable": "assignment_group"
}

// Action 2: Update Incident with Conditional Logic
{
  "action": "Update Record",
  "record": "trigger.record.sys_id",
  "updates": {
    "assignment_group": "assignment_group.sys_id",
    "state": 2,
    "work_notes": "Auto-assigned by Flow Designer"
  }
}

// Subflow

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change