What is flow designer in Servicenow | Flow designer Basics

 

Flow Designer in ServiceNow

Flow Designer is a powerful tool in ServiceNow that enables users to automate processes, streamline workflows, and create logic-based actions without writing code. It provides a modern, visual interface that helps administrators design automation flows for both Service Catalog items and tables.

1. Understanding Flow Design

A Flow is a defined sequence of steps or activities that are executed automatically based on a specified trigger. It allows you to connect multiple systems, automate repetitive tasks, and enforce business logic with minimal effort.

Flows are primarily built for:

• Catalog Items – Automating catalog-related processes, such as approvals or task generation.
• Tables – Executing actions when records change or specific conditions are met.

2. Components of a Flow

Trigger

A trigger defines the event that starts the flow. It can be:

• Creation or update of a record
• Submission of a catalog item
• A scheduled time or external event (like a webhook)

Example: “When a new Service Catalog request is submitted, start the onboarding process.”

Actions

Actions are the building blocks of flows. They define what the system should do after the trigger fires. Common actions include:

• Creating or updating records
• Sending notifications
• Requesting approvals
• Running subflows

You can add actions from the “Add Action, Flow Logic, or Subflow” section in the designer.

Flow Logic

Flow logic helps you control process decisions. You can use conditions, loops, or branching logic (If/Else statements) to decide which path the flow follows.

Error Handler

The Error Handler allows you to manage errors gracefully. When something goes wrong, you can define alternative steps to handle or record the failure appropriately.

3. Data and Pills

Flows use data pills — reusable, drag-and-drop data elements that represent variables or field values. For example, you can drag “Requested Item Record” or “Manager Name” as data inputs in actions.

Example Pills include:

• Requested Item Record
• Run Start Time
• Assignment Group
• Approval State
• Catalog Details

These pills provide dynamic access to data relevant to your flow.

4. Creating a Flow

Steps to Create:

1. Go to Process Automation → Flow Designer.
2. Choose New → Flow.
3. Define the Trigger (e.g., “Service Catalog item requested”).
4. Add Actions such as:
   • “Get Catalog Variables”
   • “Create Catalog Task”
   • “Ask for Approval”
5. Configure inputs by connecting the appropriate data pills.
6. Add conditions using Flow Logic if needed.
7. Test and activate the Flow.

5. Example: Automating an Employee Onboarding Flow

Scenario: A new employee submits an onboarding form through the Service Catalog. The system automatically:

1. Retrieves catalog variables (employee name, email, start date, etc.).
2. Creates a catalog task for HR to process documentation.
3. Sends the request to the manager for approval.
4. Once approved, the flow updates the item status and logs approval history.

Configuration Overview:

• Trigger: Service Catalog → Onboarding Request
• Actions:
  • Get Catalog Variables (employee details)
  • Create Catalog Task (assign to HR)
  • Ask For Approval (manager review)
• Condition: If approval equals “Approved”, proceed to next step; else, end flow.

6. Key Benefits

• No-code automation for faster deployment.
• Improved visibility of process flow.
• Error handling ensures stable execution.
• Reusable subflows save development time.
• Integration ready for connecting with external systems.

7. Best Practices

• Name steps clearly to reflect their purpose.
• Reuse existing subflows instead of recreating logic.
• Use conditions to avoid unnecessary actions.
• Test thoroughly before activating in production.
• Document triggers and expected results for maintainability.