Storage Provider Integrations

Storage provider integrations connect external document repositories to your OmniBots workspace. Once configured, these integrations allow your Knowledge Bases to sync documents from external sources automatically, keeping your bot's knowledge up to date without manual file uploads.

Supported Providers

Provider	Authentication	Use Case
SharePoint	OAuth 2.0 (Azure AD app registration)	Corporate document libraries
Google Drive	OAuth 2.0 or service account	Shared drives and team folders
Amazon S3	IAM access key + secret	Cloud object storage
Dropbox	OAuth 2.0 (app token)	Team file sharing
OneDrive	OAuth 2.0 (Azure AD app registration)	Personal and business cloud storage
Box	OAuth 2.0 or JWT (server auth)	Enterprise content management
Azure Blob	Connection string or SAS token	Azure cloud object storage

Configuring SharePoint

1. Go to Settings > Integrations > Add Integration.
2. Select Storage as the type, then choose SharePoint.
3. Enter your Azure AD Tenant ID, Client ID, and Client Secret from your app registration.
4. Enter the SharePoint Site URL (e.g., https://yourorg.sharepoint.com/sites/docs).
5. Click Test Connection, then Save.

TIP

The Azure AD app registration requires the Sites.Read.All Microsoft Graph API permission. Use application permissions (not delegated) so the integration works without a signed-in user.

Configuring Google Drive

1. Select Storage > Google Drive.
2. Upload or paste your service account JSON key, or use OAuth to authorize access.
3. Enter the Folder ID or Shared Drive ID to scope the integration.
4. Click Test Connection, then Save.

Configuring Amazon S3

1. Select Storage > S3.
2. Enter your Access Key ID and Secret Access Key.
3. Enter the Bucket Name and Region (e.g., us-east-1).
4. Optionally set a Prefix to limit access to a specific folder path.
5. Click Test Connection, then Save.

Configuring Dropbox

1. Select Storage > Dropbox.
2. Enter your App Key and App Secret from the Dropbox developer console.
3. Complete the OAuth flow to authorize access.
4. Click Test Connection, then Save.

Configuring OneDrive

1. Select Storage > OneDrive.
2. Enter your Azure AD Tenant ID, Client ID, and Client Secret.
3. Click Test Connection, then Save.

Configuring Box

1. Select Storage > Box.
2. Choose authentication method: OAuth 2.0 or JWT (Server Auth).
3. For JWT, upload your Box app configuration JSON file.
4. For OAuth, enter your Client ID and Client Secret, then complete the authorization flow.
5. Click Test Connection, then Save.

Configuring Azure Blob

1. Select Storage > Azure Blob.
2. Enter your Connection String or a SAS Token with read and list permissions.
3. Enter the Container Name.
4. Click Test Connection, then Save.

WARNING

Use SAS tokens with the narrowest scope possible. Grant only read and list permissions, and set an expiration date. Rotate tokens before they expire to avoid service interruptions.

imageStorage provider selection screen showing provider cards for SharePoint, Google Drive, S3, Dropbox, OneDrive, Box, and Azure Blob, with a configuration form for the selected provider showing credential fields and test connection button

Storage provider configuration

Using Storage Integrations in Knowledge Bases

After configuring a storage integration, you can add it as a document source in any Knowledge Base:

1. Open a Knowledge Base and go to the Document Sources tab.
2. Click Add External Source.
3. Select the storage integration from the dropdown.
4. Browse folders and select which files or directories to sync.
5. Set file filters (e.g., only .pdf and .docx files).
6. Choose a sync schedule: manual, hourly, daily, or weekly.
7. Click Save.

OmniBots downloads, indexes, and embeds documents from the source according to the schedule. Only changed or new files are processed on subsequent syncs.

Testing Connections

Use the Test Connection button on any storage integration to verify that credentials are valid and the target location is accessible. The test performs a lightweight read operation and reports success or failure with details.

Next Steps

• Set up CCaaS platforms for live agent handoff
• Learn about Knowledge Bases to use your connected documents