@handle), connects to your workspace, and receives messages.
The good news: you don’t need to configure scopes or settings manually. The SlackHive wizard generates a complete app manifest — you just paste it into Slack and click a few buttons.
This page walks through that process in detail, and covers troubleshooting if something goes wrong.
What you’re creating
Each Slack app gives your agent:- A bot user — the
@handleyour team @mentions in channels - Socket Mode — a persistent connection that receives messages in real time (no webhooks needed, no public URL required)
- The right OAuth scopes — permissions to read messages, post replies, and add reactions
Step 1: Generate the manifest
When you’re on Step 2 of the agent creation wizard, click Generate Manifest. SlackHive creates a JSON manifest pre-configured for your agent with the correct name, scopes, and Socket Mode settings. Keep this manifest JSON ready — you’ll paste it into Slack in the next step.Step 2: Create the Slack app
Open the Slack API console
Go to api.slack.com/apps in a new browser tab. Sign in with the Slack account that has permission to install apps in your workspace.
Start creating a new app
Click the Create New App button in the top right. A dialog will appear asking how you’d like to configure your app.
Choose From an app manifest
Select From an app manifest (not “From scratch”). This lets you paste the pre-configured manifest rather than setting everything up manually.
Paste the manifest
You’ll see a text editor. Delete any existing content, then paste the manifest JSON from the SlackHive wizard. Click Next.
Step 3: Install to your workspace
Your app exists, but it’s not yet installed in your workspace.Go to OAuth & Permissions
In the left sidebar of the Slack app settings page, click OAuth & Permissions.
@your-agent-name) now exists in your workspace.
Step 4: Collect your credentials
You need three values to connect the agent in SlackHive. Here’s exactly where to find each one.Bot Token (xoxb-...)
- Go to OAuth & Permissions in the left sidebar
- Under OAuth Tokens for Your Workspace, find Bot User OAuth Token
- Copy it — it starts with
xoxb-
App Token (xapp-...)
- Go to Basic Information in the left sidebar
- Scroll down to App-Level Tokens
- Click Generate Token and Scopes
- Give it a name (e.g.
socket-mode) - Click Add Scope and select
connections:write - Click Generate
- Copy the token — it starts with
xapp-
Signing Secret
- Still on Basic Information
- Under App Credentials, find Signing Secret
- Click Show to reveal it, then copy the hex string
Step 5: Enter credentials in SlackHive
Go back to the SlackHive agent wizard (Step 3 — Credentials) and paste all three values:| Field | Value |
|---|---|
| Bot Token | xoxb-... |
| App Token | xapp-... |
| Signing Secret | The hex string from App Credentials |
Required OAuth scopes
The generated manifest includes these bot token scopes. Here’s what each one is for:| Scope | Why it’s needed |
|---|---|
app_mentions:read | Receive events when the bot is @mentioned in a channel |
channels:history | Read messages in public channels (needed for thread context) |
channels:read | List channels and get channel info |
chat:write | Post messages and replies |
groups:history | Read messages in private channels |
groups:read | List and access private channels |
im:history | Read direct messages |
im:read | Access DM channel info |
im:write | Send direct messages |
mpim:history | Read group DMs |
reactions:write | Add emoji reactions (used for “thinking” indicators while processing) |
users:read | Look up user display names (for memory and context) |
Troubleshooting
Verification failed — connection refused
Verification failed — connection refused
The most common cause is Socket Mode not being enabled.
- Go to your Slack app settings
- Click Socket Mode in the left sidebar
- Make sure the toggle is On
- Go back to SlackHive and try verifying again
Verification failed — invalid token
Verification failed — invalid token
- Check that you pasted the Bot Token (starts with
xoxb-) in the Bot Token field, not the App Token - Make sure there are no extra spaces before or after the token
- If you recently regenerated the token, make sure you copied the new one
App Token scope error
App Token scope error
The App Token must have the
connections:write scope. If you created the token without adding this scope:- Go to Basic Information → App-Level Tokens
- Click on your token name
- Add the
connections:writescope - Regenerate the token and copy the new value
Bot doesn't appear in workspace
Bot doesn't appear in workspace
If you can’t find
@your-agent-name in Slack after completing the wizard:- Check that the app was installed: go to Slack app settings → OAuth & Permissions → the Install to Workspace button should show as already installed
- In Slack, type
@in a message box and start typing the agent’s name - If it still doesn’t appear, try reinstalling the app from OAuth & Permissions
Agent is Active but not responding
Agent is Active but not responding
If the dashboard shows the agent as Active but it doesn’t respond to @mentions:
- Make sure you’ve invited the bot to the channel:
/invite @your-agent-name - Check the Logs tab on the agent — it will show if messages are being received
- Verify the agent doesn’t have channel restrictions set (Overview tab → Allowed Channels)
After setup
Once credentials are verified, the runner connects the agent to Slack automatically. The agent status changes to Active in the dashboard. Invite the bot to a channel and start a conversation:Each agent can only be installed in one Slack workspace. If you need agents in multiple workspaces, create separate Slack apps for each workspace and create separate agent entries in SlackHive.