Skip to main content
Use the @bijection/connectors/google-calendar entrypoint to declare Google Calendar resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Calendar

incremental: incremental

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: google-calendar/calendar/incremental/standard. Connection and resource configuration are declared by this exact case. Credential kind: google-calendar. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: events
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection holds an OAuth google-calendar credential (googleCalendar.credential). Each binding selects one calendar with calendarId; discovery lists the calendars the connection can select. Writes are conditioned on the event’s opaque etag and authorized by the application’s governing rules. Semantics come from the admitted declaration: an incremental snapshot bounded by maxRows (at most 128 events for this profile), sync-token continuation with an explicit reset on 410 Gone, and channel push notifications that only request another read. Inspect the installed source for its exact profile. Authoring: this connector keeps its lower-level recipe. Its sync-token and page-token pair, reset status and channel subscription are provider facts that http.records does not claim.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.