An AI Social Media Campaign Engine with Human-in-the-Loop Approval

The brief: a full social campaign from one form, with a human holding the publish button.

The client wanted to turn a single brand intake into a complete, ready-to-schedule social media campaign across LinkedIn and Facebook — original copy and visuals for every post — while keeping a person firmly in control of what actually goes live. The two requirements were in tension: the speed and volume of full automation, paired with the editorial safety of human review. We resolved that tension with a 63-node n8n workflow built around an AI content strategist and a per-image human-approval loop.

Stage 1 — Brand intake. Everything starts from a simple form capturing the inputs that make content on-brand rather than generic: brand name, industry, target demographics and location, primary value proposition, the customer challenge, desired outcome, brand voice, specific topics to focus on, and the company website. These variables become the creative brief for the rest of the pipeline.

Stage 2 — Strategic content generation. A research-augmented AI agent (running GPT-5-mini via OpenRouter, with a Perplexity web-search tool and an explicit "think" step for planning) acts as the campaign strategist. Rather than spitting out captions, it first reasons about the right approach — selecting a proven copy framework such as PAS (Problem-Agitate-Solution), StoryBrand, or BAB (Before-After-Bridge) — and pulls current market or local context via web search when fresh data would strengthen the message. It then produces a batch of platform-specific posts: a professional, thought-leadership tone for LinkedIn and a warmer, community-driven tone for Facebook. Each post arrives as structured JSON containing the copy, emojis and hashtags, a distinct visual style (photography, infographic, 3D scene, or illustration), strategic overlay text, and a suggested posting date.

Stage 3 — Image generation. For each post, the matching image prompt is sent to Google Imagen 4 (hosted on Replicate) to generate an on-brief visual. Posts are processed one at a time through a batching loop so each image can be handled — and reviewed — individually.

Stage 4 — Human-in-the-loop approval. This is the heart of the system. Every generated image is sent to a reviewer in Slack using a send-and-wait-for-response step that pauses the workflow. The reviewer either approves the image — and the pipeline moves on to the next post — or rejects it with written feedback. On rejection, that feedback is fed to NanoBanana (an image-editing model, also on Replicate), which revises the image accordingly, and the new version is sent straight back to Slack for another round. The loop continues until a human signs off, so nothing proceeds on a visual the reviewer hasn't explicitly accepted.

Stage 5 — Storage and record-keeping. Once approved, an image-path switch resolves whether to use the original or the edited version, the final asset is uploaded to Google Drive, and the post's details are appended to a Google Sheets record — giving the team a clean, auditable log of every campaign asset and its metadata.

Stage 6 — Multi-platform scheduling. A platform switch routes each post to the correct destination, and the finished, approved content is scheduled through the Late API (getlate.dev) — to LinkedIn for the professional posts and to Facebook/Instagram for the social ones — using the brand's connected account IDs and the posting dates assigned earlier.

Why this design works. It captures the economics of automation without surrendering editorial control. The AI handles the heavy lifting — strategy, research, copywriting across two distinct platform voices, and four visual styles — while the Slack approval gate guarantees a human signs off on every single image before it's stored or scheduled. The rejection-and-revise loop means feedback doesn't bounce work back to square one; it refines the existing asset in place. Google Sheets provides the audit trail, Google Drive the asset library, and the whole orchestration runs on self-hosted infrastructure, keeping brand inputs and credentials under the owner's control.