Connecting Integrations

Doti connects with your most important workplace tools to make all your organizational knowledge searchable, secure, and actionable — in real time.

Admins can connect once per system at the org level, define data boundaries through collections, and control which users or agents can access each integration.

How It Works

Doti uses a global connection mechanism — meaning once an admin connects a system (e.g., Google Drive, Confluence, Jira), it becomes accessible across the organization based on permissions and agent setup.

To maximize security and data control, Doti allows you to define Collections — logical groupings of data pulled from a specific integration.

Examples of Collections:
- A specific Google Drive folder
- A single Jira project
- A Confluence space used by Engineering

These collections are used to scope what data is available to each agent, team, or API flow.

Sync Frequency Notice

Doti syncs data from connected integrations every few hours. The exact sync cycle may vary per integration, depending on:

  • API rate limits imposed by the source system

  • Integration type (e.g., Slack, Drive, Jira)

  • Volume of data

For most systems, new or updated content will be available in Doti shortly after ingestion - without requiring manual refresh.

⚠️ Reconnecting an Integration?

If you need to reconnect an existing integration, do not delete the connection.

Instead:

  1. Open the integration’s configuration modal

  2. Click the “Previous” button until you reach the first step

  3. Click “Connect” to re-trigger the OAuth flow or base authentication

This ensures your existing collections, permissions, and agent mappings remain intact.

🗑️ Warning: Deleting an Integration

Deleting an integration will:

  • Permanently remove its connection credentials

  • Erase all data ingested from that integration

  • Unlink all associated collections, agents, and teams

This action is irreversible. Only proceed if you're certain the integration is no longer needed.

Slack

Authentication Type - OAuth2

User permissions required for installation - Slack Workspace Admin

Permissions & Scopes - Read & Write

App_mentions:read,
Channels:history,
Channels:join,
Channels:read,
Chat:write,
Commands,
Files:read,
Groups:history,
Groups:read,
Im:history,
Im:read,
Im:write,
Mpim:history,
Mpim:read,
Reactions:write,
Team:read,
users:read,
users:read.email,
Chat:write.customize

Collection - Channel

Default Historical Data Timeframe - 2 years

Real-time Search - Not supported

Searchable Data - Messages, threads and Metadata from Public & Private channels.

Setup

  1. In the Doti Platform, navigate to the integrations page.

  2. Click on the 'Connect' button on the Slack integration card.

  3. In the modal that appears, click the "Add to Slack" button.

  1. You will then be redirected to the Slack App authorization page. Click the "Allow" button to authorize Doti for your Slack workspace.

  1. Once approved by a Slack Workspace Administrator, Doti will immediately be added to your Slack Workspace.

  2. To start fetching data from channels, invite Doti to these channels and then type in "/doti sync" (This action will not be seen by others in the channel).

Confluence

Authentication Type - OAuth2

User permissions required for installation - Atlassian Organization Admin & Browse Users & Groups Permission

Permissions & Scopes - READ ONLY

readonly:content.attachment:confluence,
read:confluence-groups,
read:confluence-user,
read:confluence-content.permission,
search:confluence,
read:confluence-content.summary,
read:confluence-content.all,
read:confluence-props,
read:confluence-space.summary,

Collection - Space (Recursive), Folder

Default Historical Data Timeframe - 2 years

Real-time Search - Not supported

Searchable Data - Pages, Page comments and Metadata

Setup

  1. In the Doti Platform, navigate to the integrations page.

  2. Click on the 'Connect' button on the Confluence integration card.

  3. In the modal that appears, click the 'Continue' button to initiate the OAuth authentication flow.

  4. You will then be redirected to the Atlassian authorization page. Click the "Accept" button to authorize Doti for the Atlassian Organization.

  5. ** Ensure that the user authorizing the integration with Confluence has access to all pages and spaces that are intended for ingestion

  1. Once approved, you will be redirected back to the Doti Platform to choose the spaces and folders to connect to Doti.

  2. Type the Space/Folder name in the dropdown; select all necessary Spaces & Folders, then click 'Connect' to complete the process.

Troubleshooting: Enforce Permissions at Source Error

