Skip to content
Book a demoStart free
Connectors

Rocket.Chat connector

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

Rocket.Chat connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Rocket.Chat 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 customer support data instead of moving it.

Sync your Rocket.Chat data into BigQuery with Kaivo to analyse channels, messaging, and team activity.

CategoryCustomer Service
AuthenticationAPI key
SetupSelf-service

Getting started with the Rocket.Chat connector

Section titled “Getting started with the Rocket.Chat connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Rocket.Chat account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your Personal Access Token.

Field Description
Personal Access Token
A Personal Access Token created in your Rocket.Chat account under Profile → Personal Access Tokens. See the docs. The token is case sensitive.

|

When you set up the connector, you provide:

Field Description
Instance URL
Your Rocket.Chat instance URL, including https://. Do not add a trailing slash or path.

| | User ID |

The user ID shown next to the token when you create your Personal Access Token.

|

Tables and columns synced from Rocket.Chat

Section titled “Tables and columns synced from Rocket.Chat”

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

channels (18 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_id STRING
_updated_at STRING
broadcast BOOL
default BOOL
description STRING
encrypted BOOL
fname STRING
msgs INT64
name STRING
ro BOOL
sys_mes BOOL
t STRING
team_id STRING
team_main BOOL
ts STRING
users_count INT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
roles (8 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_id STRING
description STRING
mandatory2fa BOOL
name STRING
protected BOOL
scope STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
rooms (18 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_id STRING
_updated_at STRING
broadcast BOOL
default BOOL
description STRING
encrypted BOOL
federated BOOL
fname STRING
lm STRING
msgs INT64
name STRING
ro BOOL
sys_mes BOOL
t STRING
ts STRING
users_count INT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
subscriptions (15 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
_id STRING
_updated_at STRING
alert BOOL
fname STRING
group_mentions INT64
ls STRING
name STRING
open BOOL
rid STRING
t STRING
ts STRING
unread INT64
user_mentions INT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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.
teams (10 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type INT64
_id STRING
_updated_at STRING
created_at STRING
name STRING
number_of_users INT64
room_id STRING
rooms INT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
users (10 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
type STRING
_id STRING
active BOOL
last_login STRING
name STRING
name_insensitive STRING
status STRING
username STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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.
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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 STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Rocket.Chat 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.

How long does the initial sync take for Rocket.Chat?

Section titled “How long does the initial sync take for Rocket.Chat?”

It depends on how much history is in your Rocket.Chat 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.

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 Rocket.Chat’s schema changes?

Section titled “What happens when Rocket.Chat’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 Rocket.Chat, 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.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

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 Rocket.Chat 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 Rocket.Chat connector in Kaivo and all of its synced data is deleted with it.

Use channels and rooms to track messaging activity over time.

Join teams with users to see where conversation happens.

Use roles and subscriptions to review access across your workspace.

Use Rocket.Chat data in your AI and BI tools

Section titled “Use Rocket.Chat data in your AI and BI tools”

Once Rocket.Chat 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 Rocket.Chat data.

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

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

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

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

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

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

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

See our pricing page for Rocket.Chat connector pricing and plan details.

  • HubSpot: Sync HubSpot to BigQuery.
  • Dixa: Sync Dixa to BigQuery.
  • Freshservice: Sync Freshservice to BigQuery.
  • Genesys: Sync Genesys to BigQuery.
  • Gorgias: Sync Gorgias to BigQuery.
  • giosg: Sync giosg to BigQuery.