Platform
Two-Way Calendar Sync
Agent bookings write to the real calendar; owner changes are read back and reconciled.
Webhook- Google Calendar API
- OAuth 2.0
- HMAC webhooks
- PostgreSQL
- Direction
- Two-way
Read the steps as a list
- trigger Owner edits in Google Calendar
- integration Push notification · Google Calendar
HMAC-signed.
- action Fetch changed event
- condition Would double-book?
- action Reconcile booking
- output Flag for a human
Refuses to silently overwrite when two sources of truth disagree.
- output Booking record updated
The problem
Kroma would happily show a booking as confirmed after the owner had already deleted it calendar-side. The customer turns up; nobody is expecting them.
How it works
Bookings the agent creates appear in the owner's actual Google Calendar. A push-notification pipeline watches for changes the owner makes there and reconciles them back.
The outcome
Owner-side deletes and moves are detected and reconciled. When a moved event would now double-book, it is flagged for a human rather than silently overwritten — the system refuses to guess when two sources of truth disagree.