Skip to main content
To use Langdock in Slack, the Langdock app must be installed in your Slack workspace. This can only be done by a workspace admin following the steps detailed on the Slack Bot integration page.
Afterwards, make sure that you have the app installed in your account. It should appear in the “Apps” section at the bottom left. If it’s not installed, please click on “Add apps” to add the app to your Slack account. Check if successfully installed if the Langdock App appears in the Apps section in Slack

​
Basic Usage

The Langdock Slack Bot gives you full access to Langdock models and Agents directly in Slack. Once installed, you can interact with it by:
  • Tagging @Langdock in any channel where the app is a member
  • Sending a direct message to @Langdock (find it under “Apps” in your left sidebar)
After tagging @Langdock or messaging it directly, the bot responds in a thread where you can choose your default model or any Agent. The default model comes from your workspace settings or your personal preferences in Langdock Preferences. Tag @Langdock to call the App Click on answer with "Model" or select an Agent

​
What does the Slack Bot see?

The Langdock Slack Bot only sees messages in threads where it’s tagged or messaged directly. This is by design for privacy, it doesn’t monitor other channel messages or threads. To ensure the bot sees a specific message, tag it in that same thread. In the example below, the bot can see and translate the previous message because they’re in the same thread: Example translation in the same thread

​
Using Agents

You have access to all Agents available in your Langdock workspace. After tagging @Langdock or messaging it directly, search and select any Agent as shown below. The Agent will respond using all its knowledge and capabilities. Access to Agents from the App

​
Approving an action

When an action, a connected tool, or a call to another Agent needs your approval, the bot posts a card in the thread. The card names the action and the required fields that have a value. It also names the integration and account when those are known, and the number of optional fields that are set. Click Approve to run it, or Deny to skip it. Only the person who asked can answer. If someone else tries to answer, only they see “Only the person who asked can approve this action.”
If the action needs a connection chosen in Langdock, Slack posts the action name followed by “needs a connection chosen in Langdock, which Slack can’t do yet. Please run it from Langdock.” There is no Approve or Deny button on that message.
Example of the approval card in Slack with Approve and Deny

​
Continue conversation in Langdock

By default, Slack Bot messages don’t appear in your Langdock message history. To continue the conversation in Langdock, click “Continue conversation in Langdock” in any bot reply. This opens the conversation in your browser, picking up exactly where you left off in Slack.
While you can see what the bot replies to other users in Slack, you can only continue your own conversations. To join an existing thread, send a new message in that thread.
Example conversation in slack with the App Same example but in Langdock

​
Web search, file work, image generation

The Slack Bot has identical capabilities to the Langdock web app. You’ll get the same results whether you’re using Slack or the web interface. Example of the App using Web Search

​
Images and documents

The Slack Bot reads images and documents it can open, the same way the web app does. If a file in the thread can’t be read, the bot still replies and can tell you which file could not be read. Example of the App reading through a shared file and giving back a summary

​
Skills

The Slack Bot runs the Skills you already use in a regular chat: your personal Skills, workspace Skills, and built-in Skills. Actions linked to a Skill can run after the bot reads that Skill’s instructions.

​
Limitations of the Slack Bot

  • Cannot be used in Direct Messages with other users, only in channels or direct messages to the bot
  • Only sees content in threads where it’s tagged, no access to broader workspace information like channel members or other messages

​
FAQ

Use the Slack Bot when users should access Langdock models or agents directly from Slack. It is useful for quick team questions, lightweight workflows, and bringing agents into existing Slack conversations.
Check that the app is installed, the user has Langdock access, the relevant agent or model is available, and Slack permissions are configured correctly. If the issue affects one channel, check channel access and app permissions.