A recurring event — a weekly webinar, a monthly office hours, a standing community call — has a genuinely repeating shape: same format, new date, every cycle. That repetition is exactly what makes it worth automating instead of designing a fresh reminder graphic each time.
The chain
Trigger — a daily timer, checking whether today falls within your reminder window for an upcoming event (a week out, three days out, the day of).
HTTP Request — pulling the next event's date, title, and description from a calendar API or a simple internal list you maintain.
Code node — computing days-until-event from the pulled date and today's date, feeding that number to the next step.
If node — branching on the computed days-remaining to select which reminder stage this run represents — "save the date," "this week," "starting soon" are different captions on the same event.
Apply Template — binding the event title, date, and stage-specific caption into your saved design.
Post — publishes the reminder automatically; see the exact Instagram node chain if this is your first build.
Why staged reminders, not one post per event
A single reminder posted once tends to reach whoever happens to be scrolling that exact day. Multiple staged reminders — a week out, a few days out, the morning of — reach different segments of your audience at different moments, which is the actual reason a countdown sequence outperforms a lone announcement, not just repetition for its own sake. The If node's job is making each stage feel like a distinct, appropriately-urgent post rather than the identical graphic reposted three times.
This is not the same as repurposing a past webinar
It's worth being explicit about the direction here: this automation promotes something upcoming, using the event's future date as the trigger for timing. Turning a completed webinar's recording into a batch of social posts afterward is a different workflow entirely — see repurposing a webinar into content for that direction. Both are legitimate, but they're solving different problems with different data sources.
Keeping the calendar accurate
The entire automation is only as good as the calendar or list feeding it — a stale entry means a countdown to an event that already happened, or worse, confidently reminding people about the wrong date. Treat the data source's accuracy as the actual maintenance burden here, not the workflow itself, and check drafted output on manual trigger whenever you add a new event before trusting the countdown to run unattended.