Flow examples
Quick answer
Four small flows you can adapt: reminder, escalation, integration push and catalog fulfilment.
Key takeaways
- Re check conditions after a wait step
- Escalations should leave a work note explaining themselves
- Failed integration pushes need an alert, not a silent continue
- Keep fulfilment tasks in the flow, not in script
Reminder before breach
Trigger on incident updated, condition priority 1 and state not resolved. Wait for duration until 30 minutes before SLA breach, then send an email to the assignment group manager. Guard it with a check that the record is still open when the wait finishes.
Escalation on no acknowledgement
Trigger on created, wait for condition acknowledged is true with a timeout, and on timeout reassign to the on call escalation group and post a work note. The work note matters, because it explains to the next person what happened.
Push on close
Trigger on updated where state changes to closed. Use a REST action to notify the downstream system, and set error handling to stop with a failure that raises an event so a failed push is visible rather than silent.
Catalog fulfilment
Trigger on the request item, ask for approval from the requester manager, create catalog tasks for each fulfilment step, and close the item when all tasks are closed. Keep task creation in the flow so the process is visible to the process owner.
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What should follow a long wait step?
- A. An immediate email
- B. A re check of the condition
- C. A rollback
- D. A new trigger
Show answer
B. A re check of the condition
The record may have changed while the flow waited.
How should a failed outbound push behave?
- A. Continue silently
- B. Stop and raise a visible failure
- C. Retry forever
- D. Delete the record
Show answer
B. Stop and raise a visible failure
Silent failures cause data drift that is found much later.