I’m a definite newbie and not really understanding all the capabilities of Make. I created a simple scenario but kept running into issues with modules needing intermediate values from a function and then also needing values from another module and it appeared that Make needs to be linear to pass data from one module to another without intermediate functions. Whether this is correct or not, does it make sense to use, like any other application, a datastore (google sheet, db (rest api), airtable) to store values and then build multiple specific use case scenarios that are then triggered by changes in that underlying datastore instead of a few complex scenarios? One of the challenges with the multiple scenarios is not having a hierarchy of scenarios is that the purpose of Grid? Thanks J
Hi @jlmc
You’re right—Make runs scenarios in a linear, step-by-step fashion, and it can get tricky when you need to reuse values across different parts of a complex flow. In those cases, breaking things into smaller, more focused scenarios and using a datastore like Google Sheets, Airtable, or Make’s built-in Data Stores as a shared data source is actually a solid approach. It helps reduce complexity and makes each scenario easier to maintain and debug.
As for the Grid, yes—it’s designed to help organize and visualize your scenarios better, especially when you start scaling. While it doesn’t give you a strict hierarchy or nesting of scenarios, it helps you group related ones so you can keep track of them more easily.
Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation
Thank you so much, this saved me a lot of time trying to make Make do something it was not designed for.
J