← All templates

Content Marketing

Blog → Social Distribution

Writing the post is the work; distributing it is the tax. This workflow watches your RSS feed, reformats the post for each channel, schedules the posts through Buffer, notifies your team and logs the URL so you can measure what you actually published this quarter.

6 stepsRequires Zapier Starter or higher20 minEasy
BufferGoogle SheetsSlackRSS by ZapierFormatter by Zapier

What you get

Every published post reaches all your channels the same day.
Post copy is consistent instead of improvised at 11pm.
You keep a dated content log for reporting and repurposing.

Workflow blueprint

RS
When this happens
RSS by ZapierNew Item in Feed
1FO
Formatter by ZapierText — Truncate
2BU
BufferAdd to Queue
3BU
BufferAdd to Queue
4GS
Google SheetsCreate Spreadsheet Row
5SL
SlackSend Channel Message

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 3 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Buffer has no native n8n node, so that step arrives as an HTTP Request node with the endpoint left for you to fill in.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Detect the new post in your feed

Configure this step using the field mapping in the blueprint.

2
Trim the summary to social length

Configure this step using the field mapping in the blueprint.

3
Queue the LinkedIn post

Configure this step using the field mapping in the blueprint.

4
Queue the short-form post

Configure this step using the field mapping in the blueprint.

5
Log the post and notify the team

Configure this step using the field mapping in the blueprint.

Implementation notes

  • LinkedIn and X are Buffer profiles here, not Zapier connections. You connect Buffer once and it holds the channel logins, so adding a fourth channel later is a Buffer setting rather than another Zap step.
  • Queue rather than post immediately. A staggered queue outperforms five simultaneous posts on every channel.
  • Hootsuite, Later, Typefully and Publer all substitute for Buffer.
  • Add a Filter step on category if your feed contains posts you do not want distributed.