Slack

The Slack app connects your Slack workspace to Sprigr Team in two layers. A workspace bot, connected once by an admin, lets every agent in the company post messages, read channel history and threads, and react in the channels it has been invited to. A personal connection, made by each person for themselves, lets their own agent search their messages and read their DMs and private channels. The two are kept apart: personal tools only ever see the calling person’s own Slack.

Note

Slack ships as a certified marketplace app. One install holds the workspace bot token and each person’s own token. Installing the app is an alternative to the Slack channel card on an agent: it gives agents Slack tools (reading and posting) as well as a way to be messaged. See Channels for the channel-card route.

Prerequisites

• A Slack workspace, and permission to install apps to it for the workspace bot step.
• Admin or Owner role in your Sprigr Team organisation to install the app. Any member can make a personal connection once it is installed.

Installing and connecting

1. Install the app

   Sign in to team.sprigr.com, open Apps in the sidebar, find Slack under Available, and install it. See Installing Apps.

2. Connect the workspace bot

   Open the app’s settings page from Apps > Installed and click Connect Slack workspace. Authorise it in Slack. The settings page then shows which workspace the bot is connected to.

3. Invite the bot to channels

   In each Slack channel you want agents to use, run /invite @<your bot>. Until the bot is a member, sends and reactions in that channel return not_in_channel.

4. Connect your personal Slack (optional)

   Ask your agent to connect your Slack. It runs slack_connect_personal and gives you a private link bound to you; approve it in Slack. Your connection is visible only to your own agent. The settings page shows how many people have connected, not who.

5. Check the connection

   Ask your agent “Is Slack connected?” It reports whether the workspace bot is connected and whether you have a personal connection.

Try asking your agent

“Post in #ops that the 2pm delivery has been pushed to tomorrow.”

“What was decided in the #launch thread this morning?”

“Search my Slack for the message from Priya about the venue quote.”

Available tools

Workspace bot (shared by every agent)

Tool	Description
slack_send_message	Send a message to a channel or DM as the company bot, optionally in a thread
slack_list_channels	List channels the bot is a member of, with topics and member counts
slack_get_channel_history	Read recent messages from a channel the bot is in
slack_get_thread	Read a thread’s parent and replies
slack_add_reaction	Add an emoji reaction to a message
slack_connection_status	Report whether the bot and the calling person’s personal connection are connected

Personal connection (only the calling person’s Slack)

Tool	Description
slack_search_messages	Search your messages, channels and DMs with Slack search syntax (in:#channel, from:@user, before:date)
slack_read_channel	Read recent messages from any channel you can see, including private channels
slack_read_dm	Read your direct message history with a person
slack_list_my_channels	List every channel you can see, including private channels and group DMs
slack_get_user_info	Read a Slack user’s profile (name, email, title, status, timezone)
slack_connect_personal	Start a personal connection and return your private authorise link

The app can also act as a Slack channel for your agents: inbound messages to the bot are delivered to the agent, and replies go back through the bot, with threads supported.

Common use cases

• Team notifications. A workflow posts a summary to #ops when a job is invoiced or a shipment goes out.
• Catch-up. “What did I miss in #support overnight?” reads the channel history and summarises it.
• Thread digest. The agent reads a long thread and lists the decisions and open questions.
• Finding a message. “Find where Sam shared the supplier price list” searches your own Slack and returns the message.
• Agent in Slack. Teammates message the bot directly and get the agent’s reply in the same thread.

Troubleshooting

not_in_channel when sending or reacting The bot has not been invited to that channel. Run /invite @<your bot> in the channel.

Search or DM tools say a personal connection is required You have not connected your own Slack. Ask your agent to connect your Slack and approve the private link it gives you. Someone else’s personal connection does not cover you.

Workspace bot shows not connected Only an admin who completed the Connect Slack workspace step has connected it. Reconnect from the app’s settings page.

The bot cannot read a private channel The workspace bot only sees channels it has been invited to. For private channels you belong to, use your personal connection instead.

Next steps

• Channels: Reach an agent from Slack, Telegram, WhatsApp or WebChat.
• Workflows: Post to Slack as a workflow step.
• Integrations Overview: See all available integrations.