Using Agents in Slack

Connect your Gumloop agents to Slack channels so your entire team can interact with AI-powered assistants in the tools they use every day.

Why Use Agents in Slack?

Bringing agents to Slack transforms how your team learns and adopts AI automation:

Shared Learning

Visibility by default: Every interaction in a channel becomes a learning opportunity for the team. No more siloed knowledge—everyone sees how to use agents effectively.

Natural Integration

Where work happens: Teams already use Slack for communication. Agents integrate seamlessly into existing workflows without requiring new tools.

Collaborative Usage

Team-wide access: Instead of one person running automations, entire teams can leverage the same agent with consistent results.

Instant Adoption

Zero learning curve: If your team knows how to @mention someone in Slack, they know how to use an agent. No training required.

The Learning Effect: When someone asks an agent a question in a channel, everyone sees the interaction. This passive learning accelerates team-wide adoption faster than any training session could.

Adding an Agent to Slack

Authenticate with Slack (First-Time Setup)

If you haven’t already connected Gumloop to your Slack workspace, you’ll need to authenticate first.Visit the personal credentials page and authenticate with Slack to connect the Gumloop app to your workspace.

Gumloop credentials page showing Slack authentication

Click the Add Credential button for Slack and follow the OAuth flow to authorize Gumloop in your workspace.

Add the Gumloop bot to Your Channel

In the Slack channel where you want your agent you would need to add the Gumloop bot. To add the bot, you have two options:

Type /invite @Gumloop in the channel, OR
Click the channel name → Add integrations/Add app → Search for “Gumloop”

Typing /invite @Gumloop in Slack channel

This gives Gumloop permission to read and respond in the channel.

Confirmation that Gumloop was added to channel

Agents can be added to public or private channels, but not to direct messages (DMs).

Get Your Agent's Slack Command

In Gumloop, navigate to the Agents page and click on the agent you want to add to Slack.

Gumloop Agents page showing list of agents

You have two options to get the Slack command:

Option 1: Use “Connect to Slack” Button (Recommended)

Click the “Connect to Slack” button in the left sidebar menu:

This opens a dialog that provides the complete /gummie add command. Click the copy button to copy the entire command:

Connect to Slack modal with copy command button

This is the fastest method—it gives you the complete command ready to paste directly into Slack!

Option 2: Copy from Settings

Alternatively, you can get the agent ID from Settings:

Click the “Settings” button (gear icon) in the top right
Copy the agent ID from the settings panel

Manually create the command: /gummie add [your-agent-id]

Add Agent to Channel

Back in your Slack channel, paste the command:

/gummie add [your-agent-id]

Pasting /gummie add command in Slack channel

Press Enter. Your agent is now active in the channel!

Confirmation message that agent was successfully added

One agent per channel: Only one agent can be active in a Slack channel at a time. To switch agents, remove the current one first with /gummie remove.

Using Your Agent in Slack

Starting a Conversation

To interact with your agent, @mention it in a top-level message:

@Gumloop [your question or task]

Important: You must @Gumloop the agent for all top-level messages. The agent will not respond to messages that don’t include an @Gumloop.

The agent will:

Start a thread to keep conversations organized
Process your request using its configured tools and workflows
Respond with results and reasoning
Continue the conversation within the thread

Need custom branding? If you want your agent to appear with a custom name and avatar instead of “@Gumloop”, you can connect your own Slack app. See Custom Slack App Integration for setup instructions.

Customizing Agent Behavior in Slack

Control how your agent responds in Slack threads with these preferences, accessible in your agent’s settings under Slack Preferences:

Thread Response Trigger

When to respond to a message in a thread. This setting determines whether your agent responds to every message in a thread or only when explicitly mentioned.

On All Messages
Only on Mentions (Recommended)

How it works: Agent responds to every message in the thread, even without @Gumloop.Best for:

Active collaboration where the agent should participate in all discussion
When multiple team members are asking questions
Continuous back-and-forth conversations
Support channels where the agent acts as a primary responder

