Automation: some now, some later?

When a user registers for an event a data-stamped folder including the event name is created ("2024.12.31 - event name") in google drive at time of registration.   This is handled via apps script & automation functions.

Is there a way to prevent the folder from being created until the day of the event, even if months in the future?

Solved Solved
0 3 86
1 ACCEPTED SOLUTION

It is just the same bot. Use a branching condition based on the date of the event to either launch the task or add a row to the buffer table. This bot will be triggered by an addition of a new event. 

A separate bot will be run on a daily basis on the rows of the buffer table and launch the task on the events occurring on the same day.

 

View solution in original post

3 REPLIES 3

  • If the date of event is today --> launch the task to create/write in the folder
  • Otherwise, register the event in a table. A scheduled daily task would then check the table and launch the Apps Script task for the right rows on the right day. 

Ah... makes perfect sense now.   Thanks!

related question, thought I could create an action which invokes this bot, but haven't found a way to do that.  Seems there is a way, but a little convoluted.  The action makes some modification to the table, then a copy of the bot, would trigger to the table change and invoke the same script?   Haven't gotten it to work yet, but from what I've read that is 'a way' to do it.    Is there a better way perhaps?

It is just the same bot. Use a branching condition based on the date of the event to either launch the task or add a row to the buffer table. This bot will be triggered by an addition of a new event. 

A separate bot will be run on a daily basis on the rows of the buffer table and launch the task on the events occurring on the same day.

 

Top Labels in this Space