IndexPine docs
Docs
Features
Social Repurposer

📣 Omnichannel Social Repurposer

Turn every published article into a week of social content — Twitter/X threads, LinkedIn posts, email snippets — automatically.

Publishing an article without distributing it is table stakes — every serious content operation already does it. The Omnichannel Social Repurposer turns each article into a complete set of platform-native social content, ready to schedule or publish immediately, saving hours of manual reformatting per article.

What is generated per article

When an article is published, IndexPine generates the following social assets in parallel:

  • Twitter/X thread — a 5–8 tweet thread that summarises the article's key points. Each tweet is standalone-readable. The thread ends with a link to the full article.
  • LinkedIn post — a 200–400 word LinkedIn-native post formatted with the platform's characteristic line-break style and emoji usage. Hooks with a strong opening line, delivers value, closes with a link.
  • Email newsletter snippet — a 100–150 word digest paragraph suitable for a "what we published this week" section in any email platform.
  • Short-form quote cards — three pull-quotes extracted from the article, formatted as text overlays suitable for Instagram or LinkedIn carousels.

Connecting distribution channels

Social assets are delivered via webhook in the same JSON payload as the article. The payload includes a socialAssets field:

json
{
  "event": "article.published",
  "article": { ... },
  "socialAssets": {
    "twitterThread": [
      "Tweet 1 text here — standalone point",
      "Tweet 2 text here — next point",
      "...5-8 tweets total...",
      "Full article: https://myblog.com/your-article-slug"
    ],
    "linkedInPost": "Opening hook line...\n\nBody of the post...\n\nLink: ...",
    "emailSnippet": "This week we published...",
    "quoteCards": [
      "Pull quote 1",
      "Pull quote 2",
      "Pull quote 3"
    ]
  }
}

Automating distribution with Make or Zapier

Connect the IndexPine webhook to Make or Zapier, then route the social assets to your scheduling tools:

  • Route twitterThread to the Twitter/X API or a Buffer Twitter queue.
  • Route linkedInPost to the LinkedIn API or a Buffer LinkedIn queue.
  • Route emailSnippet to a Mailchimp/Beehiiv digest template.
  • Route quoteCards to a Canva template automation or Airtable for a designer to style.
Review before publishing socially
Social content is more personal and brand-sensitive than blog content. We recommend reviewing the generated social assets before they go live, especially for the first few articles until you have calibrated the voice settings to match your social presence.
Previous🗺️ Topical Authority MapNext 🤖 GEO Optimizer