Skip to main content
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

1

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.
Slack OAuth authorization screen
2

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:
  1. Type /invite @Gumloop in the channel, OR
  2. 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).
3

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:Click the “Connect to Slack” button in the left sidebar menu:
Connect to Slack button in left sidebar
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:
  1. Click the “Settings” button (gear icon) in the top left
Agent settings button location
  1. Copy the agent ID from the settings panel
Copying agent ID from settings
  1. Manually create the command: /gummie add [your-agent-id]
4

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:
  1. Start a thread to keep conversations organized
  2. Process your request using its configured tools and workflows
  3. Respond with results and reasoning
  4. Continue the conversation within the thread
Agent interaction in Slack thread

​
Thread Behavior & Response Modes

Once a thread is started, your agent’s response behavior depends on its Thread Response Mode setting:
Thread response mode settings
  • On All Messages
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
How to configure: In your agent’s Slack settings in Gumloop, select “On all messages” from the Thread Response Trigger dropdown.

​
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.

​
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.
If your Slack email matches your Gumloop account:
  1. The agent automatically uses your personal default credentials
  2. You have immediate access to all tools and workflows you’re authorized to use
  3. 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.
If you’re not yet a Gumloop user, you’ll see a signup prompt the first time you try to use an agent:
Gumloop signup prompt in Slack
What happens:
  1. Agent responds with a message asking you to sign up
  2. Click the link to create your Gumloop account using your Slack email
  3. After signing up, authenticate with the services the agent needs
  4. 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.
If the agent needs a credential you haven’t set up yet:
  1. The agent will notify you about the missing authentication
  2. Visit your Gumloop credentials page
  3. Authenticate with the required service
  4. 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
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

FeaturePersonal AgentWorkspace Agent
Who can use it?Anyone in Slack channelOnly workspace members
Credentials usedAlways personal defaultPersonal default OR workspace default (if configured)
Best forGeneral use, maximum accessibilityTeam collaboration with shared credentials

​
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
Active Gummie in Slack
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

CommandWhat It DoesExample
/invite @GumloopAdd Gumloop bot to the channel/invite @Gumloop
/gummie add [agent-id]Add an agent to the current channel/gummie add gMPSaB1Jjuo34XtwbTo2br
/gummie removeRemove the agent from the current channel/gummie remove
/gummie activeShow which agent is active in this channel/gummie active
/gummie helpShow all available commands/gummie help
Thread response mode is configured in your agent’s Slack settings in Gumloop, not via slash commands.

​
Best Practices

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.
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.
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.
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.
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.
Before deploying an agent to a team channel:
  1. Test the agent with your own credentials
  2. Document which services team members need to authenticate with
  3. Share the credentials page link
  4. Consider creating a setup guide specific to your agent
This prevents confusion when team members first try to use the agent.
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

Check:
  1. ✅ Did you @Gumloop the agent? Top-level messages require @mentions
  2. ✅ Is Gumloop added to the channel? (/invite @Gumloop)
  3. ✅ Is an agent added to this channel? (Run /gummie active to verify)
  4. ✅ Is this a public or private channel? (Agents don’t work in DMs)
  5. ✅ 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!
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
If you’re seeing a signup prompt but already have a Gumloop account:
  1. Verify your Slack email matches your Gumloop account email
  2. If different, either:
    • Update your Gumloop email to match Slack
    • Or sign in to Slack with the email used for Gumloop
  3. After matching emails, try the agent again
If you get messages about missing credentials:
  1. Visit your credentials page
  2. Authenticate with the required service
  3. 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.
Only one agent can be active per channel. If the wrong agent is responding:
  1. Check active agent: /gummie active
  2. Remove current agent: /gummie remove
  3. Add correct agent: /gummie add [correct-agent-id]
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
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
To get your agent’s Slack command:Easiest method: Click “Connect to Slack” button in the agent menu and copy the commandAlternative:
  1. Go to gumloop.com/hub?view=agents
  2. Click on your agent
  3. Click “Settings” (gear icon)
  4. 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 customer@email.com"
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.

​
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
⌘I