How to Use Flow Designer in ServiceNow (with a Real Use Case)

 Flow Designer is ServiceNow’s low-code automation engine that lets you organize -step processes without writing complicated workflows. Of using the old Workflow Editor you create flows by using triggers, actions and logic blocks on a visual screen. This makes it easier for admins and developers to automate approvals, notifications and integrations.

Why Flow Designer is important

Flow Designer is at the center of servicenow online training setups because it:

Helps with low-code and no-code automation for admins and business users.

Works closely with Service Catalog, Incident, Change and custom apps.

Allows using subflows handling errors and running tasks at the time for better automation.

For companies using ITSM, HRSD or CSM Flow Designer is the way to automate request handling, approvals and rules.

Example: Access request rules

An example is automating requests for VPN access with the right reasons checking and getting approval. In this case:

A user asks for a Service Catalog item for VPN access.

The flow looks to see if a business reason is given.

If there is no reason a security check task is made.

If there is a reason the request goes through an approval process.

When approved a task to fulfill the request is created. When rejected a task to record the rejection is created.

This makes sure access is not given without a reason check and a clear list of what happened.

How to build the flow

Find the starting point and the approval steps

Show the order: Requester → Security Check (if needed) → Approver(s) → Fulfillment.

Create flow

Go to Flow Designer -> New -> Flow and choose the trigger type "Catalog Item Requested."

Catalog information

I suggest you use the Get Catalog Variables action to grab fields like business_justification from the request. This step is very important. If you do not use Get Catalog Variables the flow might think the variables are empty when someone filled in the business_justification on the portal.

Add decision logic

Use an If/ block:

If business_justification is empty → Create a Security Review Catalog Task.

If business_justification is not empty → Go to Ask for Approval.

Set up approval

Add the "Ask for Approval" action. Make sure you set "Wait for approval" to Yes. Then you can name the people who can approve such as a manager or a security lead.

Deal with results

If the request is approved: Create a Fulfillment Catalog Task.

If the request is rejected or not needed: Create a Rejection Documentation Task.

Add error handling

Put your steps inside a Try block. It is an idea to set up messages, for when things go wrong or when there is a delay.

Test and turn on

Test in a test environment with different situations: full approval process, rejection at each step and delays. When it works turn the flow on. Check the logs for the first live runs.

Tips for using Flow Designer

Use Flow Stages to show steps (like "Waiting for Approval " "Fulfillment”) in the Request Summary widget.

Turn on the system property com.glide.hub.flow_engine.stage_display.show_approvers = true to show the names of people waiting to approve in the stage details.

Use Subflows to reuse steps like approvals, messages or task creation.

By learning Flow Designer with examples, like access control you can quickly provide useful automation and become a strong ServiceNow expert.