Flow Designer

What it does

This skill, Flow Designer, enables AI agents to create and manage automated workflows within ServiceNow. It replaces legacy Workflows for new development in ServiceNow, allowing users to visually build processes using components like Flows, Subflows, Actions, and Spokes. The tool handles the underlying GraphQL mutations necessary for managing the full flow lifecycle programmatically.

When to use it

• Automating incident handling based on priority (e.g., creating major incidents for Priority 1 incidents).
• Scheduling recurring tasks, such as daily or weekly processes.
• Triggering workflows from Service Catalog requests (e.g., when a "Request New Laptop" catalog item is submitted).
• Implementing error handling within automated processes to log errors and send alerts.

Key capabilities

• Flow Creation & Management: Build and manage complete automation flows.
• Subflow Reusability: Create reusable flow logic for modularity.
• Action Definition: Define single operations like Script actions, REST API calls, etc.
• Spoke Integration: Organize related actions into collections (Spokes).
• Trigger Configuration: Configure triggers based on record creation/update events (e.g., incidents, change requests) and schedules.
• Variable Management: Define input, scratch, and output variables for data handling within flows.
• Conditional Logic: Implement IF/ELSEIF branching logic within workflows.

Example prompts

• "Create a ServiceNow flow triggered when an incident is created with Priority 1."
• "Build a subflow to notify the on-call team about a high-priority issue."
• "Generate a scheduled flow that runs daily at 2:00 AM in New York time."

Tips & gotchas

• IF/ELSEIF Placement: Actions within an IF branch must have parent_ui_id set to the IF's uiUniqueIdentifier. ELSE/ELSEIF blocks must be on the same level as the IF and cannot be nested. Incorrect placement leads to "Unsupported flowLogic type" errors.
• GraphQL Mutations: The skill handles GraphQL mutations, so direct manipulation of ServiceNow APIs is not required.
• Reusability: Leverage Subflows to promote code reuse and simplify complex workflows.