Unit 4 · Make Foundation: Routing and Filters

Overview of scheduling

3 min read Updated May 21, 2026

Text page

Welcome to unit four of the “Expanding my first scenario” course.

By this point you have completed your scenario - great job!

The following units will be focused on other elements that you need to know in Make.

Now you are going to explore options around running and scheduling your scenario.

Text page w/portrait image

Scheduling allows you to define the specific time and frequency at which you run your scenarios.

There are many options available here, and these will be based on the needs, type, and purpose of your scenario.

You can run your scenario:

  • At regular intervals - such as 15 / 30 / 45 minutes
  • Once - a one time execution on a specified date / time
  • Every day at a set time
  • Days of the week at a specific time
  • Days of the month at a specific time
  • Specified dates / time
  • Immediately when data arrives
  • On demand via the Run once button or an API call

Selectable image 2

It all depends on the type of scenario that you are running.

Polling

A polling trigger will execute the scenario at intervals. So if you are working with forms and want to collect and manipulate data at a regular interval, then running the scenario once per hour is ideal.

If you are running a scenario that cleans up files in Google Drive, then running this once a week is better suited.

Instant

An Instant trigger means that the scenario will be executed immediately as soon as data arrives, so you don’t need to worry about setting a time.

Text page w/portrait image

The key factor to remember is that every time your scenario runs, it will perform operations and consume credits towards your total credits count.

A quick breakdown of your credits count on your foundation use case:

  • The Weather app retrieves the current weather = 1 credit
  • The Google Sheets app adds a row = 1 credit

= 2 credits total

Therefore if you schedule the scenario to run every 15 minutes, this would total:

  • 8 credits per hour
  • 192 credits per day
  • 1,344 credits per week.

We will cover operations and credits in greater detail in the next course.

Scheduling your scenario is a straightforward process, let’s explore this now:

Before you decide to schedule

The most crucial thing with scheduling your scenario is ensuring that it is working properly. This means ensuring there are no errors when you select Run once, and that the data that you are working with is going where it needs to go. Once you are happy with your scenario, let’s schedule it.

Setting the interval

You can access scheduling in the bottom left-hand corner of the scenario builder. Clicking Scheduling will bring up the configuration pop-up.

By default At regular intervals is selected. In the dropdown here you can select your various options as previously mentioned. For your scenario, let’s select Every day, and then type 9:00. Click Save.

NOTE: this will consume 14 credits in a week.

Toggle ON / OFF

The last step to activate the scenario is in the bottom left-hand corner of the scenario builder. After you save your interval settings, click Activate Scenario in the pop-up window. Then save your scenario. You will know that your scenario is active when the ON/OFF toggle is purple.

Note: Scenarios can also be toggled ON / OFF from the scenario menu.

Text page

This concludes this unit on scheduling your scenario.

By now you should have an understanding of:

  • The difference between polling and instant trigger
  • The impact of scheduling in your operations and credits count
  • How to schedule your scenario

The next unit will explore the Run once function.