FlowsBook a callSign inCreate free accountSign up
AI employees and automation

How to set an AI employee to run only on weekdays

Untick the weekend in the Schedule block, pick the time zone and skip public holidays. How working-day timetables work, with examples for teams whose week starts on Sunday.

Part of the guide AI employees

By the xMap team · · 4 min read

To make an AI employee run only on weekdays, open its Schedule block, choose Every day (or Several times a day, or Every hour), and untick the days your team does not work, Saturday and Sunday for most teams. Set the time zone to where the team sits, and switch on skipping public holidays for your country, so the morning list does not arrive on a day nobody reads it. The panel shows the next three runs before you deploy, so you can check it at a glance.

This article is for anyone who has built an AI employee in xMap Flows and wants it to keep office hours. It covers the settings, timetables for different working weeks, an example, the mistakes people make and the other places in a flow where working days matter.

The settings that decide working days

Everything lives in the Schedule block at the start of the flow.

  • How often: Every day, Several times a day, Every hour, every 5, 15 or 30 minutes, Every week, Every month, Once, or Custom (cron).
  • Days: the days of the week it runs on. Untick the weekend to run on working days only.
  • Hours: for every 5, 15 or 30 minutes and Every hour, all day or only between two times.
  • Time zone: every time in the block is in this zone, so 07:00 means 07:00 where your team is.
  • Skip public holidays: a run due on a holiday of the country you pick is skipped, and the next one runs as usual. 51 countries are covered for 2026 to 2028, and you can list your own dates too.

Setting it up, step by step

  1. Open the flow and click the Schedule block.
  2. Pick Every day and set the time, for example 07:30.
  3. Untick the days you do not work.
  4. Pick the time zone of the people who will read the results.
  5. Switch on Skip public holidays and choose the country. Add any company closing days as dates.
  6. Read the next three runs shown under the settings. If Saturday appears, a day is still ticked.
  7. Deploy. The flow now runs on its own on working days only.

Working weeks that are not Monday to Friday

Not every team rests on Saturday and Sunday. The days are yours to tick, so set them to your own week.

Team (examples)Days to tickHolidays to skip
A sales team in TorontoMonday to FridayCanada
An operations team in DubaiMonday to FridayUnited Arab Emirates
A field team in Jakarta that works Saturday morningsMonday to Saturday, with a second flow for Saturday at 09:00 onlyIndonesia
A team in Cairo with a Sunday to Thursday weekSunday to ThursdayEgypt

Examples of how teams set their days. Check your own country's working week.

For an odd pattern, Custom (cron) takes five fields; 0 9 * * 1-5 is 09:00 Monday to Friday. Most people never need it.

An invented example

Say a dental supplier in Lyon has an AI employee that finds new dental clinics and emails a call list. It used to run every day at 07:00, so the Saturday and Sunday lists sat unread and Monday's list repeated some of them. The owner changes three things: days Monday to Friday, time zone Europe/Paris, and skip French public holidays. Now Monday's list holds everything new since Friday, because Only new remembers what earlier runs found, and on a bank holiday the list simply waits for the next working morning.

Other places where working days matter

  • Outreach sends messages only within working hours in the receiver's own time zone, 08:00 to 18:00 Monday to Friday, unless you choose any time. That protects a weekend even when the flow ran on Friday evening. See Outreach.
  • Wait can hold items until a time of day, so a list found late on Friday can be held until Monday morning. See Wait.
  • Approval stops a run until someone says yes. On a weekend nobody answers, so either avoid weekend runs or set what happens with no answer in time. See Approval.
  • The daily summary and notices follow each person's own settings. A flow that runs only on weekdays naturally sends fewer of them.

Mistakes to avoid

  • Leaving the time zone on UTC. A 07:00 run in UTC arrives in the early afternoon in Jakarta and the evening in Sydney. Set the team's zone.
  • Unticking the weekend but keeping a weekly run on Sunday. Every week uses its own day; change it too.
  • Expecting skipped runs to catch up. A skipped run does not run later. With Only new, the next run picks up what was missed, because it lets through everything not found before.
  • Forgetting holidays that move. Some religious holidays shift each year and are approximate in the list. Add your company's confirmed dates by hand.
  • Running a watch flow on weekdays only when the risk is daily. Road closures and weather alerts may need weekends too. Decide per employee.

What lands in the inbox

Once deployed, the inbox gets one result per working day at the time you set, nothing on rest days or holidays, and on the first working day after a break a list that covers everything new since the last run. Independent dental clinics to call, every weekday is a template set up this way, and Climate and environment news, every weekday does the same for news.

Questions

Can an AI employee run only Monday to Friday?

Yes. In the Schedule block, untick Saturday and Sunday. The next three runs shown in the panel confirm it.

Will it skip public holidays?

If you switch on Skip public holidays and pick the country. 51 countries are covered for 2026 to 2028, and you can add your own dates.

What if my team works Sunday to Thursday?

Tick Sunday to Thursday instead. The days are entirely yours to choose.

Does a skipped weekend mean missed results?

No, if the flow uses Only new. The first run after the weekend lets through everything it has not seen before.

Templates that do this

IndustriesB2B sales

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.