Campaign Nodes
Time Window
Control when contacts can continue through a workflow based on allowed time windows.
The Time Window node checks whether the current time is inside an allowed window before the workflow continues.
When to use it
Use this node when timing matters for downstream actions.
Common examples:
- avoid sending messages outside business hours
- hold operational notifications until an allowed day
- align a campaign step with a workspace schedule
Settings
- Node name: optional display name shown on the workflow canvas.
- Window mode: how the allowed time window should be evaluated.
- Days and times: schedule settings for when the workflow may continue.
- Timezone: the timezone used to evaluate the window, when applicable.
Simulation and execution behavior
Simulations show the expected path. Real executions evaluate the configured schedule and continue when the window allows the next step to run.
Best practices
- Use Time Window for schedule constraints, not general waiting.
- Pair Time Window with Time Delay or Wait Until when both timing and behavior conditions matter.
- Make timezone expectations explicit when campaigns operate across regions.