Skip to content
App Wizard Academy

Access — inside the guide

The Drafter workflow.

Silver's content script, scheduled and looped across every site instead of run by hand, once, on one site.

Four steps

  1. 01

    Schedule the run

    n8n's cron trigger, once a day or once a week — your call. This is what turns Silver's one-script idea into something that runs without you starting it.

  2. 02

    Loop the site list

    Pull every row from site_config, not just one. Same Claude API call from Silver, run once per site instead of once total.

  3. 03

    Write to the drafts table

    Each generated draft lands in Supabase with status 'pending' — not committed to GitHub yet, not live. Just queued for review.

  4. 04

    Log the run

    A row in the runs table either way — success or failure. If a site's draft fails, the others still complete; one bad run doesn't stall the queue.

Free model, free cap-check logic

Uses a free OpenRouter model, so drafting nine sites’ worth of content costs nothing beyond your own time reviewing it. Download the workflow or build it from this guide.

Download drafter-all-sites.json

Drafts are queued. Next: what actually publishes them once they’re approved. The Publisher, multi-site.