My goal is to have Scenario A watch events from monday.com (new item created on board in this case) and based on the filter, route to different branches and run scenario B and/or scenario C depending on results. This is what I have on scenario A:
My question is, what do I need to put at the beginning of scenario B and C to “catch” the request so it can run? At a minimum I at least need the ID from Scenario A. I tried watch events, but the Run Scenario option doesn’t have a webhook URL.
Hello @adinap.
I believe this “Run a scenario” module is relatively new. It will take some testing to figure out exactly how is passing the data and what can be passed.
An “old school” way of achieving this (if you don’t have time to experiment) is to use an HTTP request to POST whatever data you want in a JSON format in the body of the request.
On your B and C Scenarios you would set up a webhook to receive the data that is passed down from Scenario A.
Your setup would look something like this, with each HTTP module connected to the URL of the desired webhook:
I got it to work! Thanks for your guidance. Turns out there are 2 Run Scenario modules now. The new one I am using doesn’t require me to create a new API connection to Make, so that saves a step.
I didn’t understand at first that Scenario A pulls the scenario input variable name from Scenario B, then sends it back to Scenario B with the info filled in.
Hello,
Your topic caught my attention because I think I’m in the same situation. I did use the new module, which I place at the end of my workflow to send a notification to another scenario to start. However, it turns out that the next scenario triggers but picks up quite a bit of old data.
