I would love a Delay or Pause module, similar to what Zapier does natively.
I have a system that uploads a Google Meet link to a user at, for instance 10pm, but then at 10:50pm it must delete the link.
I’ve seen the workarounds such as create a drip campaign etc. but it doesn’t work for my needs.
All of these seem to require watching a data store for a specific timestamp, but of course then I need to create a scenario that polls that data store every 5 minutes.
I would love the possibility to just input an x minute pause in between modules, and to be honest it’s the only thing keeping me from switching over from Zapier completely.
Interesting idea, I could just set up specific webhooks to fire at those timed intervals.
Thanks for the suggestion, it’s a great one.
Would still prefer to not have to use a workaround like this though - I understand there may be runtime limitations for each scenario, but if Zapier can do it I’m sure Make can as well
Yeah frustrating but at least it is a workaround. Imo it makes up for Zapier’s downsides and the money spent on Cronhooks + Make is much lower than Zapier haha
Right, agreed. This is my first month using Make after a decade with Zapier, and already I’m finding some significant improvements (not to mention the cost).
Would going off an Airtable trigger be good for you. You can sort of log through Airtable and do it that way. Watch this video and see if it would be worth it for you to implement this stuff over into Make?
Hey @AnthonyatXRay thanks for the info and video - it’s certainly possible with Airtable or by using something like Google Sheets as a data store that’s polled every 15 m, but I’d like to avoid these kinds of workarounds as my clients expect simplicity with the automations I create for them.
It seems like a waste of operations to have to run multiple sleep modules. I wonder if anyone at Make can explain why sleep is limited to 300 seconds?
I haven’t really looked into the Make API but I think there’s a way to turn on a module, and to set it’s automatic start time? You could put everything after your sleep into it’s own separate scenario, Then you’d just have to set it’s start time and turn it on? Can scenarios turn themselves off with the API?
Still a lot of work when we already have the sleep module that could sleep longer.
I would also love to have a “Sleep Until” module that either starts a watch module, or has a loop that you can add a Sleep + whatever check you need to do.
This approach using the datastore as a queue to manage is very clever. I wonder how it will operate at scale in terms of operations used since you may have quite a bit of queued records to manage and if you get a large amount of records in a 15 minute time span you may have an issue with processing all those records at once. I guess you could check more often as well if you want to process smaller pieces of data.
Agreed @alex.newpath - the issue I have with it is that it’s an inelegant solution - I may have 20 entries at the same timestamp that would need to be processed, so while it may work for one bundle at a time, it doesn’t work for my use case. I’d need to prepend each timestamp with a unique identifier to make sure the correct ones are processed by subsequent steps, and it would be a huge headache.
Again, it’d be so much simpler if, y’know, I could just define the sleep module as X minutes, but perhaps that’ll come in a future update.