# How to: Schedule a scenario to run at a future date **URL:** \ **Category:** Questions\ **Tags:** scheduling\ **Created:** [January 31, 2023, 1:28am UTC](https://community.make.com/t/how-to-schedule-a-scenario-to-run-at-a-future-date/7430 "2023-01-31T01:28:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![kai](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/kai/32/4556_2.png) [@kai](https://community.make.com/u/kai)\ **Post date:** [January 31, 2023, 1:28am UTC](https://community.make.com/t/how-to-schedule-a-scenario-to-run-at-a-future-date/7430/1 "2023-01-31T01:28:38Z")
Hey all, Reasonably comfortable with Make, but have an interesting use-case which is just stumping me! ### Context: - Client has a cohort-based course they run 6 times a year. It’s a 28-day course - They want to be able to run a scenario, grab the participants from ConvertKit, add them into a specific Slack channel (that’s all easy to do 👍) ### Question: They _also_ want to be able to set the date they should all get booted out (after 28 days). This is where I’m getting stuck. I presume a 28 day delay in the scenario isn’t best practice. I thought another approach could be to set up a ‘run’ to trigger on a specific date/time in future. Kinda like a [Scheduled workflow](https://manual.bubble.io/help-guides/the-bubble-api/scheduled-workflows) in Bubble (for those familiar). You may have multiple of these future scenario runs logged in a table, waiting to run on a specific date/time. It feels like there should be a good way to do this in Make. Any approaches welcome! ---
**Author:** ![DavidGurr\_Make](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/davidgurr_make/32/4624_2.png) [@DavidGurr\_Make](https://community.make.com/u/DavidGurr_Make)\ **Post date:** [January 31, 2023, 12:03pm UTC](https://community.make.com/t/how-to-schedule-a-scenario-to-run-at-a-future-date/7430/5 "2023-01-31T12:03:35Z")
You could use the [“On demand” scheduling option](https://www.make.com/en/help/scenarios/scheduling-a-scenario#on-demand-scheduling-935240) for a scenario, and then trigger that scenario to run using the [Make API “Execute Scenario” endpoint](https://www.make.com/en/api-documentation/scenarios-scenarioId-run-post) through the Make App’s “Make an API call” module. You’d then have another scenario that would run daily, checking the table in a Datastore to see what scenarios should be triggered that day. ---
**Author:** ![NolaDigital](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/noladigital/32/226_2.png) [@NolaDigital](https://community.make.com/u/NolaDigital)\ **Post date:** [January 31, 2023, 12:07pm UTC](https://community.make.com/t/how-to-schedule-a-scenario-to-run-at-a-future-date/7430/6 "2023-01-31T12:07:20Z")
You can definitely use [Cronhooks](https://cronhooks.io/) for this. Super useful for use cases like the one your having. Basically triggers a webhook to kickstart a scenario at a specified date. So when you add them to Slack, create a new cronhook to fire 28 days from now. Then have the removal scenario trigger by a webhook (submitted to Cronhooks). ---
**Author:** ![kai](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/kai/32/4556_2.png) [@kai](https://community.make.com/u/kai)\ **Post date:** [February 2, 2023, 12:30pm UTC](https://community.make.com/t/how-to-schedule-a-scenario-to-run-at-a-future-date/7430/7 "2023-02-02T12:30:12Z")
Thank you very much @DavidGurr_Make and @NolaDigital ! Both great solutions which would suit my job to be done here. For my use here, the free plan on Cronhooks would likely cover it, and sounds like it may be the more operation-light of the two. Thanks all ---
**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\ **Post date:** [September 7, 2023, 3:30pm UTC](https://community.make.com/t/how-to-schedule-a-scenario-to-run-at-a-future-date/7430/8 "2023-09-07T15:30:58Z")