Twitter's API now supports setting a scheduled time. I'm not sure if this would mean fixing the existing twitter thing or creating a new twitter thing. This is a different api than the standard tweet post api and may require the user to have an ads account. For convenience it would be great to set minutes in the future to calculate the scheduled_at rather than dealing with date variables. I'd especially like to see a "send in a random time between X and Y minutes in the future".
My use case for this would be to direct an RSS to Twitter post. The RSS I am reading from tends to post 5 to 10 new things at once. This creates 5 to 10 new tweets all at once which is less effective for sharing news. If there was just 1 rss update per hour I could stash the rss values in variables, run a timer, read the variables, post the tweet, but with multiple RSS posts at once the variable gets written over before the end of the timer.
Alternatively, if I could pass variables to timer that would get passed on at the end of timer. I saw a need for this by some rachio users in the forum. They solved it by using global variables but they don't have events more frequently than their timers.
Another alternative would be to set variables that are specific to a single flow rather than global.