I am having trouble understanding what I’m doing wrong here. I want my workflow to take a youtube transcript and turn it into 8 posts to be uploaded to twitter automatically at 8 different times over 2 days. Gummie had originally told me to build it this way after receiving several errors its telling me to restart and do it another way.
Hey @Justin_Reed! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.
Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}
Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
Provide details about the issue—more context helps us troubleshoot faster.
Hey @Justin_Reed – Could you elaborate a bit more on the exact issue you’re running into? Also, could you either set the workflow to “anyone with the link can view” or add my email under the share settings?
If you have any failed run links, sharing them from the history page would be super helpful.
In general, to schedule a flow, you can use the time trigger.
I’ve set the flow to be viewable. However I’ve found that the way I was trying to set it up would not work the way I wanted. I am now looking into the time triggers but I am concerned as I want it to run AFTER the flow has been started so that twitter posts are posted only after a youtube video is uploaded and not in a repeating schedule that may just repost the same tweets over and over again
For example here is the flow I want
Youtube video is uploaded
Gmail trigger recieves URL link and pulls the transcript
AI generated 8 tweets to be posted
Tweets are posts as follows (as long as that time has not already been passed, if so then ignore)
Same day at 9am, noon, 3pm and 7pm
Next day at 9am, noon, 3pm and 7pm
You can definitely do it using the time trigger and the subflow setup you’ve mapped out, but it’ll be a bit tricky. You’ll need an intermediary like Google Sheets to store the posts. So, whenever the Gmail-triggered Tweet Generator subflow runs, it can log the post along with the time and date into a spreadsheet. Then, the daily scheduled subflows can pick the relevant row from that sheet if it’s available.
A more dynamic option would be to create a custom Twitter poster node that schedules the post directly using the POST accounts/:account_id/scheduled_tweets endpoint. You can refer to Twitter’s API documentation here.