Caddi integrates with the Conga Platform so your loops can work with your Conga data. This guide walks you through creating API credentials in Conga and adding them to Caddi.
Before you start
You'll need:
Administrator access to your Conga Advantage Platform organization (to create an integration user and generate credentials)
Admin access to your Caddi workspace
Your Conga region: North America (NA), Europe (EU), or Australia (AU). If you're not sure, check the URL you use to sign in to Conga (`congacloud.com` = NA, `congacloud.eu` = EU, `congacloud.au` = AU)
Step 1: Create an integration user in Conga
Caddi authenticates as a single integration user in your Conga organization. We strongly recommend creating a dedicated user for Caddi rather than reusing a real person's account:
- If an employee leaves or changes their password, your Caddi integration keeps working.
- Conga's audit history will clearly show which actions came from Caddi.
- You can scope the user's permissions to exactly what your loops need.
To set it up:
Sign in to the Conga Advantage Platform as an administrator.
Create a new user for the integration (for example, `caddi-integration@yourcompany.com`). See Conga's guide: [Adding Users](https://documentation.conga.com/en/advantage-platform-administration/current/conga-advantage-platform-for-administrators/managing-users/adding-users).
Assign the user the roles/permissions needed for the data your loops will touch (e.g., agreements, documents). Caddi can only do what this user can do.
Generate a Client ID and Client Secret for the integration user, per the same Conga guide.
Copy both values somewhere safe, Conga may only show the secret once.
Step 2: Configure Conga in Caddi
In Caddi, go to Integrations on the Sidebar then click Integration Setup and find Conga.
Click Configure and enter:
Client ID — from Step 1
Client Secret — from Step 1
Region — where your Conga organization is hosted (defaults to NA)
Save. Caddi immediately verifies the credentials against Conga — if they're wrong, you'll see an error right away and nothing is stored until validation passes.
That's it. Caddi manages the connection from here.
How the connection behaves
- One shared identity. Everyone in your Caddi workspace who uses Conga in a loop acts as the integration user. Conga-side permissions and audit logs reflect that user, not the individual Caddi user.
- Revoking access. To cut Caddi off at any time, deactivate the integration user or revoke its credentials in Conga.
Having issues? Reach out to Caddi support with the error message you're seeing.