A scheduled content
and publishing pipeline.
A Python content pipeline connecting RSS, Claude, Buffer and SMTP with scheduled GitHub Actions runs.
The problem.
The brand needed a repeatable way to turn current headlines into content for X, Facebook, and email. Manual production made publishing dependent on daily availability.
The technical task was to connect ingestion, brand instructions, platform formatting, and distribution in one scheduled pipeline.
The system.
- IngestRSS headlines
- GenerateBrand instructions
- ScheduleBuffer API
- DistributeSocial + email
What I changed.
Connect source ingestion to generation
The Python pipeline ingested RSS headlines and passed source context and a detailed brand SOP to the Claude API for platform-specific drafts.
Schedule distribution
Buffer handled social scheduling and SMTP delivered long-form email content. GitHub Actions ran the pipeline on a regular schedule.
Control repetition
Content-pillar rotation and separate article/update days gave the pipeline a repeatable editorial structure.
The result.
A scheduled pipeline joins source collection, content preparation, and distribution. The implementation connects those stages in one scheduled workflow.
Let’s take
a look.
Tell me what you’re trying to do, which tools you use, and where you’re getting stuck.
Book a conversation adedoyin.bakared@gmail.com