Statuspage connector

Set up the Statuspage connector in Kaivo: authentication, configuration, the 7 BigQuery tables it syncs, and answers to common questions.

Written By Lauri Raivio

Last updated 16 days ago

Kaivo is a fully managed data platform that syncs your Statuspage data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from Statuspage instead of moving it.

What is the Statuspage connector

Sync your Statuspage incident data into BigQuery with Kaivo to analyse uptime, incidents, and subscriber trends over time.

Category	Tech
Authentication	API key
Setup	Self-service

Getting started with the Statuspage connector

Sign up for Kaivo and create a workspace.
Connect your Statuspage account.
Choose which tables to sync.
Wait for the initial sync to finish.
Query your data in BigQuery or your favourite AI or BI tool.

Authenticating Statuspage

Authenticate with your API Key.

Field	Description
API Key	Your API Key. See here.

Tables and columns synced from Statuspage

Kaivo syncs 7 tables from Statuspage into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

components (16 columns), Add page access groups to a component

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`automation_email`	`STRING`	Requires a special feature flag to be enabled
`created_at`	`TIMESTAMP`
`description`	`STRING`	More detailed description for component
`group`	`BOOL`	Is this component a group
`group_id`	`STRING`	Component Group identifier
`id`	`STRING`	Identifier for component
`name`	`STRING`	Display name for component
`only_show_if_degraded`	`BOOL`	Requires a special feature flag to be enabled
`page_id`	`STRING`	Page identifier
`position`	`INT64`	Order the component will appear on the page
`showcase`	`BOOL`	Should this component be showcased
`start_date`	`DATE`	The date this component started being used
`status`	`STRING`	Status of component
`updated_at`	`TIMESTAMP`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

incident_templates (10 columns), Get a list of templates

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`body`	`STRING`	Body of the incident or maintenance update to be applied when selecting this template
`group_id`	`STRING`	Identifier of Template Group this template belongs to
`id`	`STRING`	Incident Template Identifier
`name`	`STRING`	Name of the template, as shown in the list on the "Templates" tab of the "Incidents" page
`should_send_notifications`	`BOOL`	Whether the "deliver notifications" checkbox should be selected when selecting this template
`should_tweet`	`BOOL`	Whether the "tweet update" checkbox should be selected when selecting this template
`title`	`STRING`	Title to be applied to the incident or maintenance when selecting this template
`update_status`	`STRING`	The status the incident or maintenance should transition to when selecting this template
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: incident_templates__components

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`automation_email`	`STRING`	Requires a special feature flag to be enabled
`created_at`	`TIMESTAMP`
`description`	`STRING`	More detailed description for component
`group`	`BOOL`	Is this component a group
`group_id`	`STRING`	Component Group identifier
`id`	`STRING`	Identifier for component
`name`	`STRING`	Display name for component
`only_show_if_degraded`	`BOOL`	Requires a special feature flag to be enabled
`page_id`	`STRING`	Page identifier
`position`	`INT64`	Order the component will appear on the page
`showcase`	`BOOL`	Should this component be showcased
`start_date`	`DATE`	The date this component started being used
`status`	`STRING`	Status of component
`updated_at`	`TIMESTAMP`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