If the connecting user for Jira & Confluence has admin permissions but still receives an error when toggling “Enforce permissions at source”, it may be due to missing global permissions.

Make Sure the User Has the Browse Users & Groups Permission

This permission is required to look up users and groups and comes from the Global permission Browse users and groups in Atlassian.

To assign this permission:

  1. Go to ⚙ Settings > System

  2. On the left-hand menu, select Global permissions

  3. Scroll to the bottom of the permissions page

  4. Under Grant "Browse users and groups", select a group that includes the affected user

  5. Click Add

Once this permission is granted, the error should be resolved.

Note: Doti will recursively fetch all data within each selected folder, including files contained in any sub-folders.

Confluence Data Center

Authentication Type - Token

User permissions required for installation - Atlassian Organization Admin

Permissions & Scopes - READ ONLY

read:space:confluence,
readonly:content.attachment:confluence,
read:confluence-groups,
read:confluence-user,
read:confluence-content.permission,
search:confluence,
read:confluence-content.summary,
read:confluence-content.all,
read:confluence-props,
read:confluence-space.summary,

Collection - Spaces, Nested Pages

Default Historical Data Timeframe - 2 years

Real-time Search - Not supported

Searchable Data - Pages, Page comments and Metadata

Setup

  1. To begin, create an PAT (Personal Access Token) for the connection.

  2. In the Doti Platform, navigate to the integrations page.

  3. Click on the 'Connect' button on the Confluence Data Center integration card.

  4. In the configuration modal, enter the following data and click "Continue":

    1. Confluence Base URL: Your Jira tenant URL.

    2. Confluence Access Token: The access token generated in Step 1.

  5. You will now be able to choose the Confluence Spaces in which you would like to connect. Type in the Space name in the dropdown; select all necessary projects, then click 'Connect' to complete the process.

Note: If your Confluence instance is behind a firewall or otherwise inaccessible from the internet, please contact us to obtain our IP addresses for enabling connectivity.

Jira

Authentication Type - OAuth2

User permissions required for installation - Atlassian Organization Admin & Browse Users & Groups Permission

Permissions & Scopes - READ ONLY

jira-user (view),
jira-work (view)

Collection - Projects

Default Historical Data Timeframe - 2 years

Real-time Search - Supported

Searchable Data - Tickets, Ticket comments ,Ticket Metadata

Setup

  1. In the Doti Platform, navigate to the integrations page.

  2. Click on the 'Connect' button on the Jira integration card.

  3. In the modal that appears, click the 'Continue' button to initiate the OAuth authentication flow.

  4. You will then be redirected to the Atlassian authorization page. Click the "Accept" button to authorize Doti for the Atlassian Organization.

  1. Once approved, you will be redirected back to the Doti Platform to choose the projects to sync with.

  2. Type the project name in the dropdown; select all necessary projects, then click 'Connect' to complete the process.

Troubleshooting: Enforce Permissions at Source Error

If the connecting user for Jira & Confluence has admin permissions but still receives an error when toggling “Enforce permissions at source”, it may be due to missing global permissions.

Make Sure the User Has the Browse Users & Groups Permission

This permission is required to look up users and groups and comes from the Global permission Browse users and groups in Atlassian.

To assign this permission:

  1. Go to ⚙ Settings > System

  2. On the left-hand menu, select Global permissions

  3. Scroll to the bottom of the permissions page

  4. Under Grant "Browse users and groups", select a group that includes the affected user

  5. Click Add

Once this permission is granted, the error should be resolved.

Jira Data Center

Authentication Type - Token

User permissions required for installation - Atlassian Organization Admin

Permissions & Scopes - READ ONLY

jira-user (view),
jira-work (view)

Collection - Projects

Default Historical Data Timeframe - 2 years

Real-time Search - Supported

Searchable Data - Tickets, Ticket comments ,Ticket Metadata

Setup

  1. To begin, create an PAT (Personal Access Token) for the connection.

  1. In the Doti Platform, navigate to the integrations page.

  1. Click on the 'Connect' button on the Jira Data Center integration card.

  1. In the configuration modal, enter the following data and click "Continue":

    1. Jira Base URL: Your Jira tenant URL.

    2. Jira Access Token: The access token generated in Step 1.

  1. You will now be able to choose the Jira Projects in which you would like to connect. Type in the Project name in the dropdown; select all necessary projects, then click 'Connect' to complete the process.

