Creator Content Repurposing

Track top LinkedIn creators in your space, convert their posts into original long-form blogs that match your brand voice, review them in Notion, and publish approved pieces to your site.

OutcomeBuilds a steady pipeline of SEO-optimized, brand-aligned content that attracts and converts qualified visitors without manual writing.

OperationalTime to value: 1 to 2 weeks4 tools

How it flows

How it flows.

Source
LinkedIn Creators
Process
Jungler Monitor
Store
Posts Database
Agent
Daily Rewrite Agent
Store
Blog Drafts Database
Process
Manual Review
Output
Approved
Output
Rejected
Process
Approval Webhook
Agent
Webflow Publish Agent
Channel
Webflow CMS
Drag to pan · scroll to zoom

    Build it, step by step

    Build it, step by step.

    1. 01

      Build your creator watch list

      Identify which LinkedIn creators are posting in your domain and collect their profile URLs. Focus on people whose topics and tone match your ICP.

      • List competitors and thought leaders who target your buyer persona
      • Capture each creator's LinkedIn profile URL
      • Prioritize creators whose style and topics align with your brand
      • Skip generic influencers; pick voices that speak to your vertical
    2. 02

      Configure Jungler to capture posts

      Feed your creator URLs into Jungler and route all new posts into a Notion database. Jungler polls LinkedIn profiles and writes each post as a row.

      • Add each LinkedIn profile URL to Jungler
      • Create a Jungler workflow that writes to Notion via integration
      • Map Jungler output fields to your Notion schema
      • Jungler runs continuously and appends new posts as they appear
    3. 03

      Set up the raw posts database in Notion

      Create a Notion database to hold every captured post. Each row is one post from one creator with metadata.

      • Creator Name (text)
      • LinkedIn Post URL (URL)
      • Post Content (long text)
      • Posted On (date)
      • Fetched On (date)
      • This database is the raw feed; no manual editing required
    4. 04

      Build the blog drafts database

      Create a second Notion database where Claude will write finished blog drafts. This database includes status fields for manual review and approval.

      • Blog Title (text)
      • Blog Body (long text)
      • Category (select)
      • Source LinkedIn URL (URL)
      • Status (select: In Review, Approved, Rejected)
      • Each row represents one candidate blog
    5. 05

      Schedule the daily rewrite job

      Set up a Claude agent task that runs daily, reads new posts, and generates long-form blogs in your brand voice. The agent writes output rows directly into the blog drafts database.

      • Create a scheduled agent task in Cowork (or your orchestrator)
      • Connect Notion MCP so Claude can read posts and write blogs
      • Prompt Claude to read rows where blog has not yet been created
      • Apply your brand voice guide and content guidelines
      • Rewrite each post as original long-form content, not a summary
      • Write output as new rows in the blog drafts database with Status set to In Review
    6. 06

      Review and triage drafts

      Each morning, open the blog drafts database and review new entries. Change Status to Approved or Rejected based on voice, accuracy, and originality.

      • Filter the database to show In Review rows
      • Read each blog for brand alignment and factual accuracy
      • Edit inline if needed (title, body, category)
      • Toggle Status to Approved for blogs that ship
      • Toggle Status to Rejected for blogs that do not meet quality bar
    7. 07

      Trigger publish automation on approval

      Configure a Notion automation that fires a webhook whenever a blog row moves to Approved status. The webhook payload includes all blog fields.

      • Create a Notion automation with trigger: Status changes to Approved
      • Action: call a webhook URL
      • Webhook payload: Blog Title, Blog Body, Category, Source LinkedIn URL
      • This automation runs instantly when you approve a blog
    8. 08

      Publish the blog to Webflow CMS

      Route the webhook to a Claude agent with Webflow MCP connected. Claude creates a new CMS item in Webflow and publishes it live.

      • Webhook hits a Claude agent endpoint with Notion MCP and Webflow MCP
      • Claude reads the approved blog fields from the payload
      • Claude creates a new Webflow CMS collection item with those fields
      • Claude publishes the item to the live site
      • Optional: tag the Notion row with Published timestamp

    The stack

    The stack.

    Talk to us: Want this workflow run for you?

    We wire it into your stack, then run it.

    Talk to Phi