incidents (28 columns), Get an incident

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`auto_transition_deliver_notifications_at_end`	`BOOL`	Controls whether send notification when scheduled maintenances auto transition to completed.
`auto_transition_deliver_notifications_at_start`	`BOOL`	Controls whether send notification when scheduled maintenances auto transition to started.
`auto_transition_to_maintenance_state`	`BOOL`	Controls whether change components status to under_maintenance once scheduled maintenance is in progress.
`auto_transition_to_operational_state`	`BOOL`	Controls whether change components status to operational once scheduled maintenance completes.
`created_at`	`TIMESTAMP`	The timestamp when the incident was created at.
`id`	`STRING`	Incident Identifier
`impact`	`STRING`	The impact of the incident.
`monitoring_at`	`TIMESTAMP`	The timestamp when incident entered monitoring state.
`name`	`STRING`	Incident Name
`page_id`	`STRING`	Incident Page Identifier
`postmortem_body`	`STRING`	Body of the Postmortem.
`postmortem_body_last_updated_at`	`TIMESTAMP`	The timestamp when the incident postmortem body was last updated at.
`postmortem_ignored`	`BOOL`	Controls whether the incident will have postmortem.
`postmortem_notified_subscribers`	`BOOL`	Indicates whether subscribers are already notificed about postmortem.
`postmortem_notified_twitter`	`BOOL`	Controls whether to decide if notify postmortem on twitter.
`postmortem_published_at`	`BOOL`	The timestamp when the postmortem was published.
`resolved_at`	`TIMESTAMP`	The timestamp when incident was resolved.
`scheduled_auto_completed`	`BOOL`	Controls whether the incident is scheduled to automatically change to complete.
`scheduled_auto_in_progress`	`BOOL`	Controls whether the incident is scheduled to automatically change to in progress.
`scheduled_for`	`TIMESTAMP`	The timestamp the incident is scheduled for.
`scheduled_remind_prior`	`BOOL`	Controls whether to remind subscribers prior to scheduled incidents.
`scheduled_reminded_at`	`TIMESTAMP`	The timestamp when the scheduled incident reminder was sent at.
`scheduled_until`	`TIMESTAMP`	The timestamp the incident is scheduled until.
`shortlink`	`STRING`	Incident Shortlink.
`status`	`STRING`	The incident status. For realtime incidents, valid values are investigating, identified, monitoring, and resolved. For scheduled incidents, valid values are scheduled, in_progress, verifying, and completed.
`updated_at`	`TIMESTAMP`	The timestamp when the incident was updated at.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: incidents__components

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`automation_email`	`STRING`	Requires a special feature flag to be enabled
`created_at`	`TIMESTAMP`
`description`	`STRING`	More detailed description for component
`group`	`BOOL`	Is this component a group
`group_id`	`STRING`	Component Group identifier
`id`	`STRING`	Identifier for component
`name`	`STRING`	Display name for component
`only_show_if_degraded`	`BOOL`	Requires a special feature flag to be enabled
`page_id`	`STRING`	Page identifier
`position`	`INT64`	Order the component will appear on the page
`showcase`	`BOOL`	Should this component be showcased
`start_date`	`DATE`	The date this component started being used
`status`	`STRING`	Status of component
`updated_at`	`TIMESTAMP`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: incidents__incident_updates

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`body`	`STRING`	Incident update body.
`created_at`	`TIMESTAMP`	The timestamp when the incident update was created at.
`custom_tweet`	`STRING`	An optional customized tweet message for incident postmortem.
`deliver_notifications`	`BOOL`	Controls whether to delivery notifications.
`display_at`	`TIMESTAMP`	Timestamp when incident update is happened.
`id`	`STRING`	Incident Update Identifier.
`incident_id`	`STRING`	Incident Identifier.
`status`	`STRING`	The incident status. For realtime incidents, valid values are investigating, identified, monitoring, and resolved. For scheduled incidents, valid values are scheduled, in_progress, verifying, and completed.
`tweet_id`	`STRING`	Tweet identifier associated to this incident update.
`twitter_updated_at`	`TIMESTAMP`	The timestamp when twitter updated at.
`updated_at`	`TIMESTAMP`	The timestamp when the incident update is updated.
`wants_twitter_update`	`BOOL`	Controls whether to create twitter update.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: incidents__incident_updates__affected_components

Column	Type	Description
`_kaivo_parent_id`	`STRING`	Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`value`	`JSON`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

