Skip to main content
Most teams don’t want another dashboard to check. Connecting Slack to Scout lets your agents work where your team already communicates — posting pipeline summaries to a sales channel, summarizing a support thread before a rep picks it up, or responding to questions in a dedicated help channel. Setup takes about five minutes and you’ll switch between Scout and Slack once to authorize the connection.

​
What Scout Agents Can Do in Slack

CapabilityExample
Post to channelsShare daily pipeline summaries, incident alerts, or weekly digests
Read threadsUnderstand context from a conversation before responding
Search historyFind past decisions, discussions, or referenced documents
React and replyAcknowledge messages and continue in-thread conversations
Respond to mentionsAnswer questions when someone mentions the agent in a channel

​
How to Connect Slack

1

Connect Slack to Scout

Go to studio.scoutos.com/integrations, find Slack, and click Connect. You’ll be redirected to Slack’s authorization page.
2

Authorize in Slack

Select the Slack workspace you want to connect, review the permissions Scout requests, and click Allow. You’ll be redirected back to Scout when the authorization is complete.
3

Configure your agent

Choose how you want your agent to work in Slack — as a tool it uses on demand, or as a deployment that lives persistently in a channel.Option A: Tools + Instructions (flexible)Use this when you want the agent to post to or read from Slack as part of a broader workflow, but not actively monitor conversations.
  1. Go to your agent’s Settings
  2. Click Add Tool in the Tools section and search for Slack
  3. In your agent’s Instructions, specify which channels it can access:
You can access the following Slack channels:
- #sales-leadership — for posting pipeline summaries
- #engineering — for technical discussion summaries
- #alerts — for posting incident updates
Option B: Deployments (channel-first)Use this when you want the agent to live in a Slack channel — listening, responding, and staying in the conversation rather than acting only on demand.
  1. Go to your agent’s Settings
  2. Click + Add Deployments → Slack
  3. In the configuration panel, select your Workspace and the Channel where the agent should operate
  4. Configure the deployment options (see below) and click + Add channel to save
OptionWhat it does
WorkspaceThe Slack workspace to deploy to — must be connected first
ChannelsThe specific channel this deployment monitors and responds in
Threaded contextPasses prior thread messages to the agent for in-context replies
Respond ifAn optional condition that filters when the agent responds — e.g., “the user is asking a technical question.” Leave blank to respond to all messages.
Additional instructionsChannel-specific instructions appended to the agent’s system prompt — useful for adjusting tone or scope per channel
If you leave Respond if blank, the agent replies to every message in the channel. That’s right for a dedicated support bot, but too noisy for a general channel like #general. Use a condition to keep the agent focused.
4

Add Scout to your Slack channels

This step is the most commonly skipped. Even after connecting and configuring everything in Scout, your agent cannot see any channel until you invite it in Slack.For each channel where you want Scout to work, go to that channel in Slack and run:
/invite @Scout
Or open the channel, click the channel name at the top, go to Integrations → Add apps, search for “Scout,” and click Add. Repeat for every channel your agent needs to access.
Scout can only read messages posted after it’s added to a channel. It won’t have access to earlier history. If you need context from past discussions, copy the relevant content into your agent’s instructions or a connected knowledge source.

​
Slack as a Deployment Channel

The most powerful Slack use case isn’t an agent that occasionally posts — it’s an agent that runs on a schedule and delivers something useful every day without being prompted. A few examples of what this looks like in practice: Daily pipeline brief — An agent connected to Salesforce runs each morning, pulls open deals with no activity in the last seven days, and posts a summary to #sales-leadership before standup. The team reviews it asynchronously instead of pulling a manual report. Incident summaries — An agent monitors #incidents, reads the thread when a new incident is posted, and replies with a structured summary: what’s affected, current status, and the latest update. On-call engineers get context without reading back through a noisy thread. Weekly digest — An agent reads activity across your engineering channels each Friday afternoon, generates a summary of decisions, PRs merged, and open questions, and posts it to #general-engineering before the weekend.

​
Instruction Examples

Add channel-specific instructions to your agent so it knows what to post and where: 
For Slack tasks:

1. Post pipeline summaries to #sales-leadership in a bullet list format.
2. Keep posts under 400 words. Use headers for readability.
3. Always mention the data source (e.g., "Source: Salesforce as of [date]").
4. Never post PII or customer contact information to public channels.
5. Use threaded replies rather than new top-level messages when responding in context.

​
Prompt Examples

These prompts work once Slack is connected and enabled on your agent:
  • “Summarize the discussion in #engineering and post the key points to #general.”
  • “Find messages about the API outage yesterday and create a timeline.”
  • “Post a weekly digest to #general-engineering based on activity this week.”
  • “Read the thread in #support about the login issue and propose solutions.”
  • “Post today’s pipeline summary to #sales-leadership — use Salesforce data.”

​
Testing Your Integration

1

Test posting from Scout

In Scout chat, ask your agent to post a test message to a channel. Verify the message appears in Slack with the correct formatting.
2

Test reading a channel

Ask your agent to summarize the last five messages in a channel. Confirm it returns the correct content.
3

Test a Deployment (if configured)

Go to one of your configured channels in Slack, mention the agent or send a message that matches your Respond if condition, and verify it replies in the thread.

​
Troubleshooting

​
Next Steps

CRM

Feed Salesforce and HubSpot data into your Slack pipeline summaries.

Email & Calendar

Post meeting briefs and calendar digests to Slack automatically.

Google Drive & M365

Summarize documents from Drive or SharePoint and post results to channels.

Integrations Overview

See the full integration stack and recommended connection order.