Skip to main content
Connect Slack and your LivingContext agents become part of the conversation: mention the bot in a channel or DM it, and it starts a real agent run and posts the answer back in the thread — no context-switching into another tool. Slack is managed from the Channels tab of the Agent platform: open Agents → Channels.

​
Connect

Slack connects with a bot token from your own Slack app — there’s no marketplace install:
1

Create a Slack app with a bot

In your Slack workspace, create an app with a bot user and install it. Copy the bot token (xoxb-…) from the app’s OAuth & Permissions page.
2

Point events at LivingContext

In the Slack app’s configuration, point Event Subscriptions and your slash command at your workspace’s /api/slack/events endpoint.
3

Paste the details in Agents → Channels

Fill in the Team ID (T…), the bot token, and optionally the workspace name and bot user ID, then click Connect Slack. The card flips to Connected, with a Disconnect button when you need it.

​
What agents can do in Slack

  • Respond to mentions — @LivingContext summarize recent metadata changes in any channel the bot is in starts an agent run; the answer arrives threaded under your message.
  • Respond to DMs — message the bot directly for the same experience one-on-one.
  • Slash commands — /lc summarize open change requests acknowledges immediately (“Working on it…”) and posts the result to the channel when done.
Answers are grounded in the same Salesforce catalog and docs corpus as everywhere else, and formatted for Slack automatically.
Want a recurring digest? Create a cron trigger — for example, “Weekday morning digest: summarize new Salesforce changes since yesterday” — and the agent posts its result wherever you’ve wired it.

​
Beyond Slack

The same Channels tab also offers:
  • Microsoft Teams — paste an incoming webhook URL and finished background runs post a card to your Teams channel.
  • Public API keys — lc_live_… bearer keys for starting runs from the REST API or your own tools.

​
Security

  • Inbound Slack traffic is protected by signed request verification — LivingContext validates Slack’s signature on every request, so forged messages can’t reach your agents. Unknown workspaces are ignored, and duplicate events are deduplicated.
  • Agents in Slack operate under the same governance as everywhere else: allowed tools, permission modes, and approvals for side-effecting actions.
  • Every side-effecting action an agent takes is recorded in the platform Audit log, regardless of whether it was triggered from Slack or the app.
Autonomous agents — the kind you’d typically run behind a channel — require a Pro or higher plan. See Billing.

​
Troubleshooting

Confirm the connection is Connected in Agents → Channels, the bot is actually in the channel you’re mentioning it from, and your Slack app’s Event Subscriptions point at /api/slack/events. Check the Runs tab for failed runs — the transcript usually explains what went wrong.
Slack rendering differs from web Markdown. If a specific answer renders oddly, ask the agent for a simpler format — for example, lists instead of wide tables.

Agent platform

Define the agents, triggers, and approvals behind your channels.

Workspace agent

The org-intelligence tool set agents draw on when answering.