metrics (20 columns), Create a metric for a metric provider

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`backfill_percentage`	`INT64`
`backfilled`	`BOOL`
`created_at`	`TIMESTAMP`
`decimal_places`	`INT64`
`display`	`BOOL`	Should the metric be displayed
`id`	`STRING`	Metric identifier
`last_fetched_at`	`TIMESTAMP`
`metric_identifier`	`STRING`	Metric Display identifier used to look up the metric data from the provider
`metrics_provider_id`	`STRING`	Metric Provider identifier
`most_recent_data_at`	`TIMESTAMP`
`name`	`STRING`	Name of metric
`reference_name`	`STRING`
`suffix`	`STRING`	Suffix to describe the units on the graph
`tooltip_description`	`STRING`
`updated_at`	`TIMESTAMP`
`y_axis_hidden`	`BOOL`	Should the values on the y axis be hidden on render
`y_axis_max`	`FLOAT64`
`y_axis_min`	`FLOAT64`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

pages (42 columns), Get a page

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`activity_score`	`FLOAT64`
`allow_email_subscribers`	`BOOL`	Can your users choose to receive notifications via email
`allow_incident_subscribers`	`BOOL`	Can your users subscribe to notifications for a single incident
`allow_page_subscribers`	`BOOL`	Can your users subscribe to all notifications on the page
`allow_rss_atom_feeds`	`BOOL`	Can your users choose to access incident feeds via RSS/Atom (not functional on Audience-Specific pages)
`allow_sms_subscribers`	`BOOL`	Can your users choose to receive notifications via SMS
`allow_webhook_subscribers`	`BOOL`	Can your users choose to receive notifications via Webhooks
`branding`	`STRING`	The main template your statuspage will use
`city`	`STRING`
`country`	`STRING`
`created_at`	`TIMESTAMP`	Timestamp the record was created
`css_blues`	`STRING`	CSS Color
`css_body_background_color`	`STRING`	CSS Color
`css_border_color`	`STRING`	CSS Color
`css_font_color`	`STRING`	CSS Color
`css_graph_color`	`STRING`	CSS Color
`css_greens`	`STRING`	CSS Color
`css_light_font_color`	`STRING`	CSS Color
`css_link_color`	`STRING`	CSS Color
`css_no_data`	`STRING`	CSS Color
`css_oranges`	`STRING`	CSS Color
`css_reds`	`STRING`	CSS Color
`css_yellows`	`STRING`	CSS Color
`domain`	`STRING`	CNAME alias for your status page
`headline`	`STRING`
`hidden_from_search`	`BOOL`	Should your page hide itself from search engines
`id`	`STRING`	Page identifier
`ip_restrictions`	`STRING`
`name`	`STRING`	Name of your page to be displayed
`notifications_email_footer`	`STRING`	Allows you to customize the footer appearing on your notification emails. Accepts Markdown for formatting
`notifications_from_email`	`STRING`	Allows you to customize the email address your page notifications come from
`page_description`	`STRING`
`state`	`STRING`
`subdomain`	`STRING`	Subdomain at which to access your status page
`support_url`	`STRING`
`time_zone`	`STRING`	Timezone configured for your page
`twitter_username`	`STRING`
`updated_at`	`TIMESTAMP`	Timestamp the record was last updated
`url`	`STRING`	Website of your page. Clicking on your statuspage image will link here.
`viewers_must_be_team_members`	`BOOL`
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

subscribers (17 columns), Get an incident subscriber

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`components`	`STRING`	The components for which the subscriber has elected to receive updates.
`created_at`	`TIMESTAMP`
`display_phone_number`	`STRING`	A formatted version of the phone_number and phone_country pair, nicely formatted for display.
`email`	`STRING`	The email address to use to contact the subscriber. Used for Email and Webhook subscribers.
`endpoint`	`STRING`	The URL where a webhook subscriber elects to receive updates.
`id`	`STRING`	Subscriber Identifier
`mode`	`STRING`	The communication mode of the subscriber.
`obfuscated_channel_name`	`STRING`	Obfuscated slack channel name
`page_access_user_id`	`STRING`	The Page Access user this subscriber belongs to (only for audience-specific pages).
`phone_country`	`STRING`	The two-character country code representing the country of which the phone_number is a part.
`phone_number`	`STRING`	The phone number used to contact an SMS subscriber
`purge_at`	`TIMESTAMP`	The timestamp when a quarantined subscriber will be purged (unsubscribed).
`quarantined_at`	`TIMESTAMP`	The timestamp when the subscriber was quarantined due to an issue reaching them.
`skip_confirmation_notification`	`BOOL`	If this is true, do not notify the user with changes to their subscription.
`workspace_name`	`STRING`	The workspace name of the slack subscriber.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

