PostPilotLive
Automated Social Posting Platform
- React
- Node.js
- Google APIs
Overview & Problem
Small organizations already run their schedule out of Google Calendar — but turning each event into a timely social post is manual, repetitive, and easy to forget. PostPilot closes that loop.
What I Built
Google Calendar API integration that extracts event metadata and dynamically generates formatted post content per platform.
Backend workflows that schedule, format, and publish posts to multiple social platforms.
A React frontend for connecting accounts, previewing posts, and overriding generated copy.
Architecture
PostPilot treats the calendar as the source of truth: each event is expanded into platform-specific posts that are generated, scheduled, and published automatically, with a React dashboard as the human checkpoint before anything goes live.
See it in action
Key Technical Decisions & Tradeoffs
Posting is driven off calendar events rather than a fixed cron sweep: each event's start time defines when its posts go out, so the schedule itself is the trigger. Publishing runs through a queue with retries, so a transient failure from a platform's API is retried rather than silently dropping a scheduled post.
Rather than blasting one identical message everywhere, PostPilot generates platform-specific copy from each event's metadata — tuned to the length, tone, and formatting each network expects. The dashboard's preview-and-override step keeps a human in the loop, so generated copy can be corrected before it publishes instead of reading like automated spam.
Results
Deployed and live at postpilot.company, PostPilot turns calendar events into scheduled, platform-specific posts end-to-end without manual intervention.
Calendar-as-source-of-truth means an organisation schedules an event once and the posts follow automatically, with the dashboard's preview-and-override step as the only human touchpoint before publishing.