Not every automation should run the instant something happens. Some things are better checked on a schedule, like a morning report, a daily backup, or a weekly cleanup of old files. When I started building scenarios in Make.com, I assumed every trigger had to be instant, a webhook firing the second a form was submitted. It took me a while to realize that a plain timer is often the calmer, cheaper, and more predictable choice.
This guide covers how scheduling actually works in Make.com: the two trigger styles you can choose between, how to lock in the right time of day, the timezone trap that catches almost everyone once, and why your polling interval quietly matters more than you think if you are on the free plan. If you are brand new to the platform, our guide to how Make.com works is a good place to start first.
How Do You Make a Make.com Scenario Run on a Timer?
Every scenario in Make starts with a trigger module, and that trigger has a scheduling section, usually shown as a small clock icon you click near the bottom of the module or in the scenario's settings panel. Click it and you get two broad choices: run at a regular interval, or run on a specific schedule.
Set your choice, save the scenario, and switch it on. From that point, Make checks the clock in the background and wakes the scenario up exactly when you told it to, whether that is every twenty minutes or every Tuesday at nine in the morning. You do not need to keep a browser tab open or a computer running. It lives entirely on Make's servers.
What Is the Difference Between Interval and Schedule Triggers?
An interval trigger repeats on a simple loop: every five minutes, every hour, every day, counted from whenever you turned the scenario on. It is the right choice when you mostly care about frequency and do not care exactly what time the clock reads, like a scenario that checks a shared inbox every fifteen minutes throughout the day.
A schedule trigger gives you precision: a specific time, specific days of the week, or specific dates of the month. This is what you want when timing itself is part of the point, like a report that needs to land in someone's inbox at eight in the morning before their day starts, or a scenario that should only run on weekdays and skip weekends entirely.
I use interval triggers for anything that just needs to stay reasonably current, and schedule triggers for anything tied to a person's routine, a deadline, or a business hour.
How Do I Run a Scenario at a Specific Time or Day?
Inside the schedule trigger settings, you pick a time of day and then choose which days apply, whether that is every day, weekdays only, or specific days you tick individually. Some setups also let you choose specific dates of the month, useful for anything tied to billing cycles or monthly reporting.
Keep it simple at first. A single time, a single set of days, and one scenario doing one job is much easier to debug than a scenario with several overlapping schedule rules. If you later need multiple run times, like a report at nine in the morning and another summary at five in the evening, it is usually cleaner to duplicate the scenario than to bolt extra logic onto one.
What Timezone Does Make.com Use, and Why Does It Trip People Up?
This is the mistake I made on my very first scheduled scenario. I set it to run at eight in the morning, checked it a week later, and the run history showed it firing at an hour that made no sense. The scenario was using a timezone that did not match where I actually live, and nothing in the interface screamed that fact at me.
Make.com scenarios pull their timezone from your account settings or, in some cases, a setting specific to that scenario, not automatically from your computer or browser. Before you trust a schedule to actually match your day, open the scenario's settings and confirm the timezone explicitly. It takes thirty seconds and saves you from a report that arrives at four in the morning instead of eight.
Why Does Your Polling Interval Matter on the Free Plan?
Here is the part beginners usually miss. A scheduled trigger does not just run when there is new data, it checks whether there is new data, and that check itself often counts as an operation, even when the answer is nothing changed. A scenario polling every single minute checks far more often across a day than one polling every fifteen minutes, even though both are doing the exact same job.
If you are on the free plan and watching your monthly operations closely, which our guide to Make.com operations covers in more depth, your polling interval is one of the biggest levers you control. Slowing down a check from every minute to every fifteen minutes rarely changes the real world outcome for most personal automations, but it changes your operations bill by a lot.
What's a Sensible Schedule for a Beginner Automation?
For most of the automations I run for myself, like syncing a spreadsheet, archiving old files, or checking a folder for new uploads, checking every fifteen to thirty minutes is plenty. Nothing in those workflows needs to react within seconds, and the slower interval keeps my operations usage comfortable.
I reserve tighter intervals for the rare cases where a delay actually causes a problem, like a scenario watching for a specific keyword in incoming support messages. Ask yourself honestly whether a fifteen minute delay would ever matter to the person on the other end. Most of the time, for a solo creator or a small side project, it will not.
Can You Combine a Timer with Other Triggers?
Yes, and it is one of the more useful patterns once you get comfortable. A scheduled scenario can remember what it already processed between runs, turning a simple timer into something closer to an event based automation, without needing a webhook at all.
You can also run a schedule trigger that itself calls other scenarios or checks multiple sources in sequence, which is handy for a morning routine that pulls from a few different apps and rolls the results into one summary.
What Happens If a Scheduled Run Finds Nothing to Do?
Nothing dramatic. The scenario runs, checks the source, finds no new data, and finishes quickly. Depending on your plan and module, that empty check may or may not use an operation, which is exactly why tightening the interval too far can waste your monthly allowance on runs that accomplish nothing. If you notice your operations dropping faster than expected, an overly aggressive schedule on a quiet data source is one of the first places to look.
Next step: Once your scenario runs on the schedule you want, the next skill worth learning is giving it memory so it does not repeat work on every run. Visit the automation hub for more Make.com guides that build on this one.