Note: If your Jira instance is behind a firewall or otherwise inaccessible from the internet, please contact us to obtain our IP addresses for enabling connectivity.

Salesforce

Authentication Type - Token

User permissions required for installation - Salesforce Admin

Permissions & Scopes - READ ONLY

Collection - Cases, Accounts

Default Historical Data Timeframe - 2 years

Real-time Search - Supported (Dynamic SOQL & SOSL)

Searchable Data - All standard objects & custom objects

Setup

  1. (Optional): Create a dedicated Salesforce user for the Doti integration. Limit its access to only the necessary objects and fields, with read-only permissions.

  2. Using the dedicated Salesforce user, generate a security token within your Salesforce settings - security token.

  3. In the Doti Platform, navigate to the integrations page.

  1. Click on the 'Connect' button on the Salesforce integration card.

  1. In the configuration modal, enter the following Salesforce credentials for the dedicated user:

    1. Salesforce Base URL: Your Salesforce tenant URL (e.g., doti.lightning.force.com).

    2. Salesforce Username: The username of the dedicated user.

    3. Salesforce Password: The password of the dedicated user.

    4. Salesforce Security Token: The security token generated in Step 2.

  1. Click "Connect". Doti will begin fetching data from Salesforce.

Note: To optimize Salesforce results for your organization by utilizing a custom field map, contact the Doti team for further information.

Notion

Authentication Type - Token

User permissions required for installation - Notion Admin

Permissions & Scopes - READ ONLY

Read Content,
Read Comments,
Read user information including email addresses

Collection - Folders

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Pages, Tables

Setup

  1. In the Notion platform, navigate to the integrations page.

  2. Create a new integration, name it "Doti AI" (or anything that suites your standards) and choose "Internal".

  1. Once created, make sure to modify this integration's capabilities to R/O only, as can be seen in the image below and hit the "Save" button.

  1. Head to the integration's "Access" tab, and click the 'Select Pages' button.

  1. Select all of the relevant workspaces and top-level pages that are relevant and accept.

  2. In the Doti Platform, navigate to the integrations page.

  3. Click on the 'Connect' button on the Notion integration card.

  4. In the configuration modal, enter the following Notion information:

    1. Notion API Token: The security token generated in previous steps.

    2. Entities: Choose any of the workspace or top-level entities you have connected the token to.

  1. Click "Connect". Doti will begin fetching data from Notion.

Note: Doti will recursively fetch all data within each selected top-level entity, including files contained in any sub-folders.

Document360

Authentication Type - Token

User permissions required for installation - Document360 Admin

Permissions & Scopes - READ ONLY

Collection -

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Pages

Setup

  1. To begin, create an API token for the connection, ensuring that 'GET' is the only permitted method.

  2. In the Doti Platform, navigate to the integrations page.

  3. Click on the 'Connect' button on the Document360 integration card.

  1. In the configuration modal, enter the following Document360 information:

    1. Endpoint: Your Document360 tenant URL (ex, doti-ai.document360.io).

    2. API Token: The API token generated in Step 1.

  1. Click "Connect". Doti will begin fetching data from Document360.

Google Drive

Authentication Type - OAuth/Domain-Wide Delegation with Service Account

User permissions required for installation - Google Workspace Admin

Permissions & Scopes - READ ONLY

https://www.googleapis.com/auth/admin.directory.group.member.readonly,
https://www.googleapis.com/auth/cloudplatformorganizations.readonly,
https://www.googleapis.com/auth/admin.directory.customer.readonly,
https://www.googleapis.com/auth/admin.directory.group.readonly,
https://www.googleapis.com/auth/drive.readonly,
https://www.googleapis.com/auth/drive.metadata.readonly

Collection - Folders

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Documents (Google Doc & Microsoft Doc), Presentations (Google Slides & Microsoft PowerPoints), Sheets (Google Sheets & Microsoft Excel) and PDF files

