Triggers
The trigger defines when a contact enters a flow. Examples include contact created, checkout started, cart abandoned, product viewed, or an order placed.
Each trigger can include filters. These filters decide who is allowed to enter the flow.
Trigger filters also act as a suppression filter. If a contact no longer matches the trigger conditions, they will not enter the flow again, even if the triggering event happens. This prevents sending messages to contacts who no longer qualify.
Steps
Steps define what happens after a contact enters a flow.
Available steps include:
Wait: delay the next action by a set amount of time
Send post: send an email, SMS, or both
Send internal email: notify your team
Call webhook: send data to an external system
Filter: add additional conditions between steps
Posts in flows are created directly in the flow builder. Each send post step has its own filter, which is how conditional logic and branching are handled in Spoks.
Settings
Flow settings control the overall behavior of the flow.
Here you can:
Turn the flow on or off
Decide whether contacts can re-enroll or only enter once, or define a custom reentry period for when a contact is allowed to enroll again
Control when actions are allowed to execute, such as any time or only during specific hours
These settings apply to the entire flow and help you fine-tune delivery timing and frequency.
Together, triggers decide when a flow starts, steps define what happens, and settings control how the flow behaves over time.