Langdock Integrations

An integration connects Langdock to a system outside the platform: SharePoint, Google Drive, Confluence, Salesforce, Jira and dozens more. It lets the chat, an agent or a workflow read data from that system or trigger actions in it. Without integrations, Langdock is a sealed-off chat. With integrations, it becomes an AI layer that knows your company.

1.1 The Three Integration Types

Langdock distinguishes three ways of connecting an external system. Most users only need type 1, some additionally type 2, and type 3 is for developers.

Type	What it is	Who builds it
Native integrations	Connections prebuilt and maintained by Langdock. 72 of them (as of October 2026), and the number keeps growing. Examples: SharePoint, Google Drive, Salesforce, Jira, Confluence.	Langdock
MCP servers	Connections via the Model Context Protocol standard. For tools that have no native integration. Examples: Hugging Face, Canva, Zapier, many more official servers.	Third-party providers or you
Custom integrations	Your own integrations in JavaScript, assembled with the Langdock builder. For internal APIs or special cases.	You, with the Langdock builder

This guide focuses on type 1 (native integrations), explains type 2 in chapter 7 and shows the entry point to type 3 in 7.3.

1.2 What an Integration Can Do

Native integrations typically serve two functions:

• Knowledge: making content from the third-party system available in the chat or to an agent. Example: searching Confluence pages, citing Google Drive files, querying SharePoint lists.
• Action: triggering something in the third-party system. Example: sending a Slack message, creating a Jira ticket, updating a Salesforce deal, creating an Outlook appointment.

Some integrations can do both, some only one. The exact list is in the official Integration Directory and in chapter 5.

1.3 Connection · the technical backbone

In Langdock terminology, the concrete link to a third-party system is called a Connection. A connection consists of three things:

• The integration type (e.g. “Google Drive”).
• The credentials (OAuth token, API key, service account, depending on the integration).
• An owner. That is the user who created the connection. The connection always runs on behalf of this person, with their permissions in the third-party system.

This owner logic matters for understanding the rest: if your Salesforce connection is read-only, an agent using your connection can only read as well. The integration inherits your permissions.

1.4 Who Can See a Connection

Connections can be private or shared. Which options are available depends on the auth method:

Auth method	Sharing possible?
OAuth (login via browser flow)	Not directly. Every person has to create their own OAuth connection. It can only be passed on indirectly: through an agent with a preselected connection (see below).
API key	Yes. Can be shared with the whole workspace, a user group, individual people or a workspace API key.
Service Account	Yes. Same as API key. Only Vertex AI Vector Search uses this method.
None (open MCP)	Yes. If the server needs no auth, the connection can be shared freely.

The workaround for OAuth: If you want to give a whole group access without handing out credentials, build an agent and set a preselected connection there. Everyone allowed to use the agent then works through that single connection without ever seeing it. Classic example: a team calendar agent that creates appointments in the shared calendar. Anyone who can edit an agent can also preselect a connection. For OAuth connections this person additionally needs the “Share OAuth connections” permission, otherwise only the non-OAuth connections are selectable.

Multiple connections to the same tool: If you have two accounts attached to the same system, you can set a default connection per integration. Langdock then always falls back to that one instead of asking on every call.

Who is allowed to share: A workspace admin shares non-OAuth connections under Integrations → select the integration → action menu of the connection → Share connection. The connection card itself does not open any sharing settings. With OAuth, nobody shares directly, not even an admin.

1.5 What Integrations Are Not

To keep the picture clear, here is what an integration is not:

• An integration is not an agent. An agent is a specialised assistant. It can use integrations but is not one itself.
• An integration is not a workflow. A workflow is a multi-step automation. It can employ integrations but is not one itself.
• An integration is not an upload. A PDF you drag into the chat is a file upload. If you want to search SharePoint files live, you need the SharePoint integration.

Before going into setup details, it is worth understanding how Langdock authenticates with the third-party system. Four methods are in use. Which one applies is decided by the integration, not by you.

2.1 OAuth · the default

OAuth is the standard method for all integrations whose third-party system supports single sign-on. That is practically every major SaaS tool.

How it works: You click “Connect” in Langdock. A pop-up opens the login page of the third-party system (e.g. Microsoft, Google, Slack). You log in and confirm which permissions Langdock may receive. The pop-up closes and the connection is there.

Who uses it: Microsoft 365 (all apps), Google Workspace (all apps), Slack, Confluence, Notion, Jira, Linear, Salesforce, HubSpot, Zendesk, GitHub, Calendly, Airtable and many more.

Advantage: Secure, the token expires and can be revoked. No secret keys to store.

Disadvantage: Every person has to connect themselves. The connection cannot be shared.

2.2 API Key

Some tools, above all data and specialist tools, have no OAuth. Instead you generate an API key (also called a “token” or “personal access token”) in the third-party system and paste it into Langdock.

Who uses it: monday.com, Databricks, Metabase, Tableau, Pinecone, Milvus, Qdrant, DeepL, ElevenLabs, Stripe, Personio, Ashby, Statista, OpenRegister, AWS Kendra, Azure AI Search, UiPath Automation Hub and more.

Two routes to the same tool: Snowflake and Looker give you a choice. Both appear twice in the directory: once as an OAuth variant (Snowflake, Looker) and once as a key variant (Snowflake PAT, Looker (API Key)) with an identical feature set. If you want to avoid the OAuth effort, take the key variant.

Advantage: The connection can be shared. One person creates it, the workspace uses it.

Disadvantage: Whoever has the key has the permissions. Treat it like a password: no Slack, no email, no tracker. Only into the Langdock field.

2.3 Service Account · the Vertex AI special case

A service account is a Google Cloud identity in the form of a JSON file. Only a single Langdock integration uses it: Vertex AI Vector Search. For this integration you upload the JSON file.

For everything else, you do not need to deal with service accounts in Langdock.

2.4 None · open MCP servers

Some MCP servers need no auth at all. They deliver public data or perform stateless operations. For these you only enter the server URL in Langdock. Nothing more.

2.5 Bring Your Own OAuth · BYOO

For four integrations (ServiceNow, Shopify Admin, Snowflake and UiPath) BYOO is mandatory. Instead of the standard Langdock OAuth app, your admin registers a dedicated OAuth app in the third-party system and enters its client ID and secret in Langdock.

The reason: these third-party systems do not accept generic multi-tenant OAuth apps or do not allow shared redirect URLs. For Shopify Admin there is simply no OAuth app managed by Langdock, and UiPath registers OAuth apps exclusively within a single Automation Cloud organisation. Details and steps in 3.4.

For all other integrations, BYOO is optional. It still makes sense if you want your own name and logo on the consent screen, if your tenant policies need to apply, or if the API rate limits should run against your own contract.

2.6 Who Does the Setup · Admin vs. End User

Task	Who does it
Enable an integration in the workspace (allow list)	Admin
Grant Microsoft tenant consent	Microsoft admin in the Entra portal
Register a BYOO app and enter it in Langdock	Admin
Create an OAuth connection for yourself	End user
Share an API key connection with the workspace	End user (owner) or Admin
Use a connection in the chat or in an agent	End user

This chapter is for workspace admins. End users can skip it and go straight to chapter 4. If the setup here is not done cleanly, you will later hear the classic “it doesn't work for me”.

3.1 Allow list · which integrations users may create at all

Default: all native integrations are enabled. If you want to restrict them for compliance or hygiene reasons, you can do so per workspace, per user group or per individual user.

Where: Workspace settings → Integrations → Manage. There the admin sees the full list of integrations and can set Allow or Deny per entry.

Two strategies:

• Open by default, deny per tool: Quick to set up, gives users flexibility. Suitable for smaller workspaces without strict governance.
• Closed by default, allow per tool: Stricter. Every new integration has to be actively enabled. Suitable for regulated industries.

3.2 Action-level scopes · which permissions Langdock requests

Every action needs specific OAuth permissions from the third-party system, for example Calendars.ReadWrite for calendar operations. Through scopes at action level you define which capabilities of an integration are available in the workspace at all. Three modes are available:

• Langdock Client (default): Langdock automatically requests exactly the scopes matching the enabled actions, plus the basic scopes for identification such as openid and email. The right choice for most workspaces.
• Own OAuth client with sync on: Behaves like the default but uses your own OAuth app. The scope request adapts automatically when actions change.
• Own OAuth client with fixed scopes: You define and maintain the requested scopes by hand. Useful if your security team reviews permissions independently of action changes and needs stability.

Where: Workspace settings → Integrations → select the integration → Scopes and Action Access. The Scope view tab shows the permissions grouped, the Action view tab shows each action individually. A Missing scope badge marks actions that still lack a permission.

The setting “New actions enabled by default” decides what happens with new actions: if it is on, Langdock enables new actions automatically as long as their scopes are already covered. If it is off, new actions stay inactive until you have reviewed them.

Action Access · who may use an individual action

In the same area, Action view tab, every action has a toggle “Available to all users”. Default is on, meaning everyone in the workspace may use the action. If you switch it off, a Share button appears through which you grant access to individual users or whole groups.

• Access to an individual action requires that the person may use the integration at all. The allow list from 3.1 applies first.
• Actions with the NATIVE badge cannot be switched off, they carry core platform functions. The NATIVE button at the top right hides them so you only see what can actually be changed.
• Typical use: read actions for everyone, write actions (send email, close ticket, update record) only for a defined group.

3.3 Microsoft tenant consent · the most common stumbling block

Seven Microsoft integrations need admin consent in Entra (formerly Azure AD) before the first user can connect:

• Microsoft SharePoint
• Microsoft OneDrive
• Microsoft Teams
• Microsoft Outlook (Mail)
• Microsoft Outlook (Calendar)
• Microsoft Excel
• Microsoft Planner

Procedure:

1. A first test user from your workspace tries to connect one of these integrations in Langdock. The attempt fails with the message “Need admin approval”. That is normal: Microsoft has thereby registered the service principal in your tenant.
2. The Microsoft admin goes to the Entra Admin Center → Enterprise Applications → searches for Langdock.
3. Clicks the application → under Security on Permissions → Grant admin consent for <Tenant>.
4. Confirms the requested Microsoft Graph scopes in the pop-up.
5. From now on the OAuth connection works for all users in the tenant.

The official guide with screenshots from the Entra portal is at docs.langdock.com/en/admin/manage-integrations/integration-setup-guides/microsoft.

Sensitivity Label Policy · Purview labels as a block

New in the admin docs: with the Sensitivity Label Policy you decide per Microsoft tenant which Microsoft Purview sensitivity labels Langdock may process. SharePoint, OneDrive, Outlook Email, Microsoft Teams and Microsoft Excel then withhold files and emails with a blocked label before anything reaches the AI. The feature appears once Langdock has enabled it for your workspace.

• Where: Settings → Integrations → Microsoft Purview (or via Data Protection & Sensitivity Labels on SharePoint, OneDrive, Outlook Email, Teams, Excel). The Purview connection needs SensitivityLabel.Read, User.Read, openid and offline_access.
• How: choose a connection, Load labels, set the Allowed toggle per label, Save Policy. On first load everything is allowed, and files without a label always stay allowed.
• New labels: a label you create in Purview stays allowed in Langdock until you click Load labels and Save Policy again. So reload and save after every label change in Purview.
• Not covered: Outlook Calendar, OneNote, Planner, To Do, Power BI, custom integrations, MCP servers and locally uploaded files. Drafting, sending, replying and forwarding in Outlook are not checked.

For blocked files, users see the notice »Blocked by Purview«. The check costs one to three extra Microsoft Graph requests per file or email, so searches and Folder Sync get somewhat slower.

3.4 BYOO · Bring Your Own OAuth

For some integrations you have to register your own OAuth app in the third-party system instead of using the generic Langdock app. The docs currently list four tools as mandatory:

• ServiceNow: Mandatory. Create an application in the ServiceNow OAuth Application Registry, fetch the redirect URL from Langdock, enter client ID + secret in Langdock. Every connecting user additionally needs the oauth_user role in ServiceNow (plus itil if incident actions are used).
• Shopify Admin: Mandatory, there is no OAuth app managed by Langdock. A workspace admin creates an app in the Shopify Dev Dashboard, enters the redirect URL and the Admin API scopes from the Langdock dialog there and copies client ID and secret back into Langdock. You connect per store via its domain. Important: the connection works with app-level permissions, i.e. the app's Admin API scopes, and not with the personal Shopify role of the person who set it up.
• Snowflake: Mandatory. Create a security integration in Snowflake via SQL command, configure the URLs, enter the keys in Langdock.
• UiPath: Mandatory. UiPath only ever registers external OAuth apps within an Automation Cloud organisation, so Langdock cannot provide a central client here. Your UiPath admin creates a Confidential application under Admin → External applications → OAuth apps, enters the scopes from the Langdock dialog exclusively under User Scope(s) (not under Application Scope(s)) and stores the redirect URL. Application ID and App Secret then go into Langdock as client ID and secret. Optionally you can set the UiPath cloud URL there as the workspace default, so your people no longer have to type it when connecting.

For most other integrations, an own OAuth client is optional: you can choose between the generic Langdock app and your own, for example if your security team demands a dedicated app.

Multiple clients per integration: You are not limited to a single OAuth client. One client acts as the default for the whole workspace, additional clients can be assigned to individual user groups. That way corporate IT can use a different OAuth client than a subsidiary, even though both use the same integration.

What you gain: Your name and logo on the consent screen, your tenant policies on access, your own rate limits instead of the shared ones.

Where in Langdock: Workspace settings → Integrations → Custom OAuth.

If you deactivate a client, existing connections stay attached to it, only new connections go elsewhere. If you delete it, existing tokens keep running until they expire, after which all affected users have to reauthorise.

Step-by-step guides: docs.langdock.com/en/admin/manage-integrations/bring-your-own-oauth.

3.5 Default Tool Stack · which tools Langdock suggests

Most companies work either with Microsoft 365 or with Google Workspace. So that Langdock does not suggest both worlds on an equal footing, you can set a Default Tool Stack. It decides which integrations new members are offered first and what Langdock falls back on for recommendations.

Where: Workspace settings → Integrations → Default tool stack. The options are Microsoft, Google or None. Langdock saves changes immediately, there is no confirmation step.

Deviate per category: Under Advanced category defaults the suite preset can be overridden for individual categories: email, calendar, file storage, messaging, meetings, project management, CRM, support, knowledge base, code repository and business intelligence. Typical case: Microsoft as the suite, but Slack for messaging and Jira for project management.

Automatic detection: If a suite reaches three or more connections and thereby leads the other, Langdock selects it on its own until you manually set something else.

Reset: Individual categories via Use suite default, the suite itself via None.

3.6 Subscribe to the admin newsletter

Langdock has a separate admin newsletter that announces integration changes in advance. Subscribing to it spares you nasty surprises when scopes change or an integration is refactored.

Subscribe: Send an empty email to admin-integrations-updates+subscribe@langdock.com. The confirmation comes back automatically.

Once your admin has enabled the integrations in the allow list (and, if necessary, Microsoft consent + BYOO are done), it is your turn. Creating a connection usually takes under two minutes.

4.1 The 5-step standard flow

The procedure is the same for all native integrations:

1. Open settings. Click your profile picture at the bottom left → Settings → Integrations.
2. Choose the integration. Find the desired integration in the list or via search. Click Connect.
3. Authenticate. Depending on the integration: with OAuth, a browser pop-up of the third-party system opens, you log in and confirm the permissions. With an API key, you enter the token in the Langdock form.
4. Name the connection (optional). The default name is the integration type. If you have several connections to the same tool (e.g. two Salesforce orgs), give them meaningful names: “Salesforce Prod”, “Salesforce Sandbox”.
5. Use it. Type @<Integration> in the chat, or select the connection in the agent under Knowledge or Tools.

4.2 Testing the connection

After creating it, the simplest test is an @ trigger in the chat. Examples:

• Drive: @Google Drive show me the ten most recently modified documents
• Confluence: @Confluence find the page “Onboarding 2026”
• Slack: @Slack list the channels of my workspace

If the integration returns content: the connection works. If an error appears: check 4.4.

4.3 Reauthorising when the token has expired

OAuth tokens have a limited lifetime. Typically 60 to 90 days, depending on the third-party system. When your token expires, the integration enters the reauth state.

Since May 2026, Langdock shows you this directly in the chat: if you want to use the integration and the token has expired, an inline notice “Re-authorize” with a link appears. One click, a new browser pop-up, a new login confirmation, done. The running conversation is preserved.

Alternatively, you can see all your connections at any time under Settings → Integrations. Expired ones appear with a red marker and a reauth button.

In workflows: Since 18 September 2026, the Workflow Monitor flags invalid connections before a run fails on them. You can reconnect them right there and then rerun failed runs, up to 20 at once, either from the point of failure or from the beginning.

Four triggers for a reauth: the token has expired, it was revoked in the third-party system, the connection lacks a scope for a new action, or your admin removed the custom OAuth client the connection was attached to (see 3.4).

4.4 What to do about errors

Four error classes, from frequent to rare:

“Need admin approval”

Occurs with Microsoft integrations. Means: your Microsoft admin has not yet granted tenant consent in Entra. Send your IT admin the link from 3.3 or directly to the official Microsoft admin approval guide.

“Permission denied” or “Insufficient scope”

You have connected, but in the third-party system you lack the role for what you are requesting. Example: in Jira you want to create tickets but only have read permissions in the project. Solution: have the permissions raised in the third-party system, then disconnect the connection once and reconnect so that the new scopes come along.

“Connection not shareable”

You tried to share an OAuth connection with colleagues. That does not work, by design. Every person creates their own OAuth connection. Only API key, service account and None connections are shareable (see 1.4).

Integration does not appear in the list at all

Then your admin has deactivated it in the allow list. Ask your internal IT service desk or the Langdock admin to enable it.

There are currently 72 native integrations (as of October 2026). Describing all of them in depth would go far beyond this guide. We proceed in three tiers:

• Tier 1: The 13 integrations most frequently requested by mid-sized companies in the DACH region. With setup steps, example prompts and pitfalls.
• Tier 2: around 30 further integrations with standard OAuth or standard API key. A table with a short description and a link to the official docs.
• Tier 3: The remaining specialist integrations (vector DBs, audio, translation etc.). Collective overview.

The complete official list is in the Integration Directory. That is also where you always find the up-to-date state, the number keeps growing.

5.1 Microsoft family

All Microsoft integrations run on OAuth via Microsoft Graph. Seven of them need tenant consent in Entra once per workspace (see 3.3). Without this step, nothing works for them at all.

SharePoint

Searches and reads documents, pages and list entries from your SharePoint sites. Allows actions in the chat such as creating files or new list items.

• Auth: OAuth, tenant consent required.
• Setup: Settings → Integrations → SharePoint → Connect → Microsoft login. Afterwards you automatically see only the sites you have access to in the original.
• In the chat: @SharePoint find the site “Sales 2026” and list the pages, @SharePoint load the file “Pricing.pdf” from the site “Sales”
• Pitfall: If you cannot see a SharePoint site in the browser, the integration cannot see it either. That is not Langdock, that is your SharePoint permission.
• Since May 2026: If you paste a SharePoint page link (.aspx) directly into the chat, Langdock resolves the page automatically and reads the content without you having to search for it separately.
• Folder Sync: SharePoint is one of the four sources supported by Folder Sync (see 6.2).

OneDrive

Personal Microsoft storage. Search, browse, download and upload.

• Auth: OAuth, tenant consent required.
• Setup: Settings → Integrations → OneDrive → Connect.
• In the chat: @OneDrive show me all files I touched last week, @OneDrive save this answer as a Markdown file in “/Notes/Langdock”
• Pitfall: OneDrive is frequently confused with SharePoint. OneDrive is personal, SharePoint is shared. For team documents, use SharePoint.
• Folder Sync: OneDrive has newly been added as a source for Folder Sync (see 6.2).

Microsoft Teams

Search channels and direct messages, send messages, check meetings.

• Auth: OAuth, tenant consent required.
• Setup: Settings → Integrations → Microsoft Teams → Connect.
• In the chat: @Teams what was discussed in the channel “Marketing” this week, @Teams send a message to Lisa that the meeting has been moved to 3 pm
• Pitfall: Sending to private channels and 1:1 chats requires stricter scopes than reading. On your first attempt to write, you may be asked to reauth.

Outlook (Mail)

Search, read, reply to and send emails. Organise folders.

• Auth: OAuth, tenant consent required.
• Setup: Settings → Integrations → Outlook Email → Connect.
• In the chat: @Outlook find all emails from Klaus in the last 4 weeks, @Outlook draft a reply to Marie's latest email and save it as a draft
• Pitfall: Sending on behalf of others (shared mailbox) needs explicit SendAs permissions in Exchange. Without them, you can only send from your own address.

Outlook (Calendar)

Read, create and move appointments, check availability.

• Auth: OAuth, tenant consent required.
• Setup: Settings → Integrations → Outlook Calendar → Connect.
• In the chat: @Outlook Calendar create a 30-minute meeting with Sarah next Wednesday at 10:30, title “Q2 planning”, @Outlook Calendar when am I still free this week between 2 and 5 pm
• Pitfall: Recurring appointments are sometimes only changed for the single instance on updates. For changes to the whole series, ask for that explicitly.

Excel

Read and write spreadsheets, create charts. Compared to file management via OneDrive: this is about the content of the cells.

• Auth: OAuth, tenant consent required.
• Setup: Settings → Integrations → Excel → Connect.
• In the chat: @Excel open the file “SalesForecast.xlsx” and give me the totals per region
• Pitfall: With very large sheets (>10k rows), the live query is slow. For such datasets, better use data analysis directly in Langdock with an uploaded file.

5.2 Google Workspace family

All Google integrations run on OAuth. Unlike Microsoft, no workspace-wide admin consent is needed. Every person connects their own Google account.

Google Drive

Search, browse, download and upload files. Cite content.

• Auth: OAuth.
• Setup: Settings → Integrations → Google Drive → Connect → Google login → scope confirmation.
• In the chat: @Drive show me all Docs I edited this week, @Drive quote me the key points from the briefing “Pitch ACME”
• Pitfall: Shared drives (formerly team drives) require your account to be a member. Files that are only shared via link may not be found by the integration's search.
• Folder Sync: Drive is one of the four sources for Folder Sync (see 6.2).

Gmail

Search, read, reply to and send emails. Manage labels.

• Auth: OAuth.
• Setup: Settings → Integrations → Gmail → Connect.
• In the chat: @Gmail find emails from “notifications@stripe.com” with status “failed”, @Gmail send a reminder to yesterday's participants that the slides are in Drive
• Pitfall: Gmail searches are context-free. If you are referring to a specific thread, copy the subject line into your instruction.

Google Calendar

Read and create appointments, check availability. With or without a Meet link.

• Auth: OAuth.
• Setup: Settings → Integrations → Google Calendar → Connect.
• In the chat: @Calendar when do I have two consecutive hours free next week, @Calendar create a meeting with lisa@example.com on Thursday at 3 pm, including a Meet link
• Pitfall: “Availability” only considers your main calendar. If you keep separate calendars (e.g. a focus time calendar), you have to mention them explicitly.

5.3 Knowledge & Collaboration

Confluence

Search, read, create new pages, update pages. Cloud or Data Center alike.

• Auth: OAuth.
• Setup: Settings → Integrations → Confluence → Connect → Atlassian login → choose the right site.
• In the chat: @Confluence find the page “Engineering Onboarding” and summarise the to-dos, @Confluence create a new page in the space “Marketing” titled “Q3 campaign”, content: this
• Pitfall: If you have several Atlassian orgs, make sure you connect the right site when connecting. Switching is only possible by disconnecting the connection and creating it anew.
• Self-hosted: If you run Confluence in your own data centre, do not use this integration but the separate Confluence Data Center. Same feature set (search, read pages and comments, create and update pages), also OAuth.
• Folder Sync: Confluence Cloud has newly been added as a source for Folder Sync (see 6.2). The Data Center variant is left out, and the sync does not pull spreadsheets from Confluence.
• Documentation gap: Confluence has no dedicated setup page in the official Langdock docs. For tricky cases, contact support@langdock.com directly.

Slack

Search channels and DMs, send messages, summarise threads.

• Auth: OAuth.
• Setup: Settings → Integrations → Slack → Connect → choose the Slack workspace → confirm permissions.
• In the chat: @Slack summarise the thread in #marketing-launch from the last two days, @Slack send a message to #ops that the deployment is running
• Pitfall: You only see private channels and DMs if your Slack account is a member of those channels. When connecting, you are asked whether Slack should invite the bot “Langdock” to your channels. That is only needed for active posting, not for reading with your user token.

5.4 CRM, Support & ITSM

Salesforce

Search leads, accounts, opportunities, contacts. Create and update records. Query reports.

• Auth: OAuth.
• Setup: Settings → Integrations → Salesforce → Connect → Salesforce login. For sandbox orgs, explicitly choose Sandbox.
• In the chat: @Salesforce show me all open opportunities in the DACH pipeline with a volume over 100k, @Salesforce update the contact Marie Müller with the new mobile number 0151...
• Pitfall: The connection inherits your Salesforce profile permissions. If you only have read on an object, the integration can only read as well. Sandbox users often forget to choose the sandbox variant when connecting and end up in prod.

HubSpot

Contacts, companies, deals, tickets. Read, search, create, update.

• Auth: OAuth.
• Setup: Settings → Integrations → HubSpot → Connect → HubSpot account login → confirm scopes.
• In the chat: @HubSpot find deals with stage “Negotiation” and a close date this month, @HubSpot set the new industry “FinTech” on the company “ACME GmbH”
• Pitfall: Custom properties are fully retrievable but have to be named exactly. If you look under Properties in the HubSpot setup and know the internal property name, it is much easier.

ServiceNow

Incidents, change requests, knowledge articles. Read, search, create, update.

• Auth: OAuth, Bring Your Own OAuth mandatory (see 3.4).
• Setup: The admin creates the OAuth app in ServiceNow (System OAuth → Application Registry) and enters client ID + secret in Langdock under Custom OAuth. Only then can the first user connect. On user login, the oauth_user role must additionally be set, and for incident actions also itil.
• In the chat: @ServiceNow show me all open P1 incidents, @ServiceNow create an incident: printer on the 3rd floor is not printing, priority Medium
• Pitfall: If the OAuth setup step is skipped, every connection attempt fails. This is the integration with the most frequent initial setup confusion in the DACH region.

5.5 PM & Issue Tracking

Jira

Search, read, create and comment on issues, change status. Cloud variant fully supported.

• Auth: OAuth.
• Setup: Settings → Integrations → Jira → Connect → Atlassian login → choose the right site.
• In the chat: @Jira find all bugs in the project “CRM” with priority High that were opened last week, @Jira create a new story ticket in the project “Onboarding” titled “Users can reset their password”, description: ...
• Pitfall: Custom workflows with special status values must be named exactly. Example: for “set status to Review”, “Review” has to be spelled exactly like that in the workflow, otherwise Jira rejects the transition.
• Self-hosted: For Jira Data Center in your own data centre there is a separate integration called Jira Data Center. It can search issues, read status and comments, and create or update tickets.

5.6 Data & Analytics

Snowflake

Run SQL queries on your Snowflake warehouses, explore schemas and tables. Read and visualise results directly in the chat.

• Auth: Two separate entries in the directory. Snowflake runs on OAuth, where BYOO is mandatory. Snowflake PAT uses a personal access token instead and needs no OAuth setup, with an identical feature set including Cortex Search.
• Setup (OAuth): The admin creates a security integration in Snowflake via SQL (TYPE = OAUTH, OAUTH_CLIENT = CUSTOM), enters the redirect URL from Langdock and copies client ID, secret and authorization URL back into Langdock. Specify warehouse and default database.
• Setup (PAT): Generate a token in Snowflake, enter it in Langdock under Snowflake PAT, done. The faster route for most teams.
• Network: If your Snowflake account uses IP allowlisting or network policies, the static Langdock IP has to be allowed. Otherwise the connection fails without a meaningful error.
• In the chat: @Snowflake list the ten highest-revenue customers of Q1 2026, @Snowflake show me the schema of the table “sales_fact”
• Pitfall: If you do not set a default warehouse, every query returns an error. The role also has to have explicit read permissions on the schemas being queried.

5.7 Tier 2 · standard OAuth or API key

These integrations follow the same standard patterns and need no special instructions. For questions, go straight to the official docs.

Integration	What for	Auth
Linear	Issues and projects, modern PM tool. Live search and creation via chat.	OAuth
Asana	Tasks, projects, teams. Actions such as creating tickets, status changes.	OAuth
monday.com	Boards, items, updates. Read and write.	API key
GitHub	Repos, issues, PRs, commits. Read and write access depending on scope.	OAuth
Bitbucket	Search repositories, review pull requests and diffs, browse and create branches.	OAuth
Zendesk	Tickets, users, knowledge base. Automate support workflows.	OAuth
Pipedrive	Find deals, leads, persons and organisations, read activities and notes, create and update entries.	OAuth
Microsoft Dynamics 365	Look up and update records in any table, qualify leads, close opportunities as won or lost.	OAuth
Notion	Pages, databases, content. Read and write.	OAuth
Miro	Read boards and frames.	OAuth
Personio	HR data: employees, absences, contracts.	API key
Stripe	Payments, customers, invoices, subscriptions.	API key
BigQuery	SQL queries on the Google Cloud data warehouse.	OAuth
Databricks	Workspaces, notebooks, queries. Unity Catalog required.	API key (PAT)
Looker / Looker (API Key)	Explore dashboards, run queries, browse data models. Two directory entries with the same feature set.	OAuth or API key
Tableau	Workbooks, views, data sources.	API key
Metabase	Dashboards and questions. From v1.47.	API key
Microsoft Fabric	Query business data from data warehouses, SQL databases, lakehouses and mirrored databases. Runs via an API for GraphQL item in Fabric, in which your Fabric admin defines which objects and operations are visible at all. Reading and writing are separate actions, a query cannot trigger a mutation, and Langdock asks for confirmation before every mutation. No tenant consent needed.	OAuth (SSO or stored credentials)
Shopify Admin	Look up and change a store's products, inventory, locations, orders, fulfillments, discounts and files. You connect per store via its domain.	OAuth, BYOO mandatory (see 3.4)
Power BI	Query datasets, retrieve reports. Tenant consent required (part of MS).	OAuth
Azure DevOps	New in the admin docs (not yet listed in the integration directory): create, search and comment on work items, sprints and team capacity, wikis, repositories, branches, multi-file commits, and creating and merging pull requests. Uses its own Azure DevOps scopes (vso.*) instead of Microsoft Graph.	OAuth
Azure Resource Manager	Also new in the admin docs: search subscriptions, resource groups and resources in Azure, retrieve activity logs and change history. Read-only, access via the user_impersonation scope, and visibility follows the user’s Azure RBAC role.	OAuth
Zoom	Create meetings, search recordings. BYOO for dedicated customers.	OAuth
Calendly	Event types, bookings, availability.	OAuth
Airtable	Read and write bases and records.	OAuth
Ashby	Recruiting functions: candidates, stages, interviews.	API key
Google Docs / Sheets / Slides / Tasks / Meet / Analytics	Specific Google Workspace apps alongside Drive, Gmail, Calendar.	OAuth
Microsoft OneNote / Planner / To Do / Entra	Further MS 365 apps alongside SharePoint, OneDrive, Teams, Outlook, Excel. Entra provides user lookups, groups and directory info and now also manages app registrations (client secrets, redirect URIs, app roles, permission grants), which needs the matching write scopes with admin consent.	OAuth
Microsoft Viva Engage	Browse communities, search and read messages, post replies, manage members.	OAuth
Confluence Data Center / Jira Data Center	The self-hosted variants of the two Atlassian tools. Separate directory entries, same functions as the cloud versions.	OAuth
Wrike	Tasks, projects, time tracking.	OAuth
UiPath	UiPath Orchestrator: trigger and queue automation jobs, monitor runs and job statistics, browse processes, queues and folders.	OAuth, BYOO mandatory (see 3.4)
UiPath Automation Hub	Search automation ideas, browse categories and applications, retrieve pipeline phase and cost-benefit details.	API key

5.8 Tier 3 · specialist integrations

For these tools we skip dedicated step-by-step instructions because they are either very narrowly tailored or connected by developer teams. The official docs are sufficient here.

Integration	What for
DeepL	Translations on demand. API key.
ElevenLabs	Speech synthesis.
Luma	Generative video.
Statista	Market data and statistics.
OpenRegister	German commercial register.
Pylon	Modern customer support.
Google Maps	Places, geocoding, routes, distance matrix. Requires your own Google Cloud project with billing.
Pinecone, Milvus, Qdrant	Vector databases for RAG use cases.
Vertex AI Vector Search	Google Cloud vector search. The only integration with service account auth.
AWS Kendra, Azure AI Search	Enterprise search backends of the major hyperscalers.

If you are looking for a tool that is not listed here: check the official Integration Directory or the MCP Directory. If it is not there either, the answer is usually a custom integration or your own MCP server.

Once integrations are set up, there are three different ways to use their content. The choice determines whether you see live data or snapshots, whether your agent always has current knowledge or a fixed state, and how much configuration effort is involved.

6.1 Three routes, one comparison

Mechanism	What it does	When to use
Folder Sync	Loads a folder from SharePoint, Google Drive, OneDrive or Confluence Cloud into an agent's knowledge once a day. Snapshot, not live.	When an agent should always access a clearly defined body of knowledge and the data does not change hourly.
Company Knowledge	Live search across all your connected sources at once (Drive, OneDrive, SharePoint, Confluence, Mail, Slack, Teams, Calendar, Linear).	When the chat or agent should search flexibly across everything you can reach, without a fixed source selection.
@-Actions in the chat	You type @Slack or @Outlook and trigger a concrete action (send a message, create an appointment).	When you want to do something, not find something. Actions, not search.

6.2 Folder Sync · snapshot knowledge for agents

Folder Sync is the simplest way to give an agent a clearly delimited set of knowledge. Example: you build an agent for “customer communication” that should know your tone-of-voice manual, email templates and customer briefings. These live in a SharePoint folder. Folder Sync pulls them in.

Where: Agent → Knowledge → Attach → Folder Sync.

Limits you need to know

• Sources: SharePoint, Google Drive, OneDrive and Confluence Cloud. The respective integration has to be enabled in the workspace and connected by you. Not included: Notion, Box, Dropbox and all Data Center variants.
• Maximum 5 folders per agent or project.
• Maximum 200 files per folder in cloud workspaces, in dedicated deployments up to 1,000.
• Purview labels: if a Sensitivity Label Policy is active (see 3.3), files with a blocked label are skipped during sync and previously synced copies are removed.
• Refresh: automatically once a day. Manually via Agent → Knowledge → ... → Refresh.
• Initial sync: can take up to an hour, depending on folder size. The daily updates afterwards run much faster.

Which file formats go in

• Supported: text documents (PDF, DOC, DOCX, TXT, MD), presentations (PPT, PPTX), SharePoint site pages (ASPX), spreadsheets from SharePoint, Google Drive and OneDrive (XLS, XLSX, CSV, TSV, Google Sheets) and other text-based files.
• Not supported: images (PNG, JPG, GIF) and other non-text media.

How search works: For text documents, Folder Sync uses semantic search and pulls in the matching passages. Spreadsheets work differently: they are evaluated via a dedicated reading tool, not via semantic search. Calculating and filtering in large sheets is more reliable that way than via text snippets.

Permissions still apply: Even with a synced folder, Langdock checks at the time of use whether the accessing person may see the file in the source system. A sync therefore does not permanently bypass any permissions.

6.3 Company Knowledge · live search across all sources

Company Knowledge has been live since the end of January 2026. It searches simultaneously in all connected sources of a person and returns hits without you having to specify beforehand where to search.

Current sources: Google Drive, OneDrive, SharePoint, Confluence, Gmail, Outlook, Slack, Microsoft Teams, Google Calendar, Linear and now also Jira.

Condition: For each of the sources you need your own active connection. What you have not connected will not be found. In addition, an admin must have enabled Company Knowledge in the workspace settings in the first place.

Where: In the chat via the Company knowledge button in the input bar. On the first click, the source selection opens automatically. In the agent, the function is under Knowledge.

Selecting sources: In the selection you toggle each connected source on or off, only the active ones are searched. If you have several accounts attached to the same tool (say two Google accounts), choose the right one via Manage Connections. Langdock remembers your selection for next time. At least one source must be active.

6.4 @-Actions · actions straight from the chat

Every connected integration can be addressed in the chat via the @ trigger. Examples:

• @Slack send a message to #marketing with the campaign update
• @Outlook create an appointment with Markus next Thursday at 2 pm
• @Jira create a bug ticket in the project CRM titled “Login error with SSO”
• @Salesforce find all deals with status “Negotiation” and a volume over 50k

The model decides for itself which concrete action of the integration matches your instruction, and asks for confirmation before executing if the action writes. Since 6 July 2026, this confirmation dialog also shows you the action's optional fields so that you can fill them in or adjust them directly before you approve the action (e.g. a CC address on an email or a label on a ticket).

The dividing line: Reading and searching actions run without a prompt so that gathering information stays fluid. Anything that creates, changes or deletes should be confirmed, because the parameters come from the model and deserve a quick look.

Preview and Source: For fields with formatted text, such as the body of an email, the confirmation dialog has two views. Preview shows the rendered result, Source the underlying HTML or Markdown. Handy when an email looks clean in the preview but you want to check what actually goes out.

Plugins · integrations, skills and tools in one place

Since 15 September 2026, Langdock bundles integrations, skills and tools under Plugins. You add a plugin directly from the chat input, and the conversation gets access to its context and actions without you having to leave the chat to set it up.

• Plugins in the sidebar: shows the integrations connected in your workspace and the available skills. Installed integrations appear first, and categories and workspace popularity help you find the right one.
• Prompt starters: Every integration comes with example prompts, so you can quickly see what it can do.
• Skills with integrations: A skill can bring one or more integrations with it. As soon as the skill is active in the chat and the model has read its instructions, their actions become available automatically. Each person still needs their own connection. Attached integrations are preserved when a skill is exported and imported as a ZIP.
• Confirmations per agent: In the Agent Builder you decide which actions need a confirmation before they run.

6.5 Decision table

What you want	Which mechanism
Agent should always use the same body of knowledge	Folder Sync
Find “where was that briefing again” in the chat, everywhere	Company Knowledge
Send an email, create an appointment, create a ticket	@-Action
Cite up-to-date sales data from Salesforce	Live question to the Salesforce integration, not Folder Sync
Keep a 200-page knowledge base permanently in the agent	Folder Sync

6.6 Using integrations on a schedule · Scheduled Tasks

Since 18 June 2026, integrations can also be used on a schedule. With Scheduled Tasks you define a prompt that runs automatically through one of your agents and accesses the integrations attached to the agent live. That way a task always pulls fresh data at the set time without you triggering the chat manually.

• Cadence: daily, weekly or a custom rhythm. Every run starts at the set time in your local time zone.
• Live data: The task uses the same @-actions and connections as the agent. Example: summarise the open Salesforce deals every Monday at 8 am, or review the new Outlook emails from the weekend.
• Manage: In the new “Scheduled” area in the sidebar you see all tasks and their run history, and you can pause or resume them.
• Via API: Since 15 September 2026, scheduled tasks can also be created, listed, updated, paused, resumed, run and deleted through the public API.

Not everything you want to connect is available as a native Langdock integration. For these cases there is the MCP route.

7.1 What MCP is

MCP stands for Model Context Protocol. It is an open standard, originally introduced by Anthropic, through which AI platforms can talk to external tools. Instead of every vendor building its own integration for every tool, every platform talks to every MCP server over the same protocol.

For you this means: if there is no native Langdock integration but there is an MCP server, you can still connect.

7.2 Connecting an existing MCP server

Langdock maintains its own MCP directory with 79 official servers by now (as of 15 October 2026). Official means: the respective provider runs and maintains the server themselves, all run remotely over HTTP/SSE, you do not have to install anything locally. Examples of tools available as MCP but not natively:

• Canva and Figma alternatives such as Mobbin · design research and templates
• Hugging Face · model hub and datasets, usable entirely without auth
• Cloudflare Workers, Vercel, Netlify, Sentry · hosting and monitoring for developer teams
• Ramp, Spendesk, PayPal, Square · finance and expense tools
• Zapier and Pipedream · bridge to thousands of further apps
• Intercom, PagerDuty, PostHog, Amplitude · support, incidents and product analytics
• SISTRIX, Statista, Stack Overflow, Context7 · research and reference works

Three servers are currently still in beta: Pennylane (on request only, for a limited circle), Pipedrive (under construction, individual actions may still be missing) and newly Leadfeeder (identify and enrich website visitors, setup steps and tools may still change). Some servers depend on a paid plan with the provider, such as Jamie (Pro, Team or Enterprise) and TaxGraph (active subscription or trial).

New in the directory: Riecken connects DATEV (clients, accounting analyses, documents and client letters) and requires an active MCP for DATEV account with a connected DATEV system. draw.io creates diagrams and shows them as an MCP App directly in the chat, with no sign-in at all.

The auth method depends on the respective server: most use OAuth, some an API key or bearer token (e.g. GitHub via PAT), and a few public servers such as Hugging Face, DeepWiki or Microsoft Learn Docs need no login at all.

Where to connect: Settings → Integrations → MCP → Add. Enter the URL of the MCP server and, if necessary, auth (API key or OAuth according to the server description). Before saving, Langdock tests the connection and shows which tools the server offers.

Four auth variants when creating: no auth for public servers, API key with a freely selectable header format (X-API-Key, Bearer, Basic), OAuth 2.0 with PKCE and automatic discovery, and Advanced OAuth 2.0 for servers without dynamic client registration, where you enter client ID and secret by hand. Custom headers can contain fixed values or placeholders such as {{ access_token }}.

API key headers in detail: the options are X-API-Key, API-Key, X-Auth-Token, Authorization: Bearer, Authorization: Token and Authorization: Basic. For Basic you enter username:password and Langdock encodes it. Without a selection, Langdock sends the key both as X-API-Key and as a Bearer token. On dedicated deployments with user OAuth login there is also the placeholder {{ user_oauth_access_token }}, which forwards the user’s Langdock login token to the MCP server.

Sharing workspace-wide: Unlike personal OAuth connections (see 8.1), an admin has been able to share an MCP connection with the whole workspace since April 2026. That way not every person has to set up the same MCP server individually.

Langdock already ships one server: Langdock Docs is included by default in cloud workspaces. With it, the chat can search the official Langdock docs directly without anyone having to set anything up.

Complete directory: docs.langdock.com/en/using-langdock/integrations/mcp-directory.

MCP Apps · interactive interfaces instead of a text reply

What is new is that an MCP server can return not just text but a small interactive interface. Langdock renders this HTML interface in a sandboxed iframe directly in the chat, for example a form or a preview instead of plain text output. The reference example is the ServiceNow MCP server. Important for you: even though the interface comes from the server, every tool call it triggers still needs your explicit confirmation.

7.3 Running your own custom MCP server

If an internal service needs to be connected that does not correspond to any external MCP server: you can write an MCP server yourself (in Python, TypeScript, Go) and address it from Langdock. That is developer work, not a click-through setup.

Alternatively, you can build a custom integration directly in Langdock without MCP, via the built-in JavaScript builder. For many use cases that is faster than your own MCP server.

It is even faster with the Integration Builder Agent: you describe in the chat which tool you want to connect and what it should do, attach the API docs if needed, and the agent sets up auth (OAuth, API key or none), actions and triggers. The prerequisite is a connection to the Langdock integration with an API key that has the Integrations API scope. Start via Integrations → Add integration → Start building or via the agent template. On dedicated deployments only the template route is available.

What the sandbox code comes with

The code of a custom action runs in a sandboxed JavaScript environment. External libraries cannot be installed or imported there, but Langdock provides a set of built-in ld.* functions that cover exactly the tasks you would otherwise need an npm package for:

• HTTP: ld.request() for calls with automatic JSON handling, ld.awsRequest() for AWS SigV4-signed requests.
• Data: conversion between CSV, Parquet, Arrow and JSON, plus a check that restricts SQL queries to read access.
• Crypto: RSA-SHA256 signatures for JWT and OAuth flows, Base64 encoding and decoding.
• Utilities: logging for debugging and ld.wait() for pauses against rate limits, capped at 30,000 milliseconds.

Limits: 100 MB per response body, 150 MB per execution including logs and inline files. Private and internal network addresses are blocked. Python code nodes in workflows use their own runtime, the ld.* functions are not available there.

Files in custom actions

A custom action can accept and return files. Inputs arrive as an object with file name, MIME type, size, Base64 content and modification date, outputs you place under a files key and they land in the chat as normal attachments. The limits are 100 MB and a maximum of 20 files per action as well as a timeout of two minutes per execution.

Details and examples: docs.langdock.com/en/using-langdock/guides/integrations/create-integrations.

Files between chat and MCP server

MCP is not limited to text. If a tool declares an input field with format: "file", Langdock automatically resolves a file reference from the chat and hands the server a ready-made object with file name, MIME type, Base64 content, size and modification date. Conversely, a server can return files via MCP resources, which land in Langdock as perfectly normal attachments: view, download, pass on to the next tool.

7.4 Langdock as an MCP server · the other direction

So far this has been about bringing external tools into Langdock. It also works the other way round: via the Langdock Agent MCP Server you expose your own agents to the outside, so that other MCP-capable clients can call them as a tool.

• Endpoint: https://api.langdock.com/mcp. For a dedicated deployment, https://<your-domain>/api/public/mcp instead.
• Auth: a Langdock API key with the Agent API scope, either as Authorization: Bearer or as x-api-key. A workspace admin creates keys in the workspace settings under API.
• Three tools: find_agent looks up the agent ID for a name, ask_agent sends a prompt to an agent (with optional messageHistory for multi-turn conversations), ask_custom_agent configures an agent ad hoc.

In practice this means: the specialist agent you built in Langdock can be addressed from other AI clients without you having to rebuild prompts and integrations there.

7.5 A2A · when agents talk to agents

Alongside MCP, Langdock supports the Agent-to-Agent protocol (A2A). It originally comes from Google and is now maintained by the Linux Foundation.

Intention	What for
Query a database, call an API, connect an external tool	MCP
Hand research to a specialised agent, coordinate several agents on one task	A2A

Technically, every A2A agent describes itself via an AgentCard, a JSON file at /.well-known/agent-card.json that lists name, description and capabilities. Automatic discovery builds on that. The procedure is always the same: read the card, send the task, receive the complete answer. There is no streaming yet, and authentication is either none or via API key.

Important for admins: Langdock blocks private and internal network addresses in AgentCard URLs and A2A requests. If you want to reach internal A2A agents, you need a dedicated deployment with URL validation set accordingly. This block is a protection against server-side request forgery, not an arbitrary hurdle.

7.6 Security notes on MCP

The most common questions from everyday setup, plus three sources through which you always stay up to date.

8.1 Common error patterns

“Need admin approval”

Occurs with the Microsoft integrations. Solution: your Microsoft admin has to grant tenant consent in Entra. Details in 3.3.

“Re-authorization required” / token expired

OAuth tokens have a limited lifetime. If the integration reports “Re-authorize”: click the link once, repeat the login, done. Since May 2026, Langdock even shows this notice inline in the chat when a token expires in the middle of a conversation.

“Connection not shareable”

You probably tried to share an OAuth connection with colleagues. That is not possible by design, an OAuth token belongs to exactly one person. Every person creates their own connection. If a team is supposed to access a source together, the route is via an agent with a preselected connection (see 1.4).

If no Share connection appears in the action menu of an API key connection, you lack the permissions: only workspace admins may share directly.

SharePoint integration does not find files

Check: does the connected Microsoft account have read access to the SharePoint site in the original at all? The integration inherits your permissions. If you cannot see the site in the browser, the integration cannot see it either.

Folder Sync leaves out files

Contrary to a common assumption, spreadsheets are no longer a problem, XLS, XLSX, CSV, TSV and Google Sheets are synced too (see 6.2). Images and other non-text media are left out. If something is still missing: the folder is capped at 200 files, everything above that is dropped. SharePoint lists and OneNote notebooks cannot be chosen as a source in the first place. For large collections it helps to attach subfolders individually as separate sync folders instead of the whole parent folder.

Synced folder is suddenly dead

A Folder Sync depends on the personal OAuth connection of the person who attached it. If that person leaves the company or their access is revoked, the sync breaks and does not recover on its own. The solution is always the same: someone else with access to the source folder attaches it anew. For business-critical agents, make sure from the start that several people have access to the source folders.

BYOO integration does not connect

Common mistake: the redirect URL in the third-party system does not match the Langdock URL expected. Exactly what Langdock specifies in the setup step has to be copied 1:1 into the third-party system. No trailing slash, no additional parameter.

8.2 Where to get official support

• Official docs portal: docs.langdock.com/en/using-langdock/integrations/introduction
• Email support: support@langdock.com
• FAQ page on integrations: docs.langdock.com/en/using-langdock/guides/integrations/faq

8.3 Staying current · three sources

1. Admin newsletter (see 3.6). Most important source. Arrives before breaking changes.
2. Public changelog: langdock.com/changelog. Shows new integrations, UI changes, bug fixes. Worth a monthly look.
3. DECAID Academy. We update this guide on major changes. The current state is always in the footer.