subscribers_histogram_by_state (22 columns), Get a histogram of subscribers by type and then state

Column	Type	Description
`_kaivo_id`	`STRING`	Primary key that uniquely identifies the row. Auto-generated by Kaivo.
`email__active`	`INT64`	The number of active subscribers found by the query.
`email__quarantined`	`INT64`	The number of quarantined subscribers found by the query.
`email__total`	`INT64`	The total number of subscribers found by the query.
`email__unconfirmed`	`INT64`	The number of unconfirmed subscribers found by the query.
`integration_partner__active`	`INT64`	The number of active subscribers found by the query.
`integration_partner__quarantined`	`INT64`	The number of quarantined subscribers found by the query.
`integration_partner__total`	`INT64`	The total number of subscribers found by the query.
`integration_partner__unconfirmed`	`INT64`	The number of unconfirmed subscribers found by the query.
`slack__active`	`INT64`	The number of active subscribers found by the query.
`slack__quarantined`	`INT64`	The number of quarantined subscribers found by the query.
`slack__total`	`INT64`	The total number of subscribers found by the query.
`slack__unconfirmed`	`INT64`	The number of unconfirmed subscribers found by the query.
`sms__active`	`INT64`	The number of active subscribers found by the query.
`sms__quarantined`	`INT64`	The number of quarantined subscribers found by the query.
`sms__total`	`INT64`	The total number of subscribers found by the query.
`sms__unconfirmed`	`INT64`	The number of unconfirmed subscribers found by the query.
`webhook__active`	`INT64`	The number of active subscribers found by the query.
`webhook__quarantined`	`INT64`	The number of quarantined subscribers found by the query.
`webhook__total`	`INT64`	The total number of subscribers found by the query.
`webhook__unconfirmed`	`INT64`	The number of unconfirmed subscribers found by the query.
`_kaivo_extracted_at`	`TIMESTAMP`	Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

How the Statuspage sync works

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Statuspage supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won't get duplicate rows.

Frequently asked questions

How long does the initial sync take for Statuspage?

It depends on how much history is in your Statuspage account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they're much faster.

Can I sync only some tables or columns?

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don't select are never copied to your warehouse.

What happens when Statuspage's schema changes?

New fields are never added automatically. You choose which fields to sync, so data you haven't selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table's sync mode: full-refresh tables always match what's currently in Statuspage, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Statuspage instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Statuspage connector in Kaivo and all of its synced data is deleted with it.

Common use cases for Statuspage data

Incident history

Use incidents to track frequency, duration, and affected components over time.

Component reliability

Join incidents with components to find which systems cause the most disruption.

Subscriber trends

Bring subscribers into BigQuery to see how your status audience grows.

Uptime reporting

Use metrics to report on uptime alongside your other reliability data.

Use Statuspage data in your AI and BI tools

Once Statuspage data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here's how the most common destinations work with Statuspage data.

Claude

Use Kaivo's MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Power BI

Microsoft's BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Data Studio

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

Tableau

The premium analytics standard, with native BigQuery integration. Setup guide →

Google Sheets

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Excel

Connect via Power Query's BigQuery connector. Setup guide →

Metabase

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Statuspage connector pricing and plan details.

Adform: Sync Adform to BigQuery.
Amplitude: Sync Amplitude to BigQuery.
Auth0: Sync Auth0 to BigQuery.
Convex: Sync Convex to BigQuery.
GitHub: Sync GitHub to BigQuery.
GitLab: Sync GitLab to BigQuery.

Was this helpful?

Still need help? Share an idea