Hi All, I have a functioning scenario working that watches for modifications to files within a shared drive in google drive (using the ‘Watch all files’ module), does some logic on them, and then either creates a new row in a Fibery database or updates an existing row.
It’s working great for one shared drive, but I’ve got multiple shared drives on google drive that I’d like to watch and feed into the same workflow, and I can’t figure out how to watch them within one scenario. I imagine I could do this by creating and maintaining a separate scenario for each shared drive, but I’d really rather not do it this way. There’s only a small handful of shared drives for now, but I expect these to grow and this solution will become unwieldy.
My intuition was to add multiple ‘Watch all files’ modules, which I did by copy/pasting, and aggregate their outputs to be fed into the rest of my scenario. But after trying and failing several different ways, I began to think that I was going about this the wrong way.
I read through this post Multiple Triggers Per Scenario, which indeed implies that what I want to do is not possible. Though there’s a workaround mentioned there (create a scenario-chain via a custom webhook), it seems silly to implement when all the inputs are coming from the same place (google drive), but just from separate shared drives.
I’m hoping I’m missing something basic, or that the clever folks here can help me get something working.
Thanks very much in advance, and please excuse any forum faux pas as this is my first post here!
Since the automation relies on Scheduled trigger, please note that you can only use one trigger per scenario.
Hence, you can only watch for one shared drive per scenario.
@Donald_Mitchell I’m accessing via a single google account that has access to multiple shared drives. I have selected Yes for Use Domain Admin Access to the workspace, so I can see all shared drives:
As mentioned there are only ~5 now, but I anticipate this number ~doubling. Based on both responses so far it seems I’m not missing anything obvious and that I’ll probably have to do the scenario chaining, which will land me with 10 individual complicated scenarios or one complicated scenario and 10 forwarding scenarios. This feels inefficient, but I suppose it may be necessary.
I imagine it backs into the limitation to watch only one shared drive at a time, which is either a google drive API limitation or a choice Make made re: how to map google drive API onto Make triggers (one drive at a time). Given that there are a whole suite of modules for managing multiple shared drives:
I thought there might be a facility for observing contents across multiple shared drives as well.
As it is, I’ll see if I can get the scenario chaining working or possibly just clone my scenarios for now. Thanks again!!
Incidentally (and please flag me off topic if this question belongs elsewhere), what’s the best place to register feature requests like ‘watch multiple shared drives at once’ or understand roadmaps for individual application integrations/modules? Is it this forum here? Does make.com participate here or is it mostly for users to discuss with each other?
I believe the modules are generally created by the vendors, in this case Google, but I could be wrong. Whatever Make can do is limited by the API and what Google allows via API.
I do believe your best bet right now is to create one Scenario that accepts as input the Google Drive file and where to find it, then process it according to your needs.
Then, you have ~5-10 separate Scenarios that all watch their own Drives and pass data on to your main Scenario.
Not that you’ll likely need it in this case, Make is also capable of creating Scenarios within itself, as long as you can provide JSON files to build them. You can export a blueprint of any Scenario, modify the JSON, then use Make to import it.
