Looking for Fun & Unique Flow Designer ideas to practice building flows

[jyothave]

Hi Community,

I’m not working full‑time in ServiceNow yet, but I’ve started learning and I want to get hands‑on with Flow Designer. I’ve finished some flow learning path and micro‑certifications, but I’m still not fully confident applying them in real scenarios.

Could you recommend interesting or unique flow challenges that go beyond “create a task when an incident is opened”? I’m looking for ideas that are fun to build and help me practice good design patterns—like using actions, subflows, flow logic, error handling, and integrations.

I’d especially love:

• Multi‑table scenarios (e.g., incident → problem → change) that require branching, looping, or lookups
• Notifications that are context-aware and suppress spam
• ATF (Automated Test Framework) strategies to validate flows without breaking prod

If you have sample requirements, step-by-step outlines, or best practices (naming conventions, guards, retries, rollback strategies), please share!

Thanks in advance!

[Hemanth M1]

Hi @jyothave ,

I would recommend you create a sample catalog item or take an existing catalog item and build a back end flow for it:

1. Send notifications

2. Trigger approval for multiple users at once (parallel approval - do it in parallel). If one approves, it should still wait for the others for a specific duration (use Subflows here).

3. Take the number of catalog task counts from the intake form and create catalog tasks using do the following until (for loop).

4. Loop through each of these tasks using lookup records and use for each step.

5. Add an error handling block (ingest error example: send notification to invalid users) so the flow routes to the error handling block as needed.

6. Add a step to get the same number of requests submitted by the requestor – get this count using flow variables or using custom action here.

You can refer sample video as well - https://www.youtube.com/watch?v=-gtjZ62ewwA 

Hope this helps!