The connector authenticates as a Guru user with HTTP Basic auth. The user whose
token you use must be able to read the team’s members and groups. A user with an
administrative role on the team is the safest choice.
1
Sign in to Guru with the account you want the connector to use.
2
Create an API token for that account from your Guru API settings. Note the
account’s email address — it is the username half of the credential.
3
Copy the token value. You provide the account email as User Email and
the token as API Token when configuring the connector.
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 Guru and click Add.
3
Choose how to set up the new Guru 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 Guru credentials:
User Email: The email address of the Guru user whose token you are using.
API Token: That user’s Guru API 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 Guru connector is now pulling access data into C1.
Follow these instructions to run the Guru connector in your own environment.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for Baton and click Add.
3
Choose how to set up the new Guru connector, set the owner, and click Next.
4
In the Settings area, click Edit, then click Rotate to
generate a new Client ID and Client Secret. Store these values securely
for your deployment.
5
Configure C1 credentials and Guru credentials as environment variables:
BATON_CLIENT_ID=<C1 client ID>BATON_CLIENT_SECRET=<C1 client secret>BATON_HOST_ID=baton-guruBATON_USER_EMAIL=<Guru user email>BATON_API_TOKEN=<Guru API token>
6
Deploy the connector using your standard self-hosted connector process.
Done. Your Guru connector is now pulling access data into C1.