SharePoint, OneDrive, Confluence, Google Drive
Which permissions does my integration have?
Integrations use either API keys or OAuth 2.0 to access external tools. If you’re redirected to another tool’s login, you’re using OAuth authentication. All OAuth integrations inherit your existing permissions from the connected tool. This means you’ll only find files you already have access to in that tool. Example: User A saves a document in SharePoint without sharing it. User B authenticates through Langdock and searches for that file, but can’t find it because User A hasn’t granted access. Once User A shares the file, User B will be able to find it through Langdock. You can learn how integration scopes and action availability work in Manage Action-Level Scopes.Can I use OneDrive, SharePoint, Confluence and Google Drive to find information?
Add individual files to chat or the Agent Knowledge section when you want to analyze specific documents. For larger collections from SharePoint, Google Drive, OneDrive, or Confluence Cloud, use Folder Sync to attach an entire folder to an Agent or Project. Confluence Cloud Folder Sync imports pages from named folders, not page attachments. Use Company Knowledge to search across connected company sources.Is all content of the integration being imported into Langdock?
No. For individual integration files, Langdock uses each platform’s search API to find files by keyword or name and imports a file only after you select it. Folder Sync imports the content from the folder you select so it can update the Agent or Project knowledge source.How often is my content updated when using integrations?
When searching for individual files, we query the external tool in real time, so you see new files immediately. Folder Sync checks the selected folder daily and also supports manual refresh. Standalone integration files in Agent knowledge are checked daily for changes. An Agent editor can refresh an eligible integration file manually.General
I receive an error when using my integration
If an action fails, check these common fixes: Input parameters Some requests need specific IDs or formatted queries. If the parameter description doesn’t provide enough detail, add this information to your agent instructions or specify it in your chat prompt. OAuth connection Actions require a valid OAuth connection. Add one by requesting a specific action for that integration in chat, or connect directly via the integration menu.- Reconnect the integration if the connection expired or was revoked.
- Check that the connected account has the scopes the action needs.
- Langdock retries eligible OAuth requests automatically after refreshing the token.
- MCP connections refresh tokens silently when the server supports refresh tokens.
FAQ
What should I check before escalating an integration issue?
What should I check before escalating an integration issue?
Check the connection, user permissions, OAuth scopes, enabled actions, provider-side access, and whether the same action works for another user or resource. Include the affected integration, user, action, and error message when contacting support.