Skip to main content
Connect your own Slack app to a Gummie agent for custom branding, dedicated bot identity, and advanced enterprise deployments.
This is an advanced feature. For most users, we recommend using the standard Gumloop Slack integration, which is simpler to set up and works great for the majority of use cases. Only use a custom Slack app if you have specific requirements for branding, multiple agents, or enterprise compliance.

When to Use a Custom Slack App

The standard Gumloop integration (@Gumloop) is the fastest way to get agents into Slack—it works out of the box with minimal setup. However, there are scenarios where connecting your own custom Slack app makes sense:

Custom Branding

Give your agent a unique name and avatar that reflects its purpose—like “Sales Assistant” or “Support Bot” instead of “@Gumloop”

Multiple Agents, Same Workspace

Run multiple agents with distinct identities in the same Slack workspace without confusion

Enterprise Compliance

Meet IT security policies that require all Slack integrations to be owned and managed internally

White-Label Solutions

Build products or services with AI agents that appear under your brand, not Gumloop’s

Standard Integration vs Custom Slack App

AspectStandard IntegrationCustom Slack App
Bot Identity@Gumloop (shared)Your custom name & avatar
Setup ComplexitySimple (minutes)Advanced (10-15 minutes)
Slash Commands/gummie add, /gummie remove, etc.❌ Not supported
ScopePer channelPer custom app (works across all channels)
Multiple AgentsOne per channelOne per custom app
Best ForMost usersEnterprise, white-label, multi-agent setups
Start with the standard integration first. If you find you need custom branding or multiple agents later, you can always add a custom Slack app.

Prerequisites

Before setting up a custom Slack app, ensure you have:
  • Admin access to your Slack workspace (to create and install apps)
  • Permission to create Slack apps at api.slack.com

Setup Options

Gumloop offers two ways to connect a custom Slack app to your agent:
This guided flow walks you through creating a new Slack app with all the correct settings pre-configured.
1

Open External Channels

In your agent, click “External Channels” in the left sidebar menu.You’ll see the available channel integrations. Click “Connect” next to Custom Slack App.
External Channels page showing Custom Slack App option with Connect button
2

Choose New App

A modal will appear asking how you’d like to connect your Slack app. Select “New App” to create a fresh Slack app with Gumloop’s pre-configured settings.
Modal showing New App and Existing App options
3

Customize Your App

Enter the details for your custom Slack app:
  • App Name: The display name your bot will have in Slack (e.g., “Sales Assistant”, “Support Bot”)
  • App Tag: The @mention handle for your bot (e.g., @salesassistant)
  • App Description (optional): A description others will see when viewing your app in Slack
Customization modal with App Name, App Tag, and App Description fields
Choose a descriptive name that reflects what your agent does. This is what your team will see when the bot responds in Slack.
Click “Next” when you’re done.
4

Follow the Setup Guide

Gumloop provides a step-by-step setup guide with everything you need:
Setup Guide showing 5 steps to create and configure the Slack app
Here’s what to do:
  1. Copy the Slack manifest JSON — Click the “Copy” button. This manifest contains all the pre-configured permissions, scopes, and event subscriptions your app needs.
  2. Create a new Slack app — Click “Open” to go to api.slack.com/apps, then:
    • Click “Create New App”
    • Choose “From an app manifest”
    Slack App from Manifest Option
    • Select your Slack workspace
  3. Paste the manifest JSON — In the manifest editor, paste the JSON you copied from Gumloop. This automatically configures:
    Paste Gumloop's Slack Manifest Code here
    • All required bot token scopes
    • Event subscriptions with the correct webhook URL
    • Bot user settings
  4. Complete installation in Slack — Review the app settings and click “Create”, then “Install to Workspace” and authorize the app.
  5. Return to Gumloop — Come back to this page and click “Next” to continue.
5

Enter Your App Credentials

After creating your Slack app, you’ll need to provide credentials from Slack’s Basic Information page.
Credential entry form requesting Client ID, Client Secret, and Signing Secret
In your Slack app settings, go to “Basic Information” and copy:
  • Client ID — Found under “App Credentials”
  • Client Secret — Click “Show” to reveal, then copy
  • Signing Secret — Click “Show” to reveal, then copy
Credential entry form requesting Client ID, Client Secret, and Signing Secret
Never share your Client Secret or Signing Secret publicly. Treat them like passwords.
Click “Connect to Slack” to complete the OAuth flow and authorize the connection.
6

Ensure Slack App is Installed to the Workspace

Make sure your Slack app is installed to your workspace. If you skipped this step earlier, go to your Slack app settings → OAuth & PermissionsInstall to Workspace.
Install Custom Slack App
7

Invite Your Bot to Channels

Your custom bot needs to be invited to channels where you want it to work.In Slack, go to each channel and type:
/invite @YourBotName
Replace @YourBotName with the App Tag you configured (e.g., @salesassistant).
Slack channel showing bot being invited with /invite command
Your custom Slack app agent is now ready! @mention your bot to start a conversation.

Option 2: Connect an Existing App

If you already have a Slack app or need custom configurations, you can connect it directly to Gumloop.
1

Open External Channels

In your agent, click “External Channels” in the left sidebar, then click “Connect” next to Custom Slack App.
2

Choose Existing App

Select “Existing App” to connect a Slack app you’ve already created.
Modal showing New App and Existing App options
3

Configure Your Slack App (If Not Already Done)

Before connecting, ensure your existing Slack app has the required configuration:
In your Slack app settings, go to OAuth & Permissions and add these scopes:
ScopePurpose
app_mentions:readReceive @mentions of your bot
channels:historyRead messages in public channels
channels:readList available channels
chat:writeSend messages as your bot
groups:historyRead messages in private channels
groups:readList private channels
im:historyRead direct messages (if needed)
users:readLook up user information
users:read.emailMatch Slack users to Gumloop accounts
files:readAccess file attachments
reactions:writeAdd emoji reactions to messages
In your Slack app settings, go to Event Subscriptions:
  1. Toggle “Enable Events” to ON
  2. Set the Request URL to:
    https://api.gumloop.com/api/v1/external/slack/events
    
  3. Wait for verification (green checkmark)
  4. Under “Subscribe to bot events”, add:
    • app_mention
    • message.channels
    • message.groups (for private channels)
  5. Save changes
Go to OAuth & Permissions and click “Install to Workspace” if you haven’t already. Authorize the app when prompted.
4

Enter Your App Credentials

Provide the credentials from your Slack app’s Basic Information page:
Credential entry form requesting Client ID, Client Secret, and Signing Secret
  • Client ID — Found under “App Credentials”
  • Client Secret — Click “Show” to reveal, then copy
  • Signing Secret — Click “Show” to reveal, then copy
Click “Connect to Slack” to complete the OAuth flow.
5

Assign to Your Agent and Invite to Channels

Select your custom Slack app credential from the dropdown and click “Add”.Then invite your bot to channels in Slack:
/invite @YourBotName

Using Your Custom Slack App Agent

Once set up, interacting with your custom Slack app agent works similarly to the standard Gumloop integration, with a few key differences.

Starting a Conversation

@mention your custom bot in any channel where it’s been invited:
@YourBotName What are the latest support tickets?
Interaction with Custom Slack App
The agent will:
  1. Process your request using its configured tools and workflows
  2. Respond in a thread to keep conversations organized
  3. Continue the conversation within the thread based on your agent’s settings

Key Differences from Standard Integration

Custom Slack apps don’t support /gummie slash commands. You cannot use:
  • /gummie add — Bot is added by inviting to channels instead
  • /gummie remove — Remove bot by kicking from channels
  • /gummie active — You know which bot is in a channel by its name
  • /gummie help — Not available
To manage your custom app agent:
  • Add to channels: /invite @YourBotName
  • Remove from channels: /kick @YourBotName or remove via channel settings
Unlike the standard integration which is channel-specific, your custom Slack app works in any channel where it’s invited. You don’t need to “add” the agent to each channel—just invite the bot.
Your agent appears with whatever name and avatar you configured in Slack’s app settings. Team members interact with @YourBotName instead of @Gumloop.

Slack Preferences

All the same Slack preferences available for standard agents apply to custom Slack apps:
  • Thread Response Trigger: Control whether the agent responds to all messages in a thread or only when @mentioned
  • Stream Reasoning: Show or hide the agent’s thought process
  • Hide Flow Run Results: Show or hide workflow execution details
Configure these in your agent’s settings under Slack Preferences.
Slack preferences settings panel

Credential Ownership Options

When creating your custom Slack app credential, you can choose who has access:
Credential TypeWho Can Use ItBest For
PersonalOnly youTesting, personal projects
WorkspaceAll workspace membersTeam-shared agents
OrganizationAll organization membersEnterprise-wide deployments

Troubleshooting

Check these items:
  • Is the Slack app installed to your workspace? This is the most common issue. Go to your Slack app settings → OAuth & PermissionsInstall to Workspace.
    Install Custom Slack App to Workspace
  • Is the bot invited to the channel? (/invite @YourBotName)
  • Did you @mention the bot in your message?
  • Are the event subscriptions configured correctly in Slack?
  • Is the webhook URL verified? (https://api.gumloop.com/api/v1/external/slack/events)
  • Is the credential properly assigned to your agent in Gumloop?
  • Does the user have a Gumloop account with matching email?
Check:
  • Is the bot invited to the non-working channels?
  • For private channels, do you have groups:history and groups:read scopes configured?
  • Is there a different agent assigned via the standard integration in that channel?
The URL https://api.gumloop.com/api/v1/external/slack/events should verify automatically.If it fails:
  • Check for typos in the URL
  • Ensure you’re using HTTPS (not HTTP)
  • Try again after a few minutes (temporary network issues)
  • Contact Gumloop support if the issue persists
In your Slack app at api.slack.com/apps:
  • Client ID, Client Secret, Signing Secret: Found in Basic InformationApp Credentials
  • Click “Show” next to each secret to reveal it, then copy

Important Limitations

One Agent Per Custom App

Each custom Slack app credential can only be assigned to one Gummie agent. Create separate Slack apps for each agent you need.

No Slash Commands

Custom Slack apps don’t support /gummie commands. Manage your bot by inviting/removing it from channels directly.

Credential Exclusivity

A custom Slack app credential cannot be shared between multiple agents. Assigning it to a second agent removes it from the first.

Manual Channel Management

Unlike the standard integration, you must manually invite your custom bot to each channel where you want it to work.

Security Considerations

Your Slack app’s Client Secret and Signing Secret are stored securely in Gumloop and used to verify that incoming webhooks are actually from Slack. Never share these secrets or expose them in logs.
Users must have matching email addresses in Slack and Gumloop for the integration to work. This ensures proper authentication and prevents unauthorized access.
Before processing messages, Gumloop verifies:
  • The user has a valid Gumloop account
  • The user has permission to access the agent
  • For workspace agents, project membership is verified

FAQ

Yes! They operate independently. The standard bot uses channel-based mapping with /gummie commands, while custom apps use bot-based mapping with direct invites. You can have both active in different channels.
New App uses a pre-configured manifest that automatically sets up all required permissions and events—it’s faster and less error-prone. Existing App lets you connect a Slack app you’ve already created, but you’re responsible for ensuring all scopes and events are configured correctly.
The credential in Gumloop will stop working immediately. You’ll need to create a new app and set it up again.
Update these in your Slack app settings at api.slack.com/apps. Changes will reflect in Slack automatically—no changes needed in Gumloop.
Yes! This is useful when you want the same agent available in multiple Slack workspaces. Each workspace installation creates a separate credential, and you can assign all of them to a single agent.

Next Steps