Google Calendar List (google_calendar_list_v1)

This integration is included in WebhookDB Enterprise.

Replicate Google Calendar Lists into your database. Each linked user gets one Calendar List row.

To get set up, run this code from the WebhookDB CLI:

webhookdb integrations create google_calendar_list_v1

Source documentation for this API:


This replicator is required for the creation of the following dependents:
Supports Webhooks
Supports Backfilling
Enterprise Only


Tables replicated from Google Calendar Lists have this schema. Note that the data types listed are for Postgres; when replicating to other databases, other data types maybe used.

Column Type Indexed
pk bigint  
external_owner_id text  
row_created_at timestamptz
row_updated_at timestamptz
encrypted_refresh_token text  
sync_token text  
watch_channel_id text  
watch_resource_id text  
watch_channel_expiration timestamptz
data* jsonb  

* The data column contains the raw payload from the webhook or API. In many cases there is no canonical form, like if a webhook and API request return two different versions of the same resource. In that case we try to keep the most coherent and detailed resource.”

Table definition

This definition can also be generated through webhookdb fixture google_calendar_list_v1.

CREATE TABLE public.google_calendar_list_v1_fixture (
  pk bigserial PRIMARY KEY,
  external_owner_id text UNIQUE NOT NULL,
  row_created_at timestamptz,
  row_updated_at timestamptz,
  encrypted_refresh_token text,
  sync_token text,
  watch_channel_id text,
  watch_resource_id text,
  watch_channel_expiration timestamptz,
  data jsonb NOT NULL
CREATE INDEX IF NOT EXISTS svi_fixture_row_created_at_idx ON public.google_calendar_list_v1_fixture (row_created_at);
CREATE INDEX IF NOT EXISTS svi_fixture_row_updated_at_idx ON public.google_calendar_list_v1_fixture (row_updated_at);
CREATE INDEX IF NOT EXISTS svi_fixture_watch_channel_expiration_idx ON public.google_calendar_list_v1_fixture (watch_channel_expiration);