Example: After starting a thread with @Gumloop analyze this customer, any follow-up like “What about their purchase history?” will automatically trigger the agent.

How it works: Agent only responds when explicitly @mentioned in thread replies.Best for:

Allowing team discussions without agent interruption
More controlled agent participation
Channels where both human and agent input are needed selectively
Letting teams discuss agent responses before requesting follow-ups

Example: After @Gumloop analyze this customer, you can discuss the results with your team in the thread. The agent only responds again when you @Gumloop with a follow-up question.

Use this mode when your team needs to discuss the agent’s responses without triggering new responses. Simply reply in the thread without @mentioning the agent to have private team discussions.

Stream Reasoning

See the agent’s thought process as it responds to your messages. By default, this setting is disabled (recommended for cleaner threads).

When to Enable Stream Reasoning

Disabled (Default - Recommended):

Agent shows only the final response
Threads remain clean and focused
Best for most production use cases
Team members see polished answers without technical details

Enabled:

Shows real-time reasoning as the agent processes your request
Displays each tool call, decision, and intermediate step
Useful for debugging agent behavior
Helps understand how the agent arrived at conclusions

Keep this disabled unless you need debugging visibility. Most users prefer cleaner threads without the technical reasoning details. Enable only when you want complete transparency into the agent’s decision-making process.

Example of streamed reasoning:

🤔 Analyzing the customer request...
🔍 Searching CRM for customer ID #12345...
✅ Found customer record
🔍 Checking purchase history in database...
📊 Analyzing 15 transactions from past 6 months...
💡 Generating summary...

versus just the final response:

Customer #12345 has made 15 purchases totaling $3,450 
over the past 6 months. Their average order value is $230.

Hide Workflow Run Results

Hide the view full workflow results button while chatting. By default, this setting is disabled, showing workflow run details in threads.

Understanding Workflow Run Results

When your agent uses workflows (workflows) to complete tasks, Gumloop can show a “View full workflow results” button in the thread along with workflow run details.Disabled (Default):

Shows “View full workflow results” button in thread
Displays workflow run metadata
Provides transparency into which workflows were triggered
Useful for debugging and understanding automation workflow

Enabled (Cleaner Threads):

Hides the workflow button and run details
Agent simply returns with its response
Creates cleaner, more conversational threads
Recommended when team doesn’t need workflow visibility

Enable this setting for cleaner threads. Most end users don’t need to see workflow execution details—they just want the agent’s answer. This makes conversations feel more natural and less technical.

With workflow details shown (disabled):

Agent: I've processed the customer data.

[View full workflow results →]
Workflow: Customer Analysis Pipeline
Run ID: abc123xyz
Duration: 3.2s
Status: ✅ Completed

Result: Customer is eligible for discount tier 2

With workflow details hidden (enabled):

Agent: I've processed the customer data.

Result: Customer is eligible for discount tier 2

These settings can be changed anytime in your agent’s Slack preferences. Changes take effect immediately for new conversations.

Thread Organization

Agents automatically organize conversations into threads:

New @mentions → Create new threads
Replies in threads → Continue the same conversation with full context
Multiple team members → Can jump into any thread to ask follow-ups

This keeps channels organized and makes it easy to track agent conversations.

Thread Commands

Control agent behavior within a thread using these commands:

Command	What It Does
`!stop`	Stop the agent’s current response and prevent further replies in this thread
`!link`	Get an ephemeral link to view the conversation in Gumloop

Using !stop Type !stop in the thread to end the conversation. The agent will acknowledge by reacting with a thumbs up emoji (👍) and will not send any further replies in that thread.

!stop

This is useful when:

You’ve gotten the information you need and don’t want additional responses
The agent is processing something you no longer need
You want to end the conversation cleanly without triggering another reply

Using !link Type !link in the thread to get a temporary link to view the full conversation in Gumloop. The link is ephemeral (only visible to you) and lets you see the complete conversation history, tool calls, and credit usage.

!link

This is useful when:

You want to review the agent’s reasoning in more detail
You need to share the conversation with someone outside Slack
You want to see credit costs for the conversation

Image Generation in Slack

When your agent generates images using the Image Generation tool, both the image file and a link to the image are sent directly in the Slack thread. This makes it easy to view the generated image inline and also access or share the image URL. To enable image generation for your agent, add the Image Generation tool in the agent builder under Tools → Add Image Generation Tool:

Add Image Generation Tool option in agent Tools section

Image generation costs 30 credits per image regardless of the model used (DALL-E 3, Gemini 2.5 Flash, Gemini 3 Pro, or GPT-Image-1). This is charged in addition to the agent’s normal model costs.

Credentials & Authentication

How Authentication Works

When you interact with an agent in Slack, the agent uses your personal default credentials (unless workspace credentials are configured)—not the agent creator’s credentials. This ensures proper access control and data privacy.

For Existing Gumloop Users

If your Slack email matches your Gumloop account:

The agent automatically uses your personal default credentials
You have immediate access to all tools and workflows you’re authorized to use
No additional setup required

Example: If the agent uses Gmail and Google Calendar, it will access your personal Gmail and Calendar using your authenticated credentials.

For Non-Gumloop Users

If you’re not yet a Gumloop user, you’ll see a signup prompt the first time you try to use an agent:

What happens:

Agent responds with a message asking you to sign up
Click the link to create your Gumloop account using your Slack email
After signing up, authenticate with the services the agent needs
Return to Slack and @Gumloop the agent again

You must use the same email address for Slack and Gumloop for the integration to work properly.

Missing Credentials

If the agent needs a credential you haven’t set up yet:

The agent will notify you about the missing authentication
Visit your Gumloop credentials page
Authenticate with the required service
Return to Slack and retry your request

Example: If an agent uses Google Calendar but you haven’t authenticated, you’ll get a message like:

⚠️ I need access to Google Calendar to complete this task. 
Please authenticate at: https://www.gumloop.com/settings/profile/credentials

Personal vs Workspace Agents

Recommendation: Always create agents in your personal workspace unless you need shared workspace credentials or team collaboration features.

Personal Agents (created in personal workspace):

Anyone in the Slack channel can use the agent
Each user’s request runs on their own personal credentials
Non-Gumloop users will be prompted to sign up
Best for most use cases

Workspace Agents (created in shared workspace):

Access control: Only members of that specific Gumloop workspace can use the agent
Credential behavior: If an MCP integration or credential is set to use “workspace default,” the workspace credentials are used instead of personal credentials
Non-workspace members will receive an access denied message

Learn more about the differences between personal and shared workspaces in the Organizations and Workspaces documentation.

Key Differences Summary

Feature	Personal Agent	Workspace Agent
Who can use it?	Anyone in Slack channel	Only workspace members
Credentials used	Always personal default	Personal default OR workspace default (if configured)
Best for	General use, maximum accessibility	Team collaboration with shared credentials

Using Workspace Credentials with Agents

If you want team members to use your agent without requiring them to set up their own credentials, you can configure the agent to use workspace credentials. This is particularly useful when you want to share an agent with your team and have everyone use the same authenticated accounts.

Team or Enterprise plan required: Workspaces are available on Team and Enterprise plans only.

Create or Select a Workspace

First, ensure you have a workspace set up. You can check your existing workspaces or create a new one from the hub page by clicking the workspace dropdown and selecting ”+ Add a workspace”.

Alternatively, you can use your organization’s default workspace, which automatically includes all organization members. Find it in your organization settings under the General tab.

Default workspace in organization settings

Move the Agent to the Workspace

From the hub page, find your agent and click the three-dot menu. Select “Move to Workspace” and choose the workspace you want to use.

Add Workspace Credentials

Open the workspace settings by navigating to the workspace and clicking on “Workspace Credentials” in the left sidebar. Add the credentials that your agent needs (e.g., Gmail, Google Drive, Salesforce).

Members of your workspace will be able to use the integrations you link here through workflows and agents.

Configure Agent to Use Workspace Credentials

In your agent’s settings, switch each integration from “Use Personal Default” to “Use Workspace Default”. Click the three-dot menu next to each integration and select the workspace credential option.

Switch agent to use workspace credentials

Important: When an agent is in a workspace, users invoking the agent must also be members of that workspace. Otherwise, they will not be able to use the workspace credentials or invoke the agent. To avoid manually adding users, use your organization’s default workspace which automatically includes all members.

Data Privacy & Security

Your Data Stays Private

When you use an agent with personal credentials, only your authenticated credentials are used. Other team members cannot access your personal data through the agent.

Controlled Access

Admin security controls and user roles in Gumloop apply to agents just like they do to workflows. You can only access what you’re authorized to access.

Managing Agents in Slack

Use these slash commands to manage agents in your channels:

View Active Agent
Remove Agent
Get Help

Check which agent is active in the current channel:

/gummie active

This displays:

Agent name
Agent ID
Who added it
When it was added

Remove the agent from the current channel:

/gummie remove

Confirms removal and frees up the channel to add a different agent.

See all available commands:

/gummie help

Displays the complete list of Slack commands and their usage.

Remember: Only one agent can be active per channel. To switch agents, use /gummie remove first, then add the new agent with /gummie add [agent-id].

Quick Reference: Slack Commands

Channel Commands (Slash Commands)

Command	What It Does	Example
`/invite @Gumloop`	Add Gumloop bot to the channel	`/invite @Gumloop`
`/gummie add [agent-id]`	Add an agent to the current channel	`/gummie add gMPSaB1Jjuo34XtwbTo2br`
`/gummie remove`	Remove the agent from the current channel	`/gummie remove`
`/gummie active`	Show which agent is active in this channel	`/gummie active`
`/gummie help`	Show all available commands	`/gummie help`

Thread Commands (Type in a thread with an active agent)

Command	What It Does
`!stop`	Stop the agent’s current response and prevent further replies
`!link`	Get an ephemeral link to view the conversation in Gumloop

Thread response mode is configured in your agent’s Slack settings in Gumloop, not via slash commands.

Best Practices

Choose the Right Channels

Deploy agents strategically to appropriate channels:Supported channel types:

✅ Public channels
✅ Private channels
❌ Direct messages (DMs) - Not supported

Example deployments:

#support: Customer service agents with ticket triage capabilities
#sales: Lead research and enrichment agents
#marketing: Campaign planning and content strategy agents
#data: Data analysis and reporting agents

Match agent capabilities to channel purpose for maximum adoption.

Set Channel Expectations

When adding an agent to a channel, post a message explaining:

📢 New Agent Alert!

I've added our "Support Bot" agent to this channel.

What it can do:
• Look up customer tickets in Zendesk
• Check user eligibility for discounts
• Pull order history from Salesforce

How to use it:
@Gumloop [your question]

Example: "@Gumloop Check if ticket #12345 is eligible for a discount"

💡 Remember: You must @Gumloop the agent in all top-level messages!

This reduces friction and encourages proper usage.

Use Descriptive Agent Names

When your team @mentions “@Gumloop”, they’re interacting with whichever agent is active in that channel.Use clear agent names in your Gumloop workspace:

✅ “Support Ticket Assistant”
✅ “Sales Lead Researcher”
✅ “Marketing Campaign Planner”
❌ “Agent 1”
❌ “My Bot”

Team members can check which agent is active with /gummie active.

Configure Thread Response Mode Appropriately

Choose the right thread response mode in your agent’s Slack settings:

“On all messages”: Best for agents that should participate in every reply
- Support bots that need to track all conversation
- FAQ agents that should answer follow-up questions
- Active collaboration scenarios
“Only on mentions” (Recommended): Best for most use cases
- Research assistants used occasionally
- Agents where teams need to discuss responses
- Controlled agent participation

This prevents unwanted interruptions and makes agent behavior more predictable.

Monitor Usage Patterns

Watch how your team uses agents in Slack:

Which questions get asked most frequently?
Where do agents struggle or give poor responses?
What workflows are called most often?

Use these insights to:

Refine agent instructions
Add new tools and workflows
Improve response accuracy
Create training materials for your team

You can view all agent conversations in the agent’s settings page in Gumloop.

Ensure Credentials Are Set Up

Before deploying an agent to a team channel:

Test the agent with your own credentials
Document which services team members need to authenticate with
Share the credentials page link
Consider creating a setup guide specific to your agent

This prevents confusion when team members first try to use the agent.

Combine with Workflow Triggers

For maximum automation, combine agents with Slack triggers:Agent: Handles ad-hoc questions in #support Workflow Trigger: Automatically processes every new message for loggingThis gives you both interactive AI assistance and automated data capture.

Troubleshooting

Agent Doesn't Respond to Top-Level Messages

Check:

✅ Did you @Gumloop the agent? Top-level messages require @mentions
✅ Is Gumloop added to the channel? (/invite @Gumloop)
✅ Is an agent added to this channel? (Run /gummie active to verify)
✅ Is this a public or private channel? (Agents don’t work in DMs)
✅ Have you authenticated with the required services?

Always use @Gumloop [your message] format for top-level messages—the agent won’t see messages without @mentions!

Agent Doesn't Respond in Threads

If the agent isn’t responding to thread replies:Check thread response mode:

If set to “Only on mentions”: You must @mention the agent in each thread reply
If set to “On all messages”: The agent should respond to every message

Verify the setting in Gumloop → Agent Settings → Slack → Thread Response Trigger

Signup Prompt for Existing Users

Authentication Errors

If you get messages about missing credentials:

Visit your credentials page
Authenticate with the required service
Return to Slack and retry

For personal agents, make sure your personal default credentials are set. For workspace agents using workspace credentials, contact your workspace admin.

Wrong Agent Responding

Only one agent can be active per channel. If the wrong agent is responding:

Check active agent: /gummie active
Remove current agent: /gummie remove
Add correct agent: /gummie add [correct-agent-id]

Can't Add Agent to Channel

If you’re unable to add an agent:

✅ Verify channel type: Agents work in public and private channels, but not in DMs
✅ Check Gumloop is invited: Run /invite @Gumloop in the channel first
✅ Confirm permissions: Ensure you have permission to add apps to the channel
✅ Check agent ID: Verify you copied the complete agent ID from Gumloop

Agent Responses Too Slow

Agents may take longer when:

Calling multiple workflows
Using complex integrations
Processing large amounts of data

Solutions:

Optimize workflows to use fewer AI nodes
Limit agent tools to only what’s necessary
Use faster AI models in agent settings
Break complex tasks into smaller agent interactions

Can't Find Agent ID

To get your agent’s Slack command:Easiest method: Click “Connect to Slack” button in the agent menu and copy the commandAlternative:

Go to gumloop.com/hub?view=agents
Click on your agent
Click “Settings” (gear icon)
Copy the agent ID from the settings panel

The command format is /gummie add [agent-id]—always copy from Gumloop rather than typing manually!

Example Use Cases

Support Channel
Sales Channel
Data Channel

Agent: Support Ticket AssistantChannel: #customer-support (public channel)Common interactions:

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

Team member (in thread): "What about ticket #12346?"
Agent (if "On all messages"): [Automatically checks ticket #12346]
Or (if "Only on mentions"): [Waits for @mention]

Team member: "@Gumloop Pull the last 5 interactions with [email protected]"
Agent: [Searches CRM and email, returns history]

Why it works: Support team gets instant access to information without leaving Slack. Every interaction teaches the team how to use the agent for similar queries.Setup tip: Use “On all messages” mode for support channels to maintain conversation flow.

Agent: Lead Research AssistantChannel: #sales-team (public channel)Common interactions:

Team member: "@Gumloop Research this company: [LinkedIn URL]"
Agent: [Enriches lead, checks CRM for activity, drafts outreach]

Team member (in thread): "Thanks! What's the best time to reach out?"
(With "Only on mentions" - no agent response, allows team discussion)

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

Why it works: Sales reps get instant research without switching tools. Newer reps learn by watching experienced reps use the agent.Setup tip: Use “Only on mentions” mode to allow sales discussions without agent interruption.

Agent: Data Analysis AssistantChannel: #data-team (private channel)Common interactions:

Team member: "@Gumloop Compare Q4 revenue vs Q3 by product line"
Agent: [Runs BigQuery workflow, generates comparison]

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

Team member: "@Gumloop Flag any anomalies in yesterday's user signups"
Agent: [Analyzes data, identifies outliers, reports findings]

Why it works: Analysts get quick answers to data questions. Non-technical team members learn what data is available and how to access it.Setup tip: Works in private channels too! Use “Only on mentions” for controlled analysis requests.

Important Limitations

One Agent Per Channel

Only one agent can be active in a Slack channel at a time. Use /gummie remove before adding a different agent.

No Direct Messages

Agents cannot be added to direct messages (DMs)—only public or private channels work.

Channel Access Required

Gumloop must be invited to the channel with /invite @Gumloop before adding an agent.

Top-Level Mentions Required

You must @mention the agent in all top-level messages. Thread behavior depends on the response mode setting.

Credentials Depend on Agent Type

Personal agents always use your personal default credentials. Workspace agents may use workspace credentials if configured.

Email Matching Required

Your Slack email must match your Gumloop account email for the integration to work.

Next Steps

Build Your First Agent

Learn how to create and configure agents in Gumloop

Browse Agent Templates

Explore pre-built agents you can deploy to Slack immediately

Agents Course

Watch video tutorials on agents and Slack integrations

Get Started

Core Concepts

Enterprise Features

Nodes

Common Errors

​Why Use Agents in Slack?

Shared Learning

Natural Integration

Collaborative Usage

Instant Adoption

​Adding an Agent to Slack

​Option 1: Use “Connect to Slack” Button (Recommended)

​Option 2: Copy from Settings

​Using Your Agent in Slack

​Starting a Conversation

​Customizing Agent Behavior in Slack

​Thread Response Trigger

​Stream Reasoning

​Hide Workflow Run Results

​Thread Organization

​Thread Commands

​Image Generation in Slack

​Credentials & Authentication

​How Authentication Works

​Key Differences Summary

​Using Workspace Credentials with Agents

​Data Privacy & Security

Your Data Stays Private

Controlled Access

​Managing Agents in Slack

​Quick Reference: Slack Commands

​Channel Commands (Slash Commands)

​Thread Commands (Type in a thread with an active agent)

​Best Practices

​Troubleshooting

​Example Use Cases

​Important Limitations

One Agent Per Channel

No Direct Messages

Channel Access Required

Top-Level Mentions Required

Credentials Depend on Agent Type

Email Matching Required

​Next Steps

Build Your First Agent

Browse Agent Templates

Agents Course

Why Use Agents in Slack?

Adding an Agent to Slack

Option 1: Use “Connect to Slack” Button (Recommended)

Option 2: Copy from Settings

Using Your Agent in Slack

Starting a Conversation

Customizing Agent Behavior in Slack

Thread Response Trigger

Stream Reasoning

Hide Workflow Run Results

Thread Organization

Thread Commands

Image Generation in Slack

Credentials & Authentication

How Authentication Works

Key Differences Summary

Using Workspace Credentials with Agents

Data Privacy & Security

Managing Agents in Slack

Quick Reference: Slack Commands

Channel Commands (Slash Commands)

Thread Commands (Type in a thread with an active agent)

Best Practices

Troubleshooting

Example Use Cases

Important Limitations

Next Steps