Education Central Brain
Automation hub for an education business—syncs multiple Airtables, with Gmail and Calendly connectors built in.
Synced data across multiple Airtable bases automatically
Gmail connector for student and parent communication flows
Calendly connector for booking and calendar sync
Background
An education company already ran on Airtable—student records in one base, courses in another, payments somewhere else. Staff were copying rows by hand, emails were sent manually, and Calendly bookings did not always match their student database.
The problem
They needed a central brain that keeps multiple Airtables in sync, triggers actions when records change, and connects Gmail and Calendly so communication and scheduling are not separate from their data. Manual copy-paste between bases was slow and error-prone.
What I built
I built a Node.js automation layer that watches Airtable webhooks and scheduled jobs. When a record changes in one base, the brain updates the linked records in other bases using mapping rules. Gmail connector sends templated emails on triggers. Calendly connector creates or updates student records when someone books a session.
Product
Key features
Multi-Airtable sync
Define which fields map between bases. Changes propagate on create, update, and delete.
Gmail connector
Send emails from templates when a student enrolls, misses a class, or payment is due.
Calendly connector
New bookings create or update student rows and attach the session to the right course record.
Webhook orchestration
Incoming events from Airtable, Calendly, and Gmail are queued and processed in order.
Sync logs & retries
Admin view of what synced, what failed, and automatic retries for API rate limits.
Engineering
How it works technically
The important architectural decisions—not a laundry list of frameworks.
Integration layer
Node.js services with clear adapters for Airtable, Gmail, and Calendly so new connectors are easy to add.
Sync rules engine
JSON-defined mappings between bases—field IDs, transform rules, and conflict handling.
Serverless workers
AWS Lambda for webhook handlers and nightly reconciliation jobs across bases.
Impact
Results & takeaways
Challenges solved
- Airtable API rate limits when syncing large batches
- Duplicate records when the same student existed in two bases with different IDs
- Gmail OAuth refresh and Calendly webhook signature verification
What changed
- Staff stopped copying data between Airtable bases by hand
- Emails and bookings tied directly to student records
- One place to see sync status when something breaks
Outcomes
Faster onboarding when new students sign up online
Fewer missed emails and double-booked sessions
Operations team trusts the data across all their Airtable bases
Building something similar?
Tell me what you are building—I will share how I would approach it and whether we are a good fit.