Daily hero images from your Google Sheets social calendar

Every weekday at 6am, run this workflow to turn queued rows in a Google Sheets social calendar into finished hero images uploaded to Google Drive.

Read today's rows from the Social Calendar tab using Google Sheets Get Values. The tab has these columns: date, platform, caption, image prompt, aspect ratio, status, and image URL. Only process rows where the date column matches today and the status column equals "queued".

For each queued row, call Black Forest Labs Generate Image — FLUX 1.1 [pro] using the image prompt and aspect ratio exactly as they appear in the sheet. Do not rewrite, expand, or otherwise editorialize the prompt: the marketer authored it deliberately and this workflow must honor it verbatim.

Black Forest Labs delivery URLs expire ten minutes after generation, so immediately fetch the returned image bytes and call Google Drive Upload File (Multipart) to persist them in a shared Drive folder. Name each file with the date, platform, and a short slug from the caption so it is easy to find in Drive.

Once the Drive upload succeeds, call Google Sheets Update Values to write the resulting Drive URL into that row's Image URL cell and flip its status from "queued" to "ready". Batch the writes if possible, but never mark a row ready until its Drive URL is confirmed.

After processing the batch, call Slack Send a Message to post one summary in the marketing channel. Include the count of images produced, the count of rows skipped or failed, and a bulleted list of the Drive links (with platform and caption snippet) so the social manager can grab the images and schedule the posts.

This is a deterministic pipeline. No reasoning, no prompt editing, no branching on tone or brand voice. If Generate Image fails for a specific row, leave that row's status as "queued" so the next run retries it, and call out the failure explicitly in the Slack summary.

Reference shape: the n8n template "Transform images with AI prompts using FLUX Kontext, Google Sheets and Drive" follows the same read-generate-upload-write-back pattern, but this workflow is scheduled daily and uses the base FLUX 1.1 [pro] text-to-image endpoint instead of Kontext image editing.