InServiceNow Flow Designer, aTriggeris used toinitiateaflow. Triggers define the conditions under which a flow starts and can be based on various system events, schedules, or user actions.
(A) A Trigger – Correct
Triggers are the starting point of a flowin Flow Designer.
A flow will not execute unless a trigger condition is met.
Types of triggers include:
Record-based triggers(e.g., when a record is created, updated, or deleted)
Scheduled triggers(e.g., run at a specific time or interval)
Application-specific triggers(e.g., Service Catalog request submission)
(B) Core Action – Incorrect
Core Actionsare predefined actions that execute tasks within a flow, such as:
Sending notifications
Updating records
Calling APIs
They aresteps within a flow,notwhat initiates it.
(C) A Spoke – Incorrect
A spokein Flow Designer is a collection of actions and subflows related to a specific application or integration (e.g., ServiceNow ITSM Spoke).
Spokescontain actionsbut donotinitiate flows.
(D) An Event – Incorrect
Eventsin ServiceNow trigger Business Rules, Notifications, and Script Actions, but they arenot directly used to initiate flowsin Flow Designer.
However, aflow can be triggered based on an event, but the event itself is not the trigger—the flow’s trigger is configured to listen for the event.
Explanation of Each Option:
Triggers should be well-definedto prevent unnecessary flow executions that might impact performance.
Use Scheduled Triggersfor time-based workflows (e.g., daily reports).
Record Triggersare commonly used for automation within ITSM processes.
Debugging Triggers: Use theFlow Execution Detailspage to troubleshoot trigger execution.
Additional Notes & Best Practices:
ServiceNow Docs: Flow Designer Triggers
https://docs.servicenow.com
ServiceNow Community: Best Practices for Flow Designer Triggers
https://community.servicenow.com
References from Certified System Administrator (CSA) Documentation:
