Problem
Fact Hub's editorial pipeline involved manual handoffs between drafting, review, publishing, and distribution. Human coordination across Google Docs, spreadsheets, and messaging channels introduced delays, missed notifications, and occasional data inconsistencies.
Approach
- — Designed a reactive state machine mapping each content piece through defined lifecycle stages.
- — Built Google Apps Script services triggering on document and sheet changes.
- — Integrated Slack and email APIs for automated reviewer notifications and status updates.
- — Added validation gates at each state transition to enforce data integrity.
Outcome
- Editorial pipeline automated end-to-end with 99%+ uptime over production months.
- Zero data integrity incidents after state machine deployment.
- Review cycle time reduced by eliminating manual status coordination.
Metrics
- Uptime
- 99%+
- Production environments
- Integrity
- 100%
- No data loss across transitions
- Integrations
- 3
- Workspace · Slack · Email
- Pattern
- State machine
- Reactive lifecycle
Architecture
Content ItemsDocs & sheets
Event TriggersApps Script
State MachineLifecycle stages
NotificationsSlack · email
Validation GatesIntegrity checks
Trade-offs
Platform
Chosen
Google Apps Script
Alternative
Custom Node.js microservice
Editorial team already lives in Google Workspace. Apps Script keeps automation where the data already resides with zero new infrastructure.
Orchestration
Chosen
Reactive state machine
Alternative
Cron-based batch processing
Content changes are event-driven. A state machine responds immediately to transitions instead of polling on a schedule.
Next project
0%