Setup

  1. In the Doti Platform, navigate to the integrations page.

  2. Click on the 'Connect' button on the Google Drive integration card.

  3. In the configuration modal, click 'Continue' to initiate the authentication process.

  4. Copy the Client ID created for you and the scopes that appear in the configuration modal.

  5. In a second tab, open the Google Workspace admin console and navigate to the domain-wide delegation configuration screen.

  6. Click the 'Add new' button and fill in the following parameters in the configuration modal:

    1. Client ID: The Client ID copied from the Doti platform in Step 4.

    2. Oauth Scopes: The Oauth scopes copied from the Doti platform in Step 4 (Comma separated).

  1. Once you've completed the setup, return to the configuration modal in the Doti Platform and click "Continue." If everything has been configured correctly, you will be automatically redirected to the next step: selecting the folders you wish to ingest (The Google authorization process may take up to 60 seconds).

  2. Select the desirable folders and click "Connect". Doti will begin fetching data from Google Drive.

  3. To preserve Google Drive's security and privacy controls, a Doti admin may only connect folders that are directly shared with them, or any Shared Drives within the organization (regardless of their specific permissions within those drives).

If you're unable to proceed past Step 6 and encounter an error on the Doti platform, please verify the following:

  1. ✅ Google Drive API is enabled in your organization

  2. ✅ Google Slides API is enabled in your organization

  3. ✅ Your Google Workspace domain matches the company domain used on the Doti platform

⚠️ All three are required for successful integration. If issues persist, contact your Google Workspace admin or reach out to the Doti team for support.

Note: Doti will recursively fetch all data within each selected folder, including files contained in any sub-folders.

Zendesk

Authentication Type - Token

User permissions required for installation - Zendesk Admin

Permissions & Scopes - READ ONLY

Collection - Ticket Groups, Articles

Index Controls - Ticket groups, Ticket fields & values

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Tickets, Articles

Setup

  1. To begin, enable & create a Zendesk API token for this connection and copy the created token.

  2. In the Doti Platform, navigate to the integrations page.

  1. Click on the 'Connect' button on the Zendesk integration card.

  2. In the configuration modal, enter the following Zendesk information:

    1. Subdomain: Your Zendesk tenant subdomain (ex, doti in doti.zendesk.com).

    2. Email: The email address of the user used to create an API Token in Step 1.

    3. API Token: The API token generated in Step 1.

  3. Once done, you will be prompted for the ticket groups you would like to ingest to Doti. Choose all of the desired ticket groups and click the 'Continue' button.

  4. Finally, for each ticket group, you can select specific tickets to ingest by applying filters based on field values.

  1. Click "Connect". Doti will begin fetching data from Zendesk.

Github

Authentication Type - Github APP (Oauth)

User permissions required for installation - Github Admin

Permissions & Scopes - READ ONLY

Administration: Read Only,
Commit Statuses: Read Only,
Contents: Read Only,
Custom Properties: Read Only,
Discussions: Read Only,
Issues: Read Only,
Metadata: Read Only,
Pull Requests: Read Only,
Custom Repository Roles: Read Only,
Members: Read Only,
Email Addresses: Read Only

Collection - Repository

Index Controls - File types (JS, TS, TSX, Python, JSON, YAML etc..)

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Repositories, Code

Setup

  1. In the Doti Platform, navigate to the integrations page.

  2. Click on the 'Connect' button on the Github integration card.

  1. In the configuration modal, enter the following Github information and click 'Continue':

    1. Organization Name: Your Github organization name (ex, doti-ai)

  1. You will then be redirected to the Github App authorization page. You may choose to limit Doti's access to specific repositories or grant it access to all during the installation. Click the "Accept" button to authorize Doti for the Github Organization.

  1. Once approved, you will be redirected back to the Doti Platform to choose the repositories to connect to Doti.

  2. Type the repositories names in the dropdown; select all necessary repositories, then click 'Continue' to continue the process.

  3. Select the file types you wish Doti to include while ingesting data from the repositories. Leaving this field empty will block Doti from ingesting any data.

  1. Click "Connect". Doti will begin fetching data from Github.

Gitlab

Authentication Type - Token

User permissions required for installation - Gitlab Admin

Permissions & Scopes - READ ONLY

read_api,
read_user,
read_repository

