Dropbox
Dropbox is a smart workspace company that provides secure file sharing, collaboration, and storage solutions
.
The Dropbox integration will allow you to connect agreements in Dropbox with Relyance.
In Dropbox:
- Log in to your Dropbox account.
- Navigate to each folder (from the left panel) you want Relyance AI to check as part of this contract integration and take note of the folder’s “path”, as displayed at the top of the page. For example, in the screenshot below, the folder is My Documents/Contracts/2022.

In Relyance:
Login to your Relyance account.
Navigate to the Settings menu on the bottom left-hand side.
Select Integrations.
Click on the Contract Integration tab.
Find the Dropbox integration card and click it to open its connections.
Select Oauth 2 / App token under Authentication Method.
The Authentication step asks for:
- Path of the folders containing contracts delimited by; (Eg: folder1; folder2): required.

- Paste the paths that you have noted from Dropbox in the text field. If there is more than one, place a semicolon (; ) between each one.
- For example, if your paths were “My Documents/Contracts/2022”, “Example/Path”, and “Quick/Brown/Fox”, then you should enter: My Documents/Contracts/2022;Example/Path;Quick/Brown/Fox
- Click Authenticate.
- This will bring up a login page on the Dropbox site.
- Click Continue on the message below.
- Click Allow on the next message box.
- At this point, you should see the following result on the Contract Integrations page:


- Congratulations, you are now connected to Dropbox.
Authentication methods and fields
Pick one of these under Authentication Method on the connection wizard's Authentication step. This table is generated from the integration catalog, so it always matches what the form actually asks for.
| Method | Required | Optional |
|---|---|---|
| Oauth2 / App Token | Path of the folders containing contracts delimited by ; |
— |
Manage this integration with Terraform
Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.
The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example dropbox/<connection_id>) or reading it with the relyance_integration_connection data source.