docs/guides/data_source/data_source_configuration.md
The Confluence data source is used to synchronize spaces, pages, and subpages maintained by a team in Confluence to a RAGFlow knowledge base. After configuration, users can query product documents, project descriptions, R&D standards, and other content in the knowledge base.
Permission requirements: Read permissions for Confluence spaces or pages. If attachments or subpages need to be synchronized, read permissions for the corresponding content are also required.
Account version requirements: Personal spaces or free team spaces in Confluence Cloud can be used. If enterprise spaces, Server, or Data Center content is synchronized, access permissions for the corresponding organization space are required.
Configuration parameters:
The Notion data source is used to synchronize Notion pages and database content to a RAGFlow knowledge base. After configuration, documents, project records, and knowledge cards organized by the team in Notion can be used for retrieval and Q&A.
Permission requirements: The Notion integration must be granted access to the target page or database.
Account version requirements: Both Notion personal pages and team spaces can be used. As long as the target page or database has been shared with the Notion integration, it can be synchronized to RAGFlow.
Configuration parameters:
The Google Drive data source is used to synchronize files or folders in Google Drive to a RAGFlow knowledge base. After configuration, team cloud documents can be used directly for knowledge base retrieval and Q&A.
Permission requirements: The Google account or OAuth authorization must have read permissions for the target files, shared folders, or cloud drives.
Account version requirements: Folders that a user is authorized to access in a personal Google Drive can be used. To synchronize organization shared folders or multi-user cloud drives, a Google Workspace administrator or an account with the corresponding authorization is usually required.
Configuration parameters:
The OneDrive data source is used to synchronize files in OneDrive or OneDrive for Business to a RAGFlow knowledge base. After configuration, personal or department cloud files can be queried in a unified way.
Permission requirements: The Microsoft account or application authorization must have read permissions for the target folders and files.
Account version requirements: This is usually configured for Microsoft 365 or Entra ID organization accounts. Personal OneDrive is generally not suitable for the current connection method based on tenant, client ID, and client secret.
Configuration parameters:
The SharePoint data source is used to synchronize SharePoint site document libraries to a RAGFlow knowledge base. After configuration, enterprise policies, department materials, and project files can be managed and queried in a unified way.
Permission requirements: The Microsoft account or application authorization must have read permissions for the target site, document library, and files.
Account version requirements: A Microsoft 365 or SharePoint organization site and Entra ID application authorization are required. Personal accounts are not applicable.
Configuration parameters:
The Box data source is used to synchronize files and folders in Box cloud drive to a RAGFlow knowledge base. After configuration, enterprise cloud drive materials and externally collaborated files can be queried in a unified way.
Permission requirements: The Box application or account must have read permissions for the target folders and files.
Account version requirements: Both personal Box folders and enterprise Box spaces can be used. Enterprise spaces require the administrator or application authorization to allow access to the target folder.
Configuration parameters:
The Dropbox data source is used to synchronize files and folders in Dropbox to a RAGFlow knowledge base. After configuration, cloud collaboration files can be used for knowledge base retrieval and Q&A.
Permission requirements: The Dropbox application or account must have read permissions for the target folders and files.
Account version requirements: Both personal Dropbox and team Dropbox can be used. Team spaces require application authorization with read permissions for the target files or folders.
Configuration parameters:
The SeaFile data source is used to synchronize account, library, or directory content in Seafile to a RAGFlow knowledge base. After configuration, private cloud drive materials and department files can be retrieved in a unified way.
Permission requirements: The SeaFile account must have read permissions for the target libraries, directories, and files.
Account version requirements: Both personal libraries and enterprise libraries can be used. When synchronizing shared libraries or specified directories, the corresponding library token or account permissions are required.
Configuration parameters:
The S3 data source is used to synchronize files in an object storage bucket to a RAGFlow knowledge base. After configuration, documents stored in the cloud or in private object storage can be uniformly included in knowledge base management.
Permission requirements: The access key, IAM role, or compatible storage account must have bucket listing and object reading permissions.
Account version requirements: An AWS S3 or S3-compatible object storage account is required. This type of data source is determined by cloud account and bucket permissions, and does not distinguish between personal and enterprise editions.
Configuration parameters:
The Google Cloud Storage data source is used to synchronize files in a GCS bucket to a RAGFlow knowledge base. After configuration, project materials, reports, and documents on Google Cloud can enter the knowledge base for team retrieval.
Permission requirements: The GCS credentials must have listing and object reading permissions for the target bucket.
Account version requirements: Google Cloud project and bucket permissions are required. They are usually configured according to cloud project permissions, and do not distinguish between personal and enterprise editions.
Configuration parameters:
The Oracle Storage data source is used to synchronize files in Oracle Cloud Object Storage to a RAGFlow knowledge base. After configuration, documents and archive materials stored on OCI can be retrieved in a unified way.
Permission requirements: The OCI credentials must have listing and object reading permissions for the target bucket.
Account version requirements: Oracle Cloud tenancy and object storage permissions are required. They are usually configured according to cloud account permissions.
Configuration parameters:
The R2 data source is used to synchronize files in a Cloudflare R2 bucket to a RAGFlow knowledge base. After configuration, public materials, business files, or historical documents stored in R2 can be queried in a unified way.
Permission requirements: The R2 access key must have listing and object reading permissions for the target bucket.
Account version requirements: A Cloudflare account and R2 bucket permissions are required. Both personal and enterprise Cloudflare accounts can be used, depending on whether they have access to the target bucket.
Configuration parameters:
The Azure Blob Storage data source is used to synchronize files in an Azure Blob container to a RAGFlow knowledge base. After configuration, materials, reports, and archive files in an Azure cloud environment can be queried in a unified way.
Permission requirements: The Azure credentials must have read permissions for the target container and blobs.
Account version requirements: An Azure storage account, connection string, or SAS authorization is required. They are usually configured according to Azure subscription and storage container permissions.
Configuration parameters:
The MySQL data source is used to synchronize table records or query results in MySQL to a RAGFlow knowledge base. After configuration, structured business data can be used for retrieval and Q&A.
Permission requirements: The database account must have SELECT permission on the target database tables. A read-only account is recommended.
Account version requirements: Both personal self-built databases and enterprise databases can be used. It is recommended to use a read-only account to connect to the target database tables.
Configuration parameters:
The PostgreSQL data source is used to synchronize table records or query results in PostgreSQL to a RAGFlow knowledge base. After configuration, structured business data can be used for retrieval and Q&A.
Permission requirements: The database account must have SELECT permission on the target database tables. A read-only account is recommended.
Account version requirements: Both personal self-built databases and enterprise databases can be used. It is recommended to use a read-only account to connect to the target database tables.
Configuration parameters: The configuration fields are the same as those for MySQL, including name, host, port, database, username, password, SQL query, content column, metadata column, ID column, timestamp column, and sync deleted files.
The BigQuery data source is used to synchronize table records or query results in BigQuery to a RAGFlow knowledge base. After configuration, structured data and analysis results in Google Cloud can be retrieved and used for Q&A.
Permission requirements: The Google Cloud account or service account must have query and read permissions for the target BigQuery project, dataset, and table.
Account version requirements: Google Cloud project and BigQuery permissions are required. They are configured according to cloud project permissions.
Configuration parameters:
The GitHub data source is used to synchronize issues and pull requests in GitHub repositories to a RAGFlow knowledge base. After configuration, open-source project materials, development discussions, and issue handling records can be queried.
Permission requirements: The GitHub token must have read permissions for the target repositories, issues, and pull requests.
Account version requirements: Both personal repositories and organization repositories can be used. Organization private repositories require the token to have read permissions for the corresponding repositories, issues, and pull requests.
Configuration parameters:
The GitLab data source is used to synchronize GitLab repositories, issues, merge requests, and code files to a RAGFlow knowledge base. After configuration, project development records and code-related knowledge can be queried in a unified way.
Permission requirements: The GitLab access token must have read permissions for the target project, issues, merge requests, and repository files.
Account version requirements: Both personal projects and group projects can be used. Private group projects require the token to have the corresponding read permissions.
Configuration parameters:
The Bitbucket data source is used to synchronize Bitbucket repository content, issues, and pull requests to a RAGFlow knowledge base. After configuration, team code collaboration records can be queried.
Permission requirements: The Bitbucket account, app password, or token must have read permissions for the target workspace and repository.
Account version requirements: Both personal workspaces and team workspaces can be used. Private repositories require authorization with read permissions.
Configuration parameters:
The Azure DevOps data source is used to synchronize Azure Repos source files and pull requests to a RAGFlow knowledge base. After configuration, repository content and code review history can be queried.
Permission requirements: The personal access token (PAT) must have the Code (Read) scope for the target organization.
Account version requirements: Both Azure DevOps Services (dev.azure.com) and self-hosted Azure DevOps Server are supported. For a self-hosted server, provide the full collection URL as the organization, for example https://tfs.contoso.com/DefaultCollection. The URL must use HTTPS, because the personal access token is sent in the Authorization header.
Configuration parameters:
project/repo to disambiguate repositories that share a name across projects.Pull request descriptions are re-fetched individually when they reach the 400 character limit the list endpoint truncates at, so long descriptions are indexed in full. Completed and abandoned pull requests are filtered by their close date; active ones are always re-indexed, because Azure DevOps exposes no dependable "last updated" timestamp for them.
Build output and vendored directories such as node_modules, bin, obj, dist, and vendor are skipped, along with binary files and files larger than 1 MB.
The Jira data source is used to synchronize issues, comments, and project records in Jira to a RAGFlow knowledge base. After configuration, project tasks, requirements, bugs, and handling records can be queried.
Permission requirements: The Jira account or API token must have read permissions for the target project and issues.
Account version requirements: Jira Cloud and Jira Server or Data Center can be used. Enterprise projects require the account to have access permissions for the corresponding project.
Configuration parameters:
The Asana data source is used to synchronize tasks, projects, and comments in Asana to a RAGFlow knowledge base. After configuration, team task records and project progress can be queried.
Permission requirements: The Asana account or access token must have read permissions for the target workspace, project, and tasks.
Account version requirements: Both personal projects and organization workspaces can be used. Organization workspaces require the account to have access permissions for the target project.
Configuration parameters:
The Gmail data source is used to synchronize Gmail email content to a RAGFlow knowledge base. After configuration, customer service emails, business correspondence, and historical communication records can be queried and reused.
Permission requirements: Google OAuth authorization must have read permissions for the target mailbox emails.
Account version requirements: The current interface includes a primary administrator email and OAuth JSON, which is more suitable for Google Workspace administrators or organization mailbox synchronization. Ordinary personal Gmail is recommended only after the actual authorization flow supports it.
Configuration parameters:
The Outlook data source is used to synchronize Outlook mailbox emails to a RAGFlow knowledge base. After configuration, business emails and communication records in Microsoft 365 can be queried.
Permission requirements: The Microsoft account or application authorization must have read permissions for the target mailbox emails.
Account version requirements: Microsoft 365 or Outlook organization accounts are recommended. Personal Outlook depends on whether the authorization flow and API permissions are available.
Configuration parameters:
The IMAP data source is used to synchronize email content in mail services that support the IMAP protocol to a RAGFlow knowledge base. After configuration, mailboxes that are not covered by standard email connectors can also be included in knowledge base retrieval.
Permission requirements: The mailbox account must enable IMAP and have read permissions for the target folder.
Account version requirements: Personal mailboxes and enterprise mailboxes can both be used, as long as the mail service supports IMAP login and the account has the required permissions.
Configuration parameters:
The Microsoft Teams data source is used to synchronize Teams channel messages and related collaboration records to a RAGFlow knowledge base. After configuration, team discussion content can be retrieved and reused.
Permission requirements: The Microsoft account or application authorization must have read permissions for the target team, channel, and messages.
Account version requirements: Microsoft 365 organization accounts and Teams permissions are required. Personal accounts are generally not applicable.
Configuration parameters:
The Slack data source is used to synchronize Slack channel messages and collaboration content to a RAGFlow knowledge base. After configuration, team communication records can be retrieved and queried.
Permission requirements: The Slack application or token must have read permissions for the target workspace and channels.
Account version requirements: Both personal workspaces and enterprise workspaces can be used. Private channels require the application to be invited or granted the corresponding permissions.
Configuration parameters:
The Discord data source is used to synchronize Discord server and channel messages to a RAGFlow knowledge base. After configuration, community communication records can be queried and analyzed.
Permission requirements: The Discord bot must have permission to read the target servers and channels.
Account version requirements: Personal servers and community servers can both be used, as long as the bot has been added to the target server and granted message reading permissions.
Configuration parameters:
The Dingtalk AI Table data source is used to synchronize records in Dingtalk AI Table to a RAGFlow knowledge base. After configuration, online table records, business ledgers, and collaborative data can be queried.
Permission requirements: The Dingtalk account or application authorization must have read permissions for the target AI Table.
Account version requirements: Dingtalk organization accounts and AI Table permissions are required. Whether it can be synchronized depends on the organization permissions and application authorization.
Configuration parameters:
The Zendesk data source is used to synchronize Zendesk tickets, comments, and knowledge base content to a RAGFlow knowledge base. After configuration, customer service records and support knowledge can be queried in a unified way.
Permission requirements: The Zendesk account, API token, or application authorization must have read permissions for the target tickets and knowledge base content.
Account version requirements: Zendesk team or enterprise accounts can be used. The account must have access permissions for the target tickets or help center content.
Configuration parameters:
The Moodle data source is used to synchronize course content, forums, resources, and learning records in Moodle to a RAGFlow knowledge base. After configuration, course materials and teaching records can be queried.
Permission requirements: The Moodle account or token must have read permissions for the target courses, activities, and resources.
Account version requirements: Self-built Moodle and organization Moodle platforms can be used. The account must have access permissions for the target courses.
Configuration parameters:
The REST API data source is used to synchronize data returned by custom business APIs to a RAGFlow knowledge base. After configuration, records in internal systems or third-party systems can enter the knowledge base according to the API structure.
Permission requirements: The API credentials must have permission to call the target API, and the data returned by the API must be readable.
Account version requirements: Personal or enterprise custom systems can both be used, provided that the target API is accessible and provides a stable data structure and authentication method.
Configuration parameters:
The Xquik data source searches public X posts and syncs each matching post into a RAGFlow knowledge base. Use it to retrieve posts by keyword, hashtag, author, language, or another supported X search operator.
Permission requirements: Create an Xquik API key. The key needs access to the Search Tweets API.
Usage requirements: Each returned post uses 1 Xquik credit. The page size and maximum page count bound each sync. Xquik is an independent third-party service.
Configuration parameters:
from:username.RAGFlow sends each incremental sync window to Xquik as inclusive sinceTime and exclusive untilTime bounds. Cursor pagination continues until no page remains or the configured maximum is reached.
The RSS data source is used to subscribe public websites, blogs, announcements, or product updates to a RAGFlow knowledge base. After configuration, the knowledge base can continuously obtain new content from the subscription source, making it convenient for users to view and ask questions in a unified way.
Permission requirements: The subscription source must be accessible. If the subscription source is protected, make sure the access address or credentials have read permissions.
Account version requirements: Public subscription sources can usually be used directly. If the RSS address is protected, provide an account or access address that can access the subscription source.
Configuration parameters: