It should be obvious but I can’t find a simple way to do this : how can I launch a scenario when another one ends ?
Or, in other words : is there a simple way to detect that a scenario has ended ? And then launch another one.
Here is my use-case :
I have an Airtable “Watch records” module that sends data to a Webflow module to either create or update pages.
After it is done, I would like to launch another scenario, that also starts with an Airtable “watch records” module.
My problem is that the Airtable Watch Records Module does not seem to give me a “total number of bundles” or a “bundle order position” (unlike the Airtable Search module…).
So I don’t know how to launch the Make “Run a scenario” module ONLY when the scenario is finished.
I can’t change the Airtable “Watch Records” module to a Search Records because I need to get records that have been updated (and the Search module can’t do that).
My solution would be to add an array aggregator followed by an iterator just after the 1st module (Watch Records), like this :
But it seems to be an overly complex solution for a very simple problem.
And it does not work if there is an error on the last bundle.
Isn’t there a way to launch a module ONLY when everything else is finished ?
Or isn’t there a Make module that can be triggered when another scenario ends ?
Add an HTTP Request to the End of the First Scenario:
Change the HTTP method to POST and enter the webhook URL of the second scenario.
In the request body, you may also pass relevant information from the first situation.
I have done that in other cases but I am not sure that solves the problem here : how do you make sure the HTTP module launches ONLY when the first scenario is finished ? And not for every bundle ?
(And second problem : if I use a Webhook module at the beginning of the second scenario, then I can’t use the Airtable Watch Records module that allows me to get all newly modified records)
I am surprised that Make does not have a simple module that would wait until a scenario is finished and then launch another one.
Or the other way around : have a module at the beginning of a scenario that would trigger only when another scenario ends (without having to use the HTTP and Webhooks workaround)
Aggregate whatever Airtable Watch Records finds into an array.
Iterate on that array and that will automatically include bundle order position and total number of bundles in each bundle.
On your router, add a new router for your Run a Scenario module and a filter for where Bundle Order Position = Total number of bundles
Your first two routes should run according to their filters but the last route should only run after the last bundle. Just ensure the last route is indeed last route, in this case 3rd.
Your second scenario may remain with the Airtable Watch Records trigger module.
