What it is.
A cron runs daily at 9 AM, reads the topics scheduled for that day out of a Google Sheet, and generates a version of each per platform. Twitter gets something short, LinkedIn gets a longer professional post, Instagram gets visual framing.
DALL-E generates an accompanying image, then everything queues through Buffer. The calendar lives in a spreadsheet, so a marketer can plan a month without opening the workflow.
What you get.
- A daily read of a Google Sheets content calendar.
- Platform-specific versions of each topic instead of one post cross-posted.
- Generated images to accompany the posts.
- Scheduling through Buffer across Twitter, LinkedIn, and Instagram.
- A calendar anyone on the team can edit without touching automation.
How to set it up.
Build the Google Sheet calendar first, with a topic and a date per row.
Connect Buffer and confirm the channels you want, then delete the platform branches you do not use.
Rewrite the platform prompts in your own voice, since the defaults produce generic posts.
Turn image generation off if you have brand templates, because generated images rarely match a design system.
Set the 9 AM cron to run before your posting window, not during it.
Keep an approval step for the first month, and read everything before it queues.
Use cases
Calendar the team can edit
Keep the plan in a sheet and let the automation read from it daily.
One topic, several platforms
Get a version per platform instead of the same text everywhere.
Queue without opening the tool
Let it push to the scheduler so nobody logs in to paste posts.
Best for
A calendar that keeps slipping
Planning in a spreadsheet is easy. Writing three versions of every post is the work nobody gets to.
One person covering three platforms
The per-platform rewrite is the work, and this does the first draft of it.
Repurposing a content plan
If the blog calendar exists, the social calendar can be generated from the same rows.