Collection - Repository

Index Controls - File types (JS, TS, TSX, Python, JSON, YAML etc..)

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Repositories, Code

Setup

  1. To begin, create a Personal Access Token for this connection and copy the created token. Make sure to configure the follow Read-Only scopes only - read_api, read_user, read_repository

  2. In the Doti Platform, navigate to the integrations page.

  3. Click on the 'Connect' button on the Gitlab integration card.

  1. In the configuration modal, enter the following Gitlab information and click 'Continue':

    1. Gitlab Host: Your Gitlab tenant URL (ex, doti-ai.gitlab.io)

    2. Token: The PAT generated in Step 1.

  1. Type the repositories names in the dropdown; select all necessary repositories, then click 'Continue' to continue the process.

  1. Select the file types you wish Doti to include while ingesting data from the repositories. Leaving this field empty will block Doti from ingesting any data.

  1. Click "Connect". Doti will begin fetching data from Gitlab.

Gong

Authentication Type - OAuth

User permissions required for installation - Gong Admin

Permissions & Scopes - READ ONLY

api:calls:read:transcript,
api:provisioning:read,
api:workspaces:read,
api:calls:read:extensive,
api:settings:scorecards:read,
api:calls:read:basic,
api:calls:read:media-url,
api:crm:integration:read,
api:library:read,
api:data-privacy:read,
api:users:read,
api:logs:read,
api:settings:trackers:read,
api:permission-profile:read,
api:flows:read,
api:crm-calls:manual-association:read

Collection - Gong Calls

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Call Title, Pariticipants, Time & Duration, Brief Summary, Action Items, Highlights, Trackers, Outline Items and Call Outcome

Setup

  1. In the Doti Platform, navigate to the integrations page.

  1. Click on the 'Connect' button on the Gong integration card.

  1. In the configuration modal, enter the following Gong information and click 'Continue':

    1. Organization: Your Gong organization name(ex, doti.ai)

  1. You will then be redirected to the Gong authorization page. Click the "Accept" button to authorize Doti for the Gong Organization.

  1. Click "Connect". Doti will begin fetching data from Gong.

How to Find Your Gong Domain Name

To complete the Gong integration, you need your Gong organization domain name.

To locate this:

  1. Log in to your Gong Admin Center.

  2. Navigate to Settings > General Settings.

  3. Under the Company Settings section, you will see your primary domain listed.

    • This is the value you should use as your Organization when configuring the Gong integration in Doti.

Note: Private Gong calls are not ingested into Doti.

Datadog

Authentication Type - Token

User permissions required for installation - Datadog Admin

Permissions & Scopes - READ ONLY

teams_read,
user_access_read,
apm_service_catalog_read,
apm_api_catalog_read,
apm_read

Collection - Datadog Teams, Datadog Services

Default Historical Data Timeframe - 2 years

Real-time Search - Not Supported

Searchable Data - Teams & Memebers, Services, Service Dependencies

Setup

  1. To begin, in the Datadog Platform, navigate to the Application keys page.

  2. Create a new key and name it in a desirable manner.

  1. Once created, edit the application's scopes, assigning the following read-only scopes and hit finish - 

    teams_read, user_access_read, apm_service_catalog_read

  1. In the Doti Platform, navigate to the integrations page.

  1. Click on the 'Connect' button on the Datadog integration card.

  1. In the configuration modal, enter the following Gong information and click 'Continue':

    1. Region: Your Datadog workspace region.

    2. Application ID: The Application Key ID generated in Step 2.

    3. API Key: The API Key generated in Step 2.

  1. Click "Connect". Doti will begin fetching data from Datadog.

Web Crawler

Authentication Type - N/A

User permissions required for installation - N/A

Permissions & Scopes - N/A

Collection - Website

Default Historical Data Timeframe - All time

Real-time Search - Not Supported

Searchable Data - Website content & pages

Setup

  1. Reach out to the Doti team with the base URL of the site you'd like to crawl.

  2. Our team will initiate the crawl and create a new Collection for you.

  3. Once processed, it will appear under your Integrations and can be assigned to any Agent.

PreviousHybridNextDots - Knowledge Nuggets

Last updated

Was this helpful?