Condition: Date / time

Use the Date / time condition node to branch a workflow by weekday, exact date, or time window — perfect for holidays, promotions, and one-off windows.

Jun 26, 2026

Watch this step in the video · Date and time

What it is and when to use it

The Date / time condition is a condition node that branches your workflow based on the calendar: weekday, a specific date, a date range, day of the month, month, or an hour window. It's the right tool for one-off windows that don't fit the recurring weekly pattern of the Business hours node — holidays, vacations, promo dates, or end-of-month cutoffs.

Unlike Business hours, which answers "open / closed / holiday" from your weekly schedule, Date / time evaluates a single rule and returns two outputs: Yes (true) and No (false).

Evaluation uses the conversation's workspace timezone, not the server's. Double-check the timezone in your workspace settings before scheduling critical dates.

Requirements

  • Available on all plans (from Lite), with a monthly quota of workflow runs based on your plan.
  • A workflow with a trigger already in place.

Steps

  1. Go to Settings → Workflows and open the workflow you want to edit (or create a new one).
  2. In the left panel, open the Nodes tab and expand the Conditions section.
  3. Drag the Date / time card onto the canvas and connect it after the previous node.
  4. Click the node to open the inspector on the right and pick an operator:
    • Date equals — an exact date (YYYY-MM-DD).
    • Date before / Date after — before or after a date.
    • Date between — a range (from / to).
    • Day of week is one of — tick Mon, Tue, Wed…
    • Day of month is one of — e.g. 1, 15, 28.
    • Month is one of — January…December.
    • Hour between — an HH:MM–HH:MM window (handles ranges that cross midnight, e.g. 22:00–06:00).
  5. Fill in the values for the operator you chose.
  6. Wire the Yes output to the branch that runs when the rule matches, and the No output to the rest of the flow.
  7. Click Save.

Verify

Use the editor's Test button to run a test execution, then check the execution timeline to see which branch the node took. The trace panel also shows the evaluated operator and the result.

If it doesn't work

  • Always takes the No branch: make sure the date format is YYYY-MM-DD and the workspace timezone is correct. An invalid setup falls to the No branch on purpose — the safe default so a promo never fires when it shouldn't.
  • Hour window doesn't match: remember the hour is evaluated in the workspace timezone, not your local time.
  • Crossing midnight: for an overnight window use 22:00–06:00; the node reads it as a range that spans two days.

Tips

  • Combine Date / time with Business hours to cover both the recurring weekly schedule and one-off exceptions (holidays).
  • For campaigns, run the Yes branch into a Send message node with the promo content and leave the No branch empty so you don't message customers off-window.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp