I want a scenario to run at two different times every day. The current platform only allows running the Scenario on one specific time, but I need two specific time each day. Thank you!
Welcome to the Make community!
Here are some options:
1. Easy
You can clone your scenario and set a different scheduled time.
2. Medium
You can set your scenario to run “On Demand”, and and two other scenarios to run your main scenario using the Run a Scenario module.
3. Hard
You can use the “Make an API call” module to set the next time you want to run the scenario
For examples on this, see
3 Likes
Could you please explain further Medium and show the steps neccesary?
Medium Option
Sure, there are two ways you can do this actually.
Option 1:
Use HTTP “Make a request” to call your main scenario’s Custom Webhook URL to trigger it
Option 2
Instead of HTTP module, use the Make “Run a Scenario” module to call your main scenario.
2 Likes
Update:
One more medium difficulty option is now available!
Option 3:
Use the Scenarios “Run a Scenario” module:
Subscenarios allow you to link multiple scenarios together to form a scenario chain. When the first scenario in the scenario chain finishes, it triggers the next scenario. This is useful in workflows with different stages or processes that need to run in a specific order.
You can migrate from using HTTP and custom webhook (Option 1), or Run a scenario modules (Option 2) to using the Scenarios > “Run a scenario” module.
According to the subscenario documentation, here is a comparison between the approaches with scenario chaining:
| Scenario chaining | Make app: Run a scenario | Trigger a webhook with the HTTP app | |
|---|---|---|---|
| Scenario triggering | Scenarios > Run a scenario | Make > Run a scenario | HTTP > Make a request - the follow-up scenario has to start with a webhook module |
| Setting next scenario | Select from a list of scenarios, categorized in folders. The scenario has to be in the same team. | Search scenarios available through the Make app connection. You can run scenarios in any organization or team to which you have access. | You have to know the webhook URL. You can trigger any webhook if you know its URL. |
| Sending data | Use the scenario inputs to accept data from the previous scenario. | Use the scenario inputs to accept data from the previous scenario. | Send the data in the HTTP request body or in the query parameters. |
| Scenario sequence management | - Each scenario in the chain has the relation tree overview. - In the scenario list, you can see which scenario is a parent, bridge or child in a chain. - In the scenario execution history, you can distinguish between scenario runs triggered by another scenario in the chain. - The bundles generated by the Run a scenario module contain a link to the execution log of the next scenario in the chain. | There are no dedicated management options. You can put sequence scenarios in a dedicated folder, use custom scenario properties, or create your own naming convention. | There are no dedicated management options. You can put sequence scenarios in a dedicated folder, use custom scenario properties, or create your own naming convention. |
| Scenarios running in parallel | You can trigger the next scenario in a chain before it finishes it’s current run. You can have multiple scenarios running in parallel. | You can have multiple scenarios running in parallel. | You can run webhook-triggered scenarios in parallel. |
For more information, see https://www.make.com/en/help/scenarios/subscenarios in the help centre.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.
1 Like