Illustration for: Chained AI: 3 Pipelines That Run Without You
← Real AI Stories
πŸ”§ Intermediate

Chained AI: 3 Pipelines That Run Without You

Meetings auto-filed in Notion. Video ads with no creator. 97 live ads from one directive. How people chain AI tools into hands-free workflows.

TL;DR

  • AI pipelines chain tools together so each step automatically feeds the next
  • Meeting pipeline: one recording β†’ organized Notion action items, zero manual steps
  • Video ad pipeline: one persona brief β†’ synthetic UGC video ads, no human creator needed
  • Ad rebuild pipeline: one directive β†’ 118 campaigns audited, 97 ads uploaded via API in 48 hours
  • Best for: Marketers, consultants, and business owners doing any repeating multi-step work
  • Key lesson: Single-tool AI is a calculator; chained AI is a factory

Three people built the same thing in three different industries: a sequence where AI tools hand work to each other, trigger to output, with no human in the middle.

Most people use AI the slow way β€” type a question, read the answer, type again. What these three built is different: a pipeline where a single event sets a chain in motion and the output arrives complete, without you touching anything in between.

The Meeting That Takes Notes for Itself

@ReadStacked had the problem every knowledge worker has: meetings generate insights that nobody captures. The notes people actually take are, as he puts it, β€œnotes I’ll never read.”

His solution is a five-tool sequence. A Plaud recorder captures the meeting. When it stops, Zapier detects the new file and fires the workflow. n8n processes the audio (transcription and formatting). Claude receives the transcript and extracts action items. Notion stores the structured output.

Meeting ends. Action items appear. He never touches it. β€œNow I just show up and actually think during meetings instead of scribbling notes.”

The output isn’t just a transcript β€” it’s organized, actionable, and consistent across every meeting. No human note-taker delivers that reliability.

The Video Ad Without a Creator

Usman Qamar (@thesuqb) needed UGC-style video ads but didn’t want the overhead of hiring creators β€” scheduling, revisions, usage rights. His pipeline generates them synthetically in four steps.

Step one: describe a persona in Claude (age, style, energy, background β€” be specific). Step two: feed that description into Nano Banana 2, which generates a photorealistic model image. This is your creator, built from scratch. Step three: paste the image back into Claude and ask for three things β€” a JSON prompt for Kling 2.6, a text version of the same prompt, and image reference guidelines for maximum realism. Step four: run the prompts in Kling 2.6 via the Kie API.

What comes out looks phone-filmed: natural lighting, natural movement. The image reference guidelines are the secret, Usman says β€” β€œthat’s why their AI videos look like AI videos. Claude structures them in a way Kling actually uses properly.”

One brief. Four tools. No casting, no scheduling, no revision rounds.

The Ad Account That Rebuilt Itself

Timothy Lewis (@tolewis) gave a custom AI agent named Katya a single directive: rebuild this neglected Meta ad account. She had 48 hours.

Katya audited 118 old campaigns with $131K in lifetime spend β€” archiving what was worth keeping, flagging the rest for deletion, and reviving the two best-performing historical copy variants. Then she generated 30 static and 10 video ads using StrikeFrame, a custom image renderer Timothy built that composites product photos, SVG overlays, and ad copy from a JSON config. A chunked upload pipeline handled 200MB video files. Everything hit Meta via the Marketing API automatically.

Before: 45 scattered ads. After: 97 thesis-driven ads across 7 clean campaigns. Zero agencies, zero Canva, zero freelancers.

β€œThis is what AI agents actually look like when you point them at real business problems.”

The Pattern

All three pipelines share one thing: a single trigger replaces a multi-person workflow. A meeting ends. A persona brief is written. A strategy doc is submitted. The pipeline takes it from there.

The difference between chatting with AI and building a pipeline is the difference between asking someone to help you cook dinner and running a kitchen that operates without you.

The tools already exist. The only design decision is what hands what to whom β€” and where you stop being the one who has to be there.

FAQ

What is an AI pipeline?

A chain of AI tools where each handles one step and passes output to the next β€” like an assembly line for knowledge work. The final result would normally require multiple people or hours of manual effort.

Do you need to code to build these AI pipelines?

The meeting notes pipeline uses no-code tools (Plaud, Zapier, n8n, Claude, Notion) β€” no coding required. The UGC video pipeline is pure prompting. The Meta ads pipeline involved custom code (StrikeFrame renderer, Marketing API). Ranges from zero to advanced.

What tools are involved across these pipelines?

Meeting pipeline: Plaud, Zapier, n8n, Claude, Notion. Video ad pipeline: Claude, Nano Banana 2, Kling 2.6 via Kie API. Ad rebuild: custom AI agent, StrikeFrame renderer, Meta Marketing API.

How is a pipeline different from chatting with AI?

Chatting requires you to type and respond at every step. A pipeline runs automatically from a single trigger to a final output β€” meeting ends, Notion updates. Brief submitted, video rendered. You're not in the loop at all.