Easy way to understand flows in Flow Designer?

[justincross]

I was just curious if there was an easy way to understand what is needed for flows or do you have to just play with the flow designer to get used to it.

For Example:

In the ServiceNow Administration Fundamentals/CSA Capstone Project, you have to create a flow for a Catalog Request.  You need to have it be approved by a manager, then if approved to add 3 Catalog Tasks.  If Rejected to send an email.

I was able to add the trigger (easy) and got the fist Action for the approver (even though I messed up on the pill dot-walking and did not add the manager properly).  I was able to add the flow (If statement) but missed the step to "wait for condition."  Also I didn't realize there was a "End Flow" option. 

[Community Alums]

hi @justincross ,

otally normal — Flow Designer can feel tricky at first, but it gets easier once you know the patterns.

For your example (catalog item → approval → tasks/email):
✅ Add the trigger → “Catalog Request Created.”
✅ Add Ask for Approval (use dot-walking to get the requested for’s manager).
✅ Then add Wait for Condition → wait until approval state changes to Approved or Rejected.
✅ Use an If branch:

• If Approved → create your 3 Catalog Tasks.

• Else → send rejection email.
  ✅ Finally, add End Flow to finish cleanly.

Tip (best practice): always use “Wait for Condition” after approval actions to pause the flow until there’s a response — otherwise, the flow keeps running.

Playing around definitely helps, but reading ServiceNow docs and sample flows will save you a lot of time too. 👍