@bijection/connectors/google-contacts entrypoint to declare Google Contacts 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.
Contacts
sync: People API sync tokens with deleted contacts
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:google-contacts/connections/sync/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: google-contacts. Keep credential material in the private credential inventory.
Inspect the complete configuration contract below for settings and conditional requirements.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
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. A Google OAuth token with a contacts scope authorizeshttps://people.googleapis.com/.
connections.sync is the People API’s sync-token export. A full pass with requestSyncToken=true establishes the user’s contacts (at most 25,000), and later passes read changes with syncToken, repeated on every page. A contact returned with metadata.deleted: true is withdrawn. An expired token (HTTP 410, EXPIRED_SYNC_TOKEN, seven days after the full sync) resets to a full pass. Writes take minutes to appear in sync results. Read-only.
Built from the provider’s published API documentation; nothing here has run against Google Contacts or been qualified.
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.