Condition: business hours

Use the Business hours node so your workflows behave differently inside and outside your operating hours, and even on holidays.

Jun 26, 2026

Watch this step in the video · Business hours

What it is and when to use it

The Business hours node is a condition that checks the current time against the hours set in your workspace and branches the flow into three outputs: In hours, Out of hours and Holiday. Use it to reply instantly during the day and send a "we'll get back to you tomorrow" message at night, on weekends, or on public holidays.

It has no settings of its own: it uses the workspace business hours, so you define them once and every workflow respects them.

Requirements

  • Configure hours under Settings → Business hours (/workspace/business-hours): days, time ranges and time zone.
  • Workspace admin permissions to edit those hours.

Steps to set it up

  1. First define your hours in Settings → Business hours. Mark the active days, open and close times, and confirm the time zone (critical for a correct calculation).
  2. Open Workflows and enter your workflow editor.
  3. Drag the Business hours node from the palette (Condition category). It needs no internal config.
  4. Wire its three branches:
    • In hours → assign to an agent, open the conversation, reply instantly.
    • Out of hours → send the away message or create a follow-up task.
    • Holiday → a specific holiday message (optional; if you leave it unconnected, holidays fall through as Out of hours in older single-handle flows).
  5. Save and activate the workflow.

About holidays

The Holiday branch fires when today's date is in the workspace holiday list. That list is managed at the workspace settings level; if you don't define holidays, the branch simply never fires and the flow uses In hours / Out of hours.

Verification

Activate the workflow and trigger it during business hours: it should take In hours. To test Out of hours without waiting until night, temporarily set the workspace hours to a range that excludes the current time, trigger again and check the execution history for the branch taken. Remember to restore the real hours.

If it doesn't work

  • Always takes In hours: make sure you saved hours under Settings → Business hours and that the time zone is correct. With no hours defined, the node assumes you're always available.
  • Wrong branch for the time: it's almost always the time zone. Confirm it in workspace settings.
  • The Holiday branch never fires: no holidays are loaded in the workspace yet.

Tips

  • Wire Out of hours to an AI agent so it covers support 24/7 when your team is away.
  • Combine it with Agent belongs to team for different away messages per area.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp