Using agents in Slack

Connect your Gumloop agents to Slack channels so your team can work with them in the tool they already use every day.

Set up

Connect a bot and add the agent to a channel.

Use

@mention, forward, stop, and follow threads.

Configure

Thread replies, detailed steps, and the attribution stamp.

Access & credentials

Who can run the agent and whose accounts it uses.

Commands

/gummie, !stop, and !link.

Troubleshooting

Fixes for the most common problems.

Why use agents in Slack?

Shared learning

Every interaction in a channel is visible to the team, so people learn how to use the agent by watching each other.

Where work happens

Your team already talks in Slack. The agent joins those conversations without a new tool to learn.

Team-wide access

Instead of one person running automations, the whole channel uses the same agent with consistent results.

No training required

If your team knows how to @mention someone in Slack, they know how to use an agent.

Add an agent to Slack

Connecting or disconnecting Slack bots requires Owner access to the agent.

Open Channels → Slack

Open Channels in the agent sidebar, then select Slack.

Channels page with Slack selected, showing Add Slack bot, Slack preferences, and the list of bots and channels

Add a bot

Click Add Slack bot to connect the default Gumloop bot or a custom Slack app. Connecting Slack the first time uses your Connectors account.

Add the bot to a channel

Click Add to Channel and pick a tab:

New Channel creates a Slack channel and adds the bot. Pick a workspace, enter a name, and optionally turn on Make Channel Private.
Existing Channel adds the bot to a channel that already exists.
Commands shows the /gummie add command if you prefer to paste it in Slack.

Add to a Slack channel sheet with New Channel, Existing Channel, and Commands tabs

Once the bot is in a channel, the Slack bots and Slack channels tables on the same page show each channel’s members, task count, and when the agent was last used.

One agent per channel with the standard @Gumloop bot. To switch agents, run /gummie remove first. To run several agents in one channel, give each additional agent its own Custom Slack App.

Custom agents work in public and private channels, not in direct messages. DMs to the Gumloop app go to your personal Gumball.

Talk to your agent

Mention the agent

@mention the agent in any message in the channel:

@Gumloop [your question or task]

Mention it in a top-level message to start a new thread, or inside an existing thread to continue the conversation. The agent always replies in the thread.

Agent interaction in Slack showing an @Gumloop mention and the agent's threaded response

Forward a message

Forward any Slack message to the agent and it treats the message as a task. The agent reads the forwarded text, formatted Block Kit content, and attached files, so you don’t need to copy and paste.

Follow the agent’s progress

While the agent works, a progress card in the thread shows what it is doing, for example Thinking…, Working on it…, or Waiting for results…. When the run ends, the card shows how long it took, then the agent posts its answer. By default the card lists each step the agent takes. To show only a short status and step count, turn off Show Detailed Steps.

Stop a response

While the agent is working, Slack can show a Working… indicator with a Stop button in the thread. Click Stop to end the agent’s current run.

If the agent already posted, its message reads This response was stopped.
If it had not posted anything yet, it replies Stopped this chat.
Other agents in the same thread keep running.

You can also type !stop in the thread. See Thread commands.

Slack only shows the Stop button for apps subscribed to Slack’s agent_session_stopped event. For a custom Slack app, see Stopping a response.

Continue a thread someone else started

Anyone in the channel who is allowed to run the agent can reply in a thread another person started, and the agent continues that conversation. Once you reply in the thread, you can also:

Open the conversation in Gumloop as a viewer.
Download files the agent shares in the thread.

Who can run the agent is set by its sharing settings. People from another organization can’t continue the thread.

Files and images

Files the agent creates are uploaded straight into the thread. When the agent uses Image Generation, Slack gets both the image file and a link. Turn on Image Generation in the agent’s Abilities section to enable it.

Abilities section of an agent showing Image Generation turned on

Current image models include GPT-Image 2.5 Flare, GPT-Image 2.5 Sunburst, GPT-Image 2, Gemini 3.1 Flash (Nano Banana 2), Gemini 3 Pro, and Gemini 2.5 Flash Image.

Image generation is charged like any other model call, based on the usage the image model reports. Higher quality or resolution costs more credits. See Credits for how BYOK affects image generation.

Rich messages and buttons (Block Kit)

The standard @Gumloop bot can post Block Kit messages, including sections, dividers, context lines, images, and buttons. You don’t need a Custom Slack App for this. The agent’s normal thread replies are formatted text. To send Block Kit, the agent uses the Slack connector:

Add the Slack connector to the agent.
Ask the agent to post a Block Kit message, or describe the message in its instructions, for example:

@Gumloop Post a Block Kit message in #releases with a summary section, a divider,
and two link buttons: "Open release notes" and "View dashboard".

The Slack connector’s Send Message, Send Ephemeral Message, Update Message, and Schedule Message tools all accept Block Kit blocks, so the agent can post to a channel or thread, show a message to one person, edit a message it sent, or schedule one for later.

Who it posts as: messages go out as the Gumloop bot. If the agent has a custom Slack app, they go out as that app instead. See Choosing Which Bot the Agent Acts As.
Attribution: when the Slack Attribution Stamp is on, Gumloop adds a Sent by line with a View conversation link to the bottom of messages sent with Send Message.
Buttons: link buttons (buttons with a url) open their link when clicked. Clicks on other buttons aren’t sent back to your agent. To have someone approve or reject an action from Slack, use approvals instead.

Gumloop also posts its own interactive messages in the thread when needed:

Approve and Reject buttons when an action needs approval
Connect and Add buttons when the agent needs an account or connector. See Whose accounts the agent uses
Request Access & Setup when someone isn’t allowed to use the agent. See Who can use the agent
Browser handoff buttons when the agent needs you to finish a step in its browser. See Agent Browser

Direct messages go to Gumball

You can DM the Gumloop app in your workspace with no channel, no @mention, and nothing to set up. Those DMs are answered by your own Gumball, the personal agent that comes with every Gumloop account, running on your connectors and skills. DMs never reach a custom agent. To DM a custom agent under its own name and avatar, connect a Custom Slack App for it.

Need custom branding? Connect your own Slack app so the agent appears with its own name and avatar instead of “@Gumloop”. See Custom Slack App Integration.

Slack preferences

Three preferences on Channels → Slack control how the agent behaves in Slack. They apply to every channel the agent is in, and changes take effect for new messages right away.

Preference	What it controls	Default
Thread Replies	When the agent answers thread replies that don’t @mention it	Auto
Slack Attribution Stamp	The agent name and View conversation link under each reply	On
Show Detailed Steps	Whether the progress card lists each step	On

Thread Replies

The Thread Replies dropdown controls when the agent replies inside a thread it is already part of.

Auto (Default)
Only on mentions
On all messages

The agent decides whether a thread reply is meant for it, so nobody has to @mention it every time.

Two-party threads: while the thread has only you and the agent, it replies to every message, the same as On all messages.
Group threads: once a thread has three or more parties (people and other bots both count), Gumloop checks each message that doesn’t @mention the agent and decides which agent in the thread, if any, it is for. The agent replies only when it is picked. If several agents share the thread, the message is judged once and at most one of them answers.
Messages for someone else: a reply that @mentions anyone other than the agent, or a broadcast (@here, @channel, or a user group), is skipped without a check.

Example: Three people are in a thread with the agent. “Can you also break that down by team?” gets an answer from the agent. “Gonzalo, can you review the PR later today?” does not.

Auto uses the Jev 1.13 model to make the decision. If you don’t have access to Jev 1.13, Auto is disabled in the dropdown and a Request access button appears under Thread Replies. An Auto agent whose creator doesn’t have access to Jev 1.13 keeps replying in two-party threads but stays quiet in group threads unless @mentioned.

The agent only responds when explicitly @mentioned. Your team can discuss in the thread without triggering it.Example: After @Gumloop analyze this customer, your team can discuss the results freely. The agent only responds again when someone @mentions it with a follow-up.

The agent responds to every thread reply, no @mention needed, while the thread is just you and the agent.Example: You start with @Gumloop analyze this customer. A follow-up like “What about their purchase history?” triggers the agent automatically.Once a third person joins the thread, the agent switches to replying only when @mentioned in that thread. Use Auto if you want the agent to keep answering follow-ups in group threads.

Slack attribution stamp

Each agent reply includes an attribution stamp with the agent’s name and a View conversation link to the full conversation in Gumloop, including tool calls and credit usage.

Slack message from Gumloop showing the attribution stamp with the agent name and View conversation link

The stamp also appears on messages the agent sends with the Slack connector’s Send Message tool, such as Block Kit messages posted to another channel. The stamp is on by default. Turn off Slack Attribution Stamp on Channels → Slack to hide it for this agent.

Show Detailed Steps

Show Detailed Steps controls how much the progress card shows while the agent works.

On (default): the card lists each step the agent takes, so the channel can see what it searched, read, or ran.
Off: the card shows a short status and a step count. Useful in busy channels or when the agent calls many tools per answer.

Access and connected accounts

Who can use the agent

Being in the Slack channel is not enough on its own. A person can run the agent only if its sharing settings allow it:

General Access	Who can use the agent in Slack
Restricted	Owners and people added by email
Team	Everyone in the team the agent lives in
Organization	Everyone in your organization
Anyone	Anyone with a Gumloop account linked to their Slack email

Anyone else gets an Access Required message in Slack with a Request Access & Setup button.

Whose accounts the agent uses

When you message an agent in Slack, each connector uses its configured account setting: Use Personal Default, Use Team Default (team agents only), or Use Specific Account. By default, it uses your connected accounts, not the agent creator’s. An explicitly agent-owned account is shared by everyone with access to the agent. See Choose which account to use.

You already use Gumloop

If your Slack email matches your Gumloop account, the agent uses your connected accounts right away with no extra setup.Example: If the agent uses Gmail and Google Calendar, it reads your Gmail and your Calendar.

You don't have a Gumloop account yet

The first time you message the agent, it replies with an Account Required prompt.

Click Get Started with Gumloop and sign up with your Slack email.
Connect the services the agent needs.
Go back to Slack and @mention the agent again.

Your Slack and Gumloop email addresses must match.

Enterprise organizations can skip this for specific agents. An admin can register your Slack workspace and let its members message chosen agents with no Gumloop account, running on a shared organization service account. See Organization Service Accounts for Slack Agents.

A connector isn't set up

If the agent needs an account you haven’t connected, it posts a message in the thread with a button to fix it, for example:

🔑 You cannot use `Send Email` tool since your Gmail account is not connected.
[Connect Gmail on Gumloop]

If the connector isn’t on the agent at all, the message reads To continue, add Gmail to this agent. with an Add Gmail button. Connect or add it, then ask the agent again.

To let teammates use the agent without connecting their own accounts, put the agent in a team and switch its connectors to team accounts.

Teams are available on Pro and Enterprise plans.

Create or select a team

On the Home page, find Teams in the sidebar and click + to create a team.

Click the plus icon in the Teams sidebar section

To include everyone automatically, set a default team that all organization members join. Go to Settings → Teams, open the three-dot menu next to a team, and select Make Default.

Teams list with the three-dot menu open on Make Default, described as setting the team as the organization default

Move the agent to the team

On the Home page, open the agent’s three-dot menu (⋮), select Move to Team, and choose the team.

Agent three-dot menu showing Copy Link, Share, Pin to My Sidebar, Rename, Duplicate, Move to Team, and Delete

Connect team connectors

Expand the team in the sidebar and open Connectors, then add the integrations the agent needs (for example Gmail, Google Drive, or Salesforce).

Team Connectors page with Discover, All, and Connected tabs and a searchable list of connectors

Point the agent at team connectors

In the agent, open the three-dot menu next to each connector and select Use Team Default.

Account menu on an agent connector showing Use Personal Default, Use Team Default, Use Specific Account, and Remove

Agents that live in a team are available at least to the whole team, and team connectors only work for team members. People outside the team can’t use team connectors through the agent. A default team avoids adding people one by one.

Data privacy

Your data stays yours

When the agent runs on your personal accounts, only your connected accounts are used. Teammates can’t reach your data through the agent.

Your permissions still apply

Admin security controls and roles in Gumloop apply in Slack. You can only reach what you’re already allowed to.

Slack commands

Channel commands

Type these in the channel’s message box.

Command	What it does
`/invite @Gumloop`	Add the Gumloop bot to the channel (required before `/gummie add`)
`/gummie add [agent-id]`	Add an agent to the current channel
`/gummie remove`	Remove the agent from the current channel
`/gummie active`	Show which agent is active in this channel
`/gummie help`	Show all available commands

You rarely need /gummie add. Channels → Slack → Add to Channel does the same thing, and its Commands tab has the full command ready to copy.

Thread commands

Type these as a reply in the agent’s thread.

Command	What it does
`!stop`	Stop the agent’s current response and prevent further replies in this thread. The agent reacts with 👍 to confirm. You can also use Slack’s Stop button.
`!link`	Get a link only you can see to the full conversation in Gumloop, including tool calls and credit usage.

Best practices and troubleshooting

Best practices
Troubleshooting

Choose the right channels

Agents work in public and private channels. Put each agent where its audience already works, for example:

#support: ticket triage and refund checks
#sales: lead research and enrichment
#marketing: campaign planning and content
#data: analysis and reporting

Set channel expectations

When you add an agent, post a message with what it can do, how to use it (@Gumloop [your question]), and one example.

Use descriptive agent names

Prefer “Support Ticket Assistant” or “Sales Lead Researcher” over “Agent 1”. The name appears in the attribution stamp, and /gummie active shows it too.

Pick a Thread Replies mode

Auto (default): best for most channels. The agent answers follow-ups meant for it and stays quiet when people talk to each other.
Only on mentions: the agent never replies unless someone @mentions it.
On all messages: for one-on-one threads where the agent should answer every reply.

Review how the agent is used

Channels → Slack shows task counts and last activity for each channel. Open the agent’s Tasks to read the conversations, then refine instructions, connectors, and skills based on where the agent struggles.

Check connectors before launch

Test with your own accounts first, list which services teammates need to connect, and share the Connectors page. Or use team connectors so nobody has to connect anything.

The agent doesn't respond

Did you @mention the agent?
Is the bot in the channel? Run /invite @Gumloop.
Is an agent active in the channel? Run /gummie active.
Is this a channel? DMs to the Gumloop app reach Gumball, not this agent.
Do the agent’s sharing settings include you?

The agent doesn't respond in threads

Check Thread Replies on Channels → Slack. With Only on mentions, you must @mention the agent in each reply. With Auto, the agent stays quiet in a group thread when a message looks meant for someone else. @mention the agent to make sure it answers.

I get an Access Required message

The agent’s sharing settings don’t include you. Click Request Access & Setup, or ask an Owner to share the agent with you or your team. See Agent Access.

Authentication errors

Click the Connect button in the agent’s message, or visit your Connectors page. For team connectors, ask a team admin.

The wrong agent responds

With the standard @Gumloop bot, only one agent can be active per channel. Run /gummie active to check, /gummie remove to clear it, then add the right agent from Channels → Slack. For several agents in one channel, use a Custom Slack App for each.

I can't add the agent to a channel

You need Owner access to the agent.
Agents work in public and private channels, not DMs.
Make sure you’re allowed to add apps to the channel in Slack.
If you use /gummie add, run /invite @Gumloop first and copy the full agent ID from the Commands tab.

The agent replies with text instead of Block Kit

Make sure the Slack connector is on the agent, then ask it explicitly to post a Block Kit message with the Slack connector, and say which channel or thread to post in. See Rich messages and buttons.

A Block Kit button doesn't do anything

Only link buttons (buttons with a url) do something when clicked. Gumloop doesn’t send clicks on other buttons back to the agent. For approve or reject decisions, use approvals.

Responses are slow

Limit the agent to the connectors it needs, try a faster model, or split big requests into smaller ones.

Example use cases

Support channel
Sales channel
Data channel

Agent: Support Ticket Assistant · Channel: #customer-support (public) · Thread Replies: Auto

Teammate: "@Gumloop Is ticket #12345 eligible for a refund?"
Agent: [Checks the ticket, reads the policy, evaluates eligibility]

Teammate (in thread): "What about ticket #12346?"
Agent: [Auto sees the follow-up is for it and checks #12346]

Teammate (in thread): "Priya, can you approve this one?"
Agent: [Stays quiet, the message is for Priya]

Why it works: Support gets answers without leaving Slack, and follow-ups flow naturally without spamming every reply.

Agent: Lead Research Assistant · Channel: #sales-team (public) · Thread Replies: Only on mentions

Teammate: "@Gumloop Research this company: [LinkedIn URL]"
Agent: [Enriches the lead, checks the CRM, drafts outreach]

Teammate (in thread): "Thanks! What's the best time to reach out?"
(No reply, the team discusses freely)

Teammate: "@Gumloop What's the status of opportunities over $50k?"
Agent: [Queries Salesforce, summarizes the pipeline]

Why it works: Reps get research instantly, and newer reps learn by watching experienced reps use the agent.

Agent: Data Analysis Assistant · Channel: #data-team (private) · Thread Replies: Only on mentions

Teammate: "@Gumloop Compare Q4 revenue vs Q3 by product line"
Agent: [Runs a BigQuery query, generates the comparison]

Teammate (in thread): "@Gumloop Now break it down by region"
Agent: [Continues with a regional breakdown]

Why it works: Analysts get quick answers, and teammates learn what data is available and how to ask for it.

Important limitations

One agent per channel (standard bot)

Only one @Gumloop agent per channel. For more, use a Custom Slack App for each.

DMs reach Gumball only

Custom agents work in public and private channels. DMs to the Gumloop app go to your Gumball.

Mention to start

You must @mention the agent to start a conversation. In threads, it depends on Thread Replies.

Email matching required

Your Slack email must match your Gumloop account email, unless your admin set up an organization service account.

Next steps

Build your first agent

Create and configure agents in Gumloop

Custom Slack App

Give an agent its own name, avatar, and DMs

Using agents in Teams

Deploy the same agents to Microsoft Teams

Set up

Use

Configure

Access & credentials

Commands

Troubleshooting

​Why use agents in Slack?

Shared learning

Where work happens

Team-wide access

No training required

​Add an agent to Slack

​Talk to your agent

​Mention the agent

​Forward a message

​Follow the agent’s progress

​Stop a response

​Continue a thread someone else started

​Files and images

​Rich messages and buttons (Block Kit)

​Direct messages go to Gumball

​Slack preferences

​Thread Replies

​Slack attribution stamp

​Show Detailed Steps

​Access and connected accounts

​Who can use the agent

​Whose accounts the agent uses

​Share connectors with a team

​Data privacy

Your data stays yours

Your permissions still apply

​Slack commands

​Channel commands

​Thread commands

​Best practices and troubleshooting

​Example use cases

​Important limitations

One agent per channel (standard bot)

DMs reach Gumball only

Mention to start

Email matching required

​Next steps

Build your first agent

Custom Slack App

Using agents in Teams

Why use agents in Slack?

Add an agent to Slack

Talk to your agent

Mention the agent

Forward a message

Follow the agent’s progress

Stop a response

Continue a thread someone else started

Files and images

Rich messages and buttons (Block Kit)

Direct messages go to Gumball

Slack preferences

Thread Replies

Slack attribution stamp

Show Detailed Steps

Access and connected accounts

Who can use the agent

Whose accounts the agent uses

Share connectors with a team

Data privacy

Slack commands

Channel commands

Thread commands

Best practices and troubleshooting

Example use cases

Important limitations

Next steps