- You say it once, from the app, a chat or your terminal.
- She does the work: research, copy shaped to each platform, and an image or video to match.
- The calendar is yours: let it run on autopilot, edit anything before it goes out, or ask for drafts and publish them yourself.
- It goes out on time, every time. She fires each post exactly when planned and retries on failure, because Temporal is holding the clock and quietly refreshing your platform tokens in the background.
Architecture
Three services do her own work, and four more back them up. In most installs those three share a single Docker container and talk to each other through HTTP. The supporting services run alongside them, usually in containers of their own.What the orchestrator actually runs
What the orchestrator actually runs
Temporal workflows took over the jobs that used to run on cron and worker processes:
- Posting scheduled content to the platforms
- Refreshing platform tokens
- Sending digest and notification emails
- Checking for missing posts and auto-posting
- Tracking posting streaks
Why Temporal and not a cron job
Why Temporal and not a cron job
Schedule a post three weeks out, restart the server twice in between, and it still fires on the right minute.
- Durable state. Workflow state is persisted, so a workflow picks up where it left off after a restart
- Retries. A failure is retried rather than dropped
- Task queues. Each platform gets its own, for concurrency control
- Visibility. A built-in UI for watching and debugging runs