Set up a Rocket.Chat connector

C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1 for unified visibility and governance over user access.

C1 provides identity governance for Rocket.Chat. Integrate your Rocket.Chat workspace with C1 for unified visibility and governance over user access.

Capabilities

Resource	Sync	Provision
Users
Roles
Teams

The connector reads one Rocket.Chat workspace. It syncs the workspace’s users, roles, and teams, along with each user’s workspace-level role assignments and each team’s membership. Users sync as enabled or disabled based on their active state in Rocket.Chat, and bot and app accounts are labeled as service accounts. Users reached through Matrix federation are marked with a federated attribute.

Roles cover both the built-in roles (admin, user, bot, and so on) and any custom roles defined in the workspace. Role assignments reflect workspace-level roles; roles scoped to individual channels (such as owner or moderator of a single room) sync as role resources for visibility but do not carry per-channel assignments.

Rate limits

Rocket.Chat’s REST API limits each endpoint to 10 requests per 60 seconds by default. The connector backs off and retries automatically when it hits the limit, but on workspaces with many users or teams a sync can take noticeably longer under the default limit. Workspace administrators can raise the limit under Admin > Settings > Rate Limiter to speed up syncs.

Gather Rocket.Chat credentials

The token’s account needs administrator access (or at minimum permission to view users, roles, and all teams — including the view-all-teams permission). A token created by a regular user cannot list other users or teams it is not a member of and does not work with this connector.

1. Sign in to your Rocket.Chat workspace as an administrator, or use a dedicated service account with administrator access.

2. Open your avatar menu and go to My Account > Personal Access Tokens. If personal access tokens are disabled, a workspace administrator can enable them under Admin > Settings > Accounts > Personal Access Tokens.

3. Enter a token name and click Add. Rocket.Chat shows the new token and the matching user ID once — copy both. The connector needs the pair: the token is sent as the X-Auth-Token header and the user ID as the X-User-Id header.

4. Note your workspace’s base URL. For Rocket.Chat Cloud this is https://<workspace>.rocket.chat; for self-hosted servers it is your own address, with no trailing slash.

Configure the Rocket.Chat connector

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for Rocket.Chat and click Add.

3. Choose how to set up the new Rocket.Chat connector.

4. Set the owner for this connector.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter the Rocket.Chat credentials:

   • Rocket.Chat base URL: your workspace’s address, with no trailing slash. For example, https://mycompany.rocket.chat.
   • User ID: the user ID shown when the personal access token was created.
   • Auth token: the personal access token.
8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Rocket.Chat connector is now pulling access data into C1.

Self-hosted

Follow these instructions to run the Rocket.Chat connector in your own environment.

1. Create secrets for the Rocket.Chat credentials.

2. Configure the connector environment variables:

   • BATON_ROCKETCHAT_BASE_URL: your workspace’s address, with no trailing slash. For example, https://mycompany.rocket.chat.
   • BATON_ROCKETCHAT_USER_ID: the user ID shown when the personal access token was created.
   • BATON_ROCKETCHAT_AUTH_TOKEN: the personal access token.
3. Deploy the connector using your standard self-hosted connector process.

Done. Your Rocket.Chat connector is now pulling access data into C1.