The connector syncs the members of a single GrowthBook organization as user
identities. Each user carries their organization-wide role, the teams they
belong to, and the projects they have a scoped role in, so you can see who has
access to your GrowthBook organization and at what level.
You need a GrowthBook secret API key with permission to read members. It
grants organization-wide API access, so treat it as a secret. A client/SDK key
will not work — the REST API requires a secret key.
1
Sign in to GrowthBook as an administrator of the organization you want to
sync.
2
Open Settings, then go to the API Keys area and find the
organization Secret keys section.
3
Click Create New Secret Key, give it a role that can read members (a
readonly organization key is enough), and copy the generated key — you
will not be able to see it again.
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 GrowthBook and click Add.
3
Choose how to set up the new GrowthBook 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 GrowthBook credentials:
Secret API key: The secret API key you created.
Base URL (optional): Leave blank for GrowthBook Cloud. Set it only
if you run a self-hosted GrowthBook instance, using your instance’s
host (for example, https://growthbook.your-company.com).
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 GrowthBook connector is now pulling access data into C1.
Follow these instructions to run the GrowthBook connector in your own
environment.
1
Create a secret for the GrowthBook secret API key.
2
Configure the connector environment variables:
BATON_GROWTHBOOK_SECRET_KEY: The GrowthBook secret API key (store this as a secret).
BATON_GROWTHBOOK_BASE_URL (optional): Your GrowthBook host, if self-hosted. Leave unset for GrowthBook Cloud.
3
Deploy the connector using your standard self-hosted connector process.
Done. Your GrowthBook connector is now pulling access data into C1.