ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Google Calendar event creation with Hangouts Meet conferencing

Calendar event creation through the cloud-connector mesh adds conference URIs and Hangouts Meet integration, with attendee management and pagination tokens. The event model decouples field mapping from JSON serialisation against API-version drift.

Scheduling is the third leg of business workflow — email, document, calendar. The platform's cloud-connector mesh had Gmail and Drive for the first two ; Calendar was the gap, and creating an event with a working conference link was the specific feature operations teams kept reaching to a side-system to handle.

This release adds full Calendar event creation with Hangouts Meet conferencing, attendee management and pagination on list operations. The refactored event model separates field mapping from JSON serialisation : the platform code talks to a typed domain object, the connector layer translates it to the Calendar API shape on the wire. Future API-version drift (Calendar API v3 → v4) affects only the connector translation ; the platform's event model stays stable.

  • Event creation with conference URI. Each event auto-provisions a Meet link ; the URI is returned in the event response for inclusion in subsequent emails and invitation surfaces.
  • Attendee management. Add, remove and update attendee response status ; the platform retains the canonical attendee list separate from Google's representation for audit.
  • Pagination tokens. List operations honour Google's pagination contract ; long calendars iterate cleanly without out-of-memory failure on the platform side.
  • Decoupled translation. The connector's mapping layer is unit-tested independently of the platform's event model so API drift surfaces as a contained test failure, not a runtime breakage.

See the feature →

← All posts