Multi-SNS Auto Scheduler Development
Budget: $30 – $250 USD
I need a reliable system that can take our prepared text and video assets and publish them automatically across multiple social networks. After our kickoff call I will share the exact platform list and credentials, but the solution should be flexible enough to add or remove channels without major re-work.
Key objectives:
• Configure multi-platform auto-upload through Comet, mapping captions, thumbnails, tags, and any platform-specific metadata.
• Create scheduling rules so each post goes live at the time I set—daily, weekly, or according to custom calendars.
• Build a distribution workflow that queues content, validates it against each API’s limits, and triggers retries on transient errors.
• Add an error-detection layer with clear logging and alerts so I can see failures, root causes, and automatic retries in one place.
• Deliver deployment scripts and concise documentation so I can run the system locally or inside our existing cloud environment.
The finished deliverable should include:
1. Source code and configuration files.
2. A short architecture diagram and README.
3. A test run showing successful posts, logged events, and graceful recovery from at least one simulated failure.
If you have prior experience with Comet (or similar middleware) and social-platform APIs, I’d love to see brief examples. Let’s discuss timelines and any clarifications in our first call.
Key objectives:
• Configure multi-platform auto-upload through Comet, mapping captions, thumbnails, tags, and any platform-specific metadata.
• Create scheduling rules so each post goes live at the time I set—daily, weekly, or according to custom calendars.
• Build a distribution workflow that queues content, validates it against each API’s limits, and triggers retries on transient errors.
• Add an error-detection layer with clear logging and alerts so I can see failures, root causes, and automatic retries in one place.
• Deliver deployment scripts and concise documentation so I can run the system locally or inside our existing cloud environment.
The finished deliverable should include:
1. Source code and configuration files.
2. A short architecture diagram and README.
3. A test run showing successful posts, logged events, and graceful recovery from at least one simulated failure.
If you have prior experience with Comet (or similar middleware) and social-platform APIs, I’d love to see brief examples. Let’s discuss timelines and any clarifications in our first call.
Related categories:
PHP
JavaScript
Python
Software Architecture
Node.js
Software Development
API
RESTful API
Cloud
Automation