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.
Can I use OneDrive, SharePoint, Confluence and Google Drive to find information?
Currently, you need to add individual files to chat or assistant knowledge to work with your integrations. This works well when you want to analyze specific documents.For broader search across all your tools (similar to web search), the technical complexity is higher because we need to download and vectorize entire folder structures rather than using the limited keyword-based search APIs these platforms provide. This is among our highest priorities and something many customers request, so we’re working on a solution as quickly as possible.
When searching for files, we query the external tool in real-time, so you’ll see new files immediately.Files already imported into assistant knowledge sync once daily. You can also trigger manual synchronization anytime.
If an action fails, check these common fixes:Input parametersSome requests need specific IDs or formatted queries. If the parameter description doesn’t provide enough detail, add this information to your assistant instructions or specify it in your chat prompt.OAuth connectionActions require a valid OAuth connection. Add one by requesting a specific action for that integration in chat, or connect directly via the integration menu.
