{
  "$schema": "https://promptfoo.tech/schemas/workflow-template.json",
  "name": "Make.com: Turn One Blog Post into 12 Assets Automatically",
  "slug": "make-blog-to-multichannel-repurposing",
  "platform": "Make",
  "category": "content-creation",
  "difficulty": "Intermediate",
  "tags": [
    "make",
    "content",
    "marketing",
    "social",
    "openai"
  ],
  "summary": "A Make scenario that reads a new WordPress post and generates a LinkedIn carousel, X thread, YouTube script, email intro, and 6 social snippets — all in your voice.",
  "overview": "Most content teams write once and distribute badly. This Make scenario turns a single published blog post into a full multichannel package the moment it goes live, using a voice guide to keep tone consistent and a review queue so nothing ships without a human eye.",
  "variables": {
    "WEBHOOK_URL": "<your webhook URL>",
    "API_KEY": "<your provider API key>",
    "OPENAI_API_KEY": "sk-..."
  },
  "steps": [
    {
      "order": 1,
      "name": "Author the voice guide",
      "description": "One markdown file: forbidden phrases, sentence-length preferences, hook style, CTA rules. This is the highest-leverage artifact in the whole scenario."
    },
    {
      "order": 2,
      "name": "Set up the WordPress webhook",
      "description": "Use WP Webhooks or a lightweight custom hook on publish. Filter by tag so drafts don't fire."
    },
    {
      "order": 3,
      "name": "Build one branch first",
      "description": "Start with the LinkedIn post — highest ROI per output. Get quality right, then clone the branch for each format."
    },
    {
      "order": 4,
      "name": "Structure Notion as a queue",
      "description": "Columns: Channel, Draft, Status, Scheduled, Published URL. Status filters make review painless."
    },
    {
      "order": 5,
      "name": "Add scheduling downstream",
      "description": "Once approved, a second Make scenario pushes to Buffer, Typefully, or Beehiiv on the schedule your team already uses."
    },
    {
      "order": 6,
      "name": "Review the misses weekly",
      "description": "Any draft that never gets approved is signal. If LinkedIn drafts keep getting rejected, the LinkedIn prompt needs work — not the voice guide."
    }
  ],
  "howItWorks": [
    "Trigger: WordPress webhook fires when a post is published with tag 'repurpose'.",
    "A Router splits the flow into six parallel branches — one per output format.",
    "Each branch calls OpenAI with a format-specific system prompt and a shared voice guide.",
    "Outputs land in a Notion 'Distribution Queue' database with status = 'draft'.",
    "A Slack notification pings the content lead with a link to review."
  ],
  "benefits": [
    "One 90-minute writing session yields a week of distribution.",
    "Voice consistency across every channel because the guide is shared.",
    "Nothing ships without human approval — AI drafts, humans decide."
  ],
  "useCases": [
    "Solo creators repurposing long-form into shorts.",
    "B2B marketing teams with a weekly cornerstone post.",
    "Agencies producing distribution kits per client per week."
  ],
  "example": "Blog post title: 'Why we killed our roadmap'. LinkedIn draft opens with: 'We deleted our public roadmap last week. Support tickets dropped 30%. Here's what we replaced it with →'",
  "faqs": [
    {
      "q": "Can this fully automate publishing?",
      "a": "It can. Don't. One tone-deaf auto-post undoes a year of trust. Keep the human review step."
    },
    {
      "q": "How many formats before diminishing returns?",
      "a": "Six is the practical ceiling. More formats means more low-quality drafts nobody ships."
    },
    {
      "q": "Which OpenAI model?",
      "a": "GPT-4o for hooks and threads, GPT-4o-mini for snippets and email intros. Split saves ~70% on tokens."
    }
  ],
  "source": "https://promptfoo.tech/workflows/make-blog-to-multichannel-repurposing",
  "updated": "2026-05-20",
  "license": "CC-BY-4.0"
}