Connectors

Connectors pull data from external tools into Knowledge Bases. A connector can be assigned to multiple Knowledge Bases.

Visibility

Each connector has a visibility setting that determines which users can retrieve its data when an agent calls query_knowledge_sources. Connectors and Knowledge Bases are filtered by visibility throughout the UI: users only see sources they have access to, and only those can be assigned to agents and MCP Gateways.

Users with the knowledgeSource:admin role can view and query every connector regardless of visibility.

Enterprise only. Team-scoped visibility and auto-synced ACLs require an enterprise license. Contact sales@archestra.ai for licensing information.

Jira

Sync issues and discussions from Atlassian Jira.

Indexed: issue descriptions, comments, and metadata from Jira Cloud or Server.

Authentication: an Atlassian account email and an API token.

Confluence

Sync wiki pages from Atlassian Confluence.

Indexed: pages from Confluence Cloud or Server.

Authentication: the same Atlassian email and API token used for Jira.

GitHub

Sync issues and pull request discussions from GitHub.

Indexed: issues, pull requests, and their comments from GitHub.com or GitHub Enterprise Server.

Authentication: a personal access token.

GitLab

Sync issues and merge request discussions from GitLab.

Indexed: issues, merge requests, and their comments from GitLab.com or self-hosted GitLab instances. System-generated notes (assignment changes, label updates, etc.) are filtered out.

Authentication: a personal access token.

Asana

Sync tasks and discussions from Asana projects.

Indexed: tasks and their user comments from selected Asana projects.

Authentication: a personal access token.

ServiceNow

Sync ITSM records from a ServiceNow instance.

Indexed: incidents, change requests, change tasks, problems, and business applications. Incidents are enabled by default; the rest are opt-in.

Authentication: basic auth (username + password) or an OAuth bearer token. For basic auth, put the username in the Email field and the password in the API Token field. For OAuth, leave Email empty and put the bearer token in the API Token field.

Notion

Sync pages and databases from a Notion workspace.

Indexed: pages from a Notion workspace.

Authentication: a Notion integration token (starts with secret_). Create an internal integration in your workspace and share the relevant pages or databases with it.

SharePoint

Sync documents and site pages from SharePoint Online.

Indexed: documents and site pages from SharePoint Online. Supported document types include .txt, .md, .csv, .json, .xml, .html, .htm, .yaml, .log, .docx, .pdf, and .pptx. When a multimodal embedding model is configured, image files (.jpg, .jpeg, .png, .gif, .webp) up to 4 MB are also indexed.

Authentication: an Azure AD app registration with client credentials (OAuth2). The app needs the Sites.Read.All application permission on Microsoft Graph, with admin consent granted.

Where to find each value:

• Tenant ID — Microsoft Entra ID > App registrations > > Overview > Directory (tenant) ID.
• Client ID — Application (client) ID on the same page.
• Client Secret — the secret Value from Certificates & secrets (not the secret ID).
• Site URL — the exact SharePoint site web URL, not the display name.

OneDrive

Ingests files from OneDrive for Business (personal drives of specified users) via the Microsoft Graph API. Text is extracted from .txt, .md, .csv, .json, .xml, .html, .htm, .yaml, .log files, as well as .docx, .pdf, and .pptx documents. When a multimodal embedding model is configured (e.g., gemini-embedding-2-preview), image files (.jpg, .jpeg, .png, .gif, .webp) up to 4 MB are also ingested and embedded directly.

Authentication uses an Azure AD app registration with client credentials (OAuth2). The app registration requires the Files.Read.All application permission on Microsoft Graph, and admin consent must be granted.

To configure the connector:

• Tenant ID comes from Microsoft Entra ID > App registrations > > Overview > Directory (tenant) ID
• Client ID comes from Application (client) ID on the same page
• Client Secret is the secret Value from Certificates & secrets, not the secret ID
• User IDs should be user principal names (UPNs, e.g. user@company.com) or Azure AD object IDs for the users whose drives you want to sync

Incremental sync uses the lastModifiedDateTime field to fetch only items modified since the last run.

Known Limitations

• Only OneDrive for Business (work/school accounts) is supported. Consumer OneDrive is not supported.
• Syncs the personal drive (/drive) of each specified user; shared libraries are not traversed.

Google Drive

Sync files from Google Drive (My Drive and Shared Drives).

Indexed: files from My Drive and Shared Drives. Supported document types include .txt, .md, .csv, .json, .xml, .html, .htm, .yaml, .log, .docx, .pdf, and .pptx. Google Workspace files (Docs, Sheets, Slides) are also indexed. When a multimodal embedding model is configured, image files (.jpg, .jpeg, .png, .gif, .webp) are indexed too. Files larger than 10 MB are skipped.

Authentication: either a service account JSON key (recommended) or a short-lived OAuth2 access token with the drive.readonly scope. For a service account: create one in the Google Cloud Console, enable the Google Drive API, download the JSON key, and share the target folders or drives with the service account email. Paste the full JSON contents (or the bearer token) into the Service Account Key / OAuth Token field.

Dropbox

Sync text and source files from a Dropbox account or team folder.

Indexed: text-based files from a Dropbox account or team folder. Supported extensions: .md, .txt, .ts, .js, .py, .json, .yaml, .yml, .html, .css, .csv, .xml, .sh, .toml, .ini, .conf.

Authentication: a Dropbox access token. Generate one from the Dropbox App Console by creating an app with the files.content.read permission.

Linear

Sync issues, projects, and cycles from a Linear workspace.

Indexed: issues by default, with optional projects (and recent updates) and cycles.

Authentication: a Linear personal API key. Create one under Settings > Security & access > Personal API keys in Linear, then paste it into the connector's Personal Access Token field.

Outline

Sync published documents from an Outline workspace.

Indexed: published documents. Both Outline cloud (https://app.getoutline.com) and self-hosted instances are supported.

Authentication: an Outline API key. Create one under Settings > API & Apps in your Outline workspace. Only documents the key has access to are synced.

Salesforce

Sync CRM records from a Salesforce org.

Indexed: CRM records from a Salesforce org. By default the connector syncs Account, Contact, Opportunity, and Case. You can list other object API names in the Objects field, or use Advanced Object Config JSON to pick exact fields and associations per object.

Authentication: a Salesforce username, password, and security token. The password field must contain the password directly concatenated with the security token (no separator). To get the token: log in to Salesforce, click your User Avatar > Settings, then go to My Personal Information > Reset My Security Token and check your email.

Example advanced config:

{
  "Lead": {
    "fields": ["FirstName", "LastName", "Company", "Email"],
    "associations": { "Account": ["Name"] }
  },
  "Case": {
    "fields": ["Subject", "Status", "Priority", "Description"]
  }
}

Id, Name, and LastModifiedDate are always included automatically.

Managing Connectors

Connectors can be managed from either the Connectors page or a Knowledge Base's detail page. After creation you can:

• Toggle enabled/disabled -- suspends or resumes the cron schedule
• Trigger sync -- runs an immediate sync outside the schedule
• View runs -- see sync history with status, document counts, and errors

Adding New Connector Types

See Adding Knowledge Connectors for a developer guide on implementing new connector types.