CONTENT DISTRIBUTION
Social Media Automation Engine
One engine that turns published site content into per platform posts for LinkedIn, Instagram and Facebook, and remembers what it has already sent.
- PROJECT
- Social Media Automation Engine
- INDUSTRY
- Content Distribution
- STACK
- n8n · WordPress REST API · Google Gemini · Facebook Graph API · Instagram API · Google Sheets
OVERVIEW
The project
Content was being published once and then distributed by hand, differently each time. Allzone built an engine that picks up published WordPress content which has not been shared yet, writes a version of it for each platform's own conventions, generates hashtags and image prompts, and marks the source so the same article is never posted twice.
CHALLENGE
What made it difficult
The same caption does not work on three platforms. Cross posting one block of text reads as automation on all of them, which costs more attention than it earns.
Distribution also needs a memory. With no record of what has been processed, a scheduled workflow republishes old articles every time it runs.
WHAT WE DID
The work delivered.
- 01
Content detection
Published content picked up automatically when it has not yet been processed for social distribution.
- 02
Per platform generation
Separate copy generated for LinkedIn, Instagram and Facebook against each platform's own requirements, alongside hashtags and image prompts.
- 03
More than one content type
Blog posts, trending topics and events all handled through this engine rather than through three separate workflows.
- 04
Publishing and tracking
Distribution through the platform APIs, with processed content marked so nothing goes out twice.
ARCHITECTURE
How it fits together
- One detection step feeding three generation paths, so platform rules live in generation rather than in three workflows
- The Facebook Graph API and the Instagram publishing flow each handled on their own terms
- A processed marker written back to the source, which is what prevents duplicates
- Publishing status tracked, so a failed post is visible rather than silent
TECHNOLOGY
The stack
- n8n
- WordPress REST API
- Google Gemini
- Facebook Graph API
- Instagram API
- Google Sheets
OUTCOME
What exists now.
Content published once reaches three platforms in a form suited to each, without a person rewriting it twice
The same article is never posted twice, because the engine records what it has handled
Trending topics and events run down the same path as blog posts instead of needing their own workflow
NEXT STEP
Tell us what you're building.
Bring us the problem with its real constraints attached. We will tell you what we would build, and what we would not.