Connect self-hosted LangSmith to Slack

• Deployment access: Permission to configure and restart your LangSmith platform backend. For Kubernetes, access to the namespace where LangSmith runs.
• Slack access: Permission to create and install an app in the Slack workspace that receives notifications. Obtain administrator approval if your workspace restricts app installation.
• LangSmith access: The organization:manage permission to connect or disconnect a Slack workspace. An organization administrator can complete this step after the operator configures the deployment.
• Network access: Backend HTTPS access to Slack and browser access to your deployment’s HTTPS callback. See Allow network access.

​

Create your Slack app

1. Copy the JSON below and replace the URL in oauth_config.redirect_urls. For the standard ingress, append /api/v1/platform/slack/callback to the URL you use to open LangSmith. For example, https://langsmith.example.com becomes https://langsmith.example.com/api/v1/platform/slack/callback. If LangSmith runs at https://langsmith.example.com/langsmith, use https://langsmith.example.com/langsmith/api/v1/platform/slack/callback. For a custom ingress or separate API host, use the HTTPS URL that reaches your deployment’s Slack callback.
2. Open Your Apps and select Create New App. Choose From a manifest, then click Continue.
3. Select the JSON tab, paste your edited manifest, and choose your Slack workspace. Click Next.
4. Review the five permissions and click Create and Install. Complete any Slack authorization or administrator approval prompts.
5. Open the new app’s Basic Information > App Credentials. Copy the Client ID and Client Secret, using Show to reveal the secret. Store them in your deployment’s secret manager. Use the Client ID, not the App ID or Signing Secret. You do not send these credentials to LangChain.

{
  "display_information": {
    "name": "LangSmith Notifications",
    "description": "Engine and alert notifications from your LangSmith deployment"
  },
  "features": {
    "bot_user": {
      "display_name": "LangSmith Notifications",
      "always_online": false
    }
  },
  "oauth_config": {
    "redirect_urls": [
      "https://langsmith.example.com/api/v1/platform/slack/callback"
    ],
    "scopes": {
      "bot": [
        "chat:write",
        "channels:read",
        "channels:join",
        "groups:read",
        "reactions:write"
      ]
    }
  },
  "settings": {
    "org_deploy_enabled": false,
    "socket_mode_enabled": false,
    "token_rotation_enabled": false
  }
}

• chat:write: Send notification messages.
• channels:read: List public channels in the channel picker.
• channels:join: Join a selected public channel when delivering a notification, if needed.
• groups:read: List private channels that the bot has been invited to.
• reactions:write: Add and remove emoji reactions. Notification delivery does not currently use this permission.

​

Configure your deployment

apiVersion: v1
kind: Secret
metadata:
  name: slack-app-credentials
  namespace: "<your-langsmith-namespace>"
type: Opaque
stringData:
  client-id: "<your-slack-client-id>"
  client-secret: "<your-slack-client-secret>"

kubectl apply -f slack-app-secret.yaml

platformBackend:
  deployment:
    extraEnv:
      - name: LANGSMITH_SLACK_CLIENT_ID
        valueFrom:
          secretKeyRef:
            name: slack-app-credentials
            key: client-id
      - name: LANGSMITH_SLACK_CLIENT_SECRET
        valueFrom:
          secretKeyRef:
            name: slack-app-credentials
            key: client-secret
      - name: LANGSMITH_SLACK_REDIRECT_URI
        value: "https://langsmith.example.com/api/v1/platform/slack/callback"

helm upgrade <release-name> langchain/langsmith \
  --namespace <your-langsmith-namespace> \
  --version <your-chart-version> \
  --values <path-to-your-existing-values-file> \
  --wait

​

Allow network access

• Backend: Outbound HTTPS to the Slack Web API at slack.com for OAuth exchange, channel lookup, and notifications.
• Browser: Access to Slack and your deployment’s callback URL and UI.

​

Connect a Slack workspace

1. Open your LangSmith instance and go to Settings > your organization’s General settings.
2. Under Slack, click Connect Slack. You can also connect from the channel selector when configuring an Engine or alert notification.
3. Choose the Slack workspace, review your app’s requested permissions, and click Allow. Complete administrator approval if required.
4. Confirm that the browser returns to your LangSmith instance and the workspace appears as Connected. Choose that workspace and a channel in your notification settings. For a private channel, invite your configured Slack app to the channel first, then refresh the picker. LangSmith joins the selected public channel when it first delivers a message, if needed.
5. Save the destination with the event types and minimum issue severity you need. See Configure Engine notifications or Configure alert notifications.

​

Verify delivery

1. Save a Slack destination for issue.created on a test project. Under Notify when, select Issue created. Set Minimum issue severity to All severities during testing.
2. Enable Engine for the test project and let it analyze new traces. Wait for Engine to create a new issue. If Engine finds no new issue, there is no issue.created notification to send.
3. Check that a message arrives in the selected channel and that View issue opens your self-hosted instance.

​

Troubleshoot the connection

• Slack is not configured: Contact your operator. Confirm that your release supports the connection and all three Slack environment variables are set. Reload the UI after restarting the backend.
• Slack configuration unavailable: The UI could not load the backend’s configuration. Reload the page and have your operator check the backend; this message does not mean app credentials are absent.
• The backend pod cannot start: Check that slack-app-credentials exists in the same namespace as LangSmith and contains both client-id and client-secret.
• Slack rejects the app credentials: Copy the Client ID and Client Secret from the same Slack app. Update the deployment Secret, restart the platform backend, and start Connect Slack again.
• Authorization cannot start: Confirm that the app has a bot user, all listed scopes, and permission to install in the selected workspace.
• Slack reports a redirect mismatch: Ensure LANGSMITH_SLACK_REDIRECT_URI matches the saved Slack Redirect URL, including scheme, host, port, and path.
• Authorization fails after returning: Start Connect Slack again. Authorization state expires after 10 minutes. Check browser access to the callback, backend access to Slack, and the configured app credentials. Keep token rotation disabled.
• A private channel is absent: Invite your configured Slack app to the channel, then refresh the picker.
• Messages do not arrive: Confirm Slack Web API access, matching encryption secrets on the API and workers, and the destination’s event and severity filters. If someone removed the app from Slack, reconnect the workspace.
• Links open the wrong host: Correct your deployment’s browser-facing URL configuration.

​

See also

• Engine on self-hosted LangSmith
• Engine notifications
• Alerts
• Configure egress