Content Publishing Automation Pipeline

Development of an internal automation pipeline for publishing scheduled content from Coda to social platforms through ZennoPoster.

Content managers plan publications in a Coda table. A Python service retrieves ready posts through the Coda API, generates structured JSON tasks, and places them into a file-based queue. ZennoPoster executes browser automation and publishes the content. The result is then processed by Python, archived, and synchronized back to the original Coda row.

I independently designed the architecture and implemented the Python orchestrator, Coda API integration, file queue, provider workflows, and result processing.

Core functionality:

- retrieving scheduled posts from Coda;
- generating structured JSON tasks;
- file-based in, out, dead, and archive queues;
- browser-based publishing through ZennoPoster;
- provider-specific workflows for Medium and Facebook Groups;
- status synchronization with the source table;
- Scheduled, In Progress, Done, and Error states;
- process locking to prevent duplicate execution;
- scheduled hourly runs;
- retry and error-handling logic;
- dead-letter queue for failed jobs;
- automatic task archiving;
- isolated workflows for different publishing providers;
- secure configuration through environment variables.

Architecture:

Coda → Python Orchestrator → JSON Queue → ZennoPoster → Social Platforms → Status Sync

Technology stack:

- Python 3;
- Coda API;
- ZennoPoster;
- browser automation;
- JSON;
- REST API;
- python-dotenv;
- Windows Scheduler / cron;
- file-based queues.

The solution was used as an internal content automation pipeline, allowing the team to manage the content schedule and publishing results from a single Coda table without manually transferring posts between systems.

The project name and client-specific internal details are not disclosed due to project restrictions.

#Python #Automation #CodaAPI #ZennoPoster #BrowserAutomation #WorkflowAutomation #RESTAPI #ContentAutomation