Slack Setup
Slack Setup
Slack integration is ideal for business teams and enterprise workflows. This guide covers the complete setup process for connecting your AI employee to Slack.
Works with both PicoClaw and Moltis.
What You'll Need
- A Slack workspace where you have admin permissions
- ~15 minutes for setup
Important: Moltis uses Socket Mode for Slack, not webhooks. This means Moltis requires an App-Level Token (app_token) in addition to the Bot Token. PicoClaw can optionally use Socket Mode viaapp_tokenas well.
Step 1: Create Slack App
Open Slack API
- Go to api.slack.com/apps
- Click Create New App
- Choose From scratch
Configure App
- Enter an App Name (e.g., "AI Assistant")
- Select your Workspace
- Click Create App
Step 2: Configure Bot Permissions
Add Bot Token Scopes
- In your app settings, go to OAuth & Permissions
- Scroll to Scopes section
- Under Bot Token Scopes, add:
| Scope | Purpose |
|---|---|
chat:write | Send messages |
channels:history | Read public channel messages |
groups:history | Read private channel messages |
im:history | Read direct messages |
im:write | Send direct messages |
app_mentions:read | Respond to @mentions |
users:read | Get user information |
Step 3: Enable Socket Mode (Required for Moltis)
Moltis Slack integration uses Socket Mode instead of webhook-based event subscriptions. PicoClaw can also use Socket Mode if an app_token is provided.
Generate App-Level Token
- In your app settings, go to Basic Information
- Scroll down to App-Level Tokens
- Click Generate Token and Scopes
- Give it a name (e.g., "socket-mode")
- Add the scope:
connections:write - Click Generate
- Copy the token (starts with
xapp-)
Important: Save this token immediately. This is your app_token and is required for Moltis.Enable Socket Mode
- Go to Socket Mode in the left sidebar
- Toggle Enable Socket Mode to On
Step 4: Subscribe to Events
Configure Events
- Go to Event Subscriptions
- Toggle Enable Events to On
Note: With Socket Mode enabled, you do not need to provide a Request URL. Slack routes events through the WebSocket connection.
Subscribe to Bot Events
Under Subscribe to bot events, add:
| Event | Purpose |
|---|---|
message.channels | Messages in public channels |
message.groups | Messages in private channels |
message.im | Direct messages |
app_mention | When bot is @mentioned |
Save Changes
Click Save Changes at the bottom of the page.
Step 5: Install App to Workspace
Install the App
- Go to Install App in the sidebar
- Click Install to Workspace
- Review the permissions
- Click Allow
Copy Bot Token
After installation, you'll see:
- Bot User OAuth Token -- Copy this token
The token starts with xoxb-
Step 6: Get Your User ID
Find Your Slack User ID
- In Slack, click on your profile picture
- Click Profile
- Click the More (...) button
- Click Copy member ID
Step 7: Configure in MakersFuel
Configuration fields differ depending on your claw type.
PicoClaw Fields
| Field | Description |
|---|---|
| bot_token | The xoxb- token from Slack |
| app_token | The xapp- App-Level Token (optional, enables Socket Mode) |
| allow_from | Comma-separated Slack member IDs (leave empty to allow all) |
Moltis Fields
| Field | Description |
|---|---|
| account_id | Bot Name (display name) |
| bot_token | The xoxb- token from Slack |
| app_token | The xapp- App-Level Token (required for Socket Mode) |
| dm_policy | Who can DM the bot: open, allowlist, or disabled |
| allowlist | List of allowed Slack member IDs (used when dm_policy is allowlist) |
Critical: Moltis Slack requires theapp_tokenfield. Without it, the Slack channel will not connect. PicoClaw can work withoutapp_tokenbut gains Socket Mode capability if one is provided.
DM Policy (Moltis)
| Policy | Behavior |
|---|---|
| open | Anyone in the workspace can message the bot |
| allowlist | Only users listed in the allowlist can message the bot |
| disabled | DMs are disabled |
Setup Steps
- Go to your employee's configuration page
- Find the Channels section
- Click Add Channel or enable Slack
- Fill in the fields for your claw type
- Click Save to apply the configuration
Step 8: Invite Bot to Channels
Add to Channels
Your bot needs to be invited to channels where you want it to work:
- Open the channel in Slack
- Type
/invite @YourBotName - Or click the channel name -> Integrations -> Add apps
Start Chatting
Test your bot:
- @mention the bot:
@YourBot hello! - Send a direct message to the bot
- Use slash commands if configured
Features
Slash Commands
You can configure custom slash commands for your bot.
| Feature | Description |
|---|---|
| Custom commands | Define in Slack app settings |
| Auto-responses | Triggered by slash commands |
| Parameters | Commands can accept input |
Message Types
| Type | Supported |
|---|---|
| Text messages | Yes |
| Rich formatting | Yes (Block Kit) |
| Files | Yes |
| Threads | Yes |
| Reactions | Yes |
Thread Support
Your bot can respond in threads:
- Maintains conversation context
- Keeps channels organized
- Reference parent messages
Configuration Reference
PicoClaw Access Control
PicoClaw uses the allow_from field:
| Setting | Description |
|---|---|
| Single user | Enter one member ID |
| Multiple users | Comma-separated IDs |
| All users | Leave empty (responds to anyone) |
Moltis Access Control
Moltis uses dm_policy and allowlist:
| Setting | Description |
|---|---|
| Open | Set dm_policy to open |
| Restricted | Set dm_policy to allowlist and add member IDs to allowlist |
| Disabled | Set dm_policy to disabled |
Channel Restrictions
Control where the bot responds:
- Invite bot only to specific channels
- Use Slack's permissions to restrict access
- Configure via workspace admin settings
Troubleshooting
"Bot not responding"
- Check scopes -- Ensure all required scopes are added
- Check app_token -- Moltis requires the
xapp-App-Level Token - Check Socket Mode -- Ensure Socket Mode is enabled in Slack app settings
- Invite to channel -- Bot must be in the channel
- Verify events -- Check event subscriptions are configured
"Missing scope" error
- Go to OAuth & Permissions
- Add the missing scope
- Reinstall app to workspace
"Invalid token" error
- Token may have been regenerated
- Copy the new token from Install App page
- Update in MakersFuel
Events not triggering
- Verify event subscriptions are enabled
- Ensure Socket Mode is enabled (for Moltis)
- Ensure bot is invited to the channel
- Check subscribed events list
Bot can't see messages
- Requires
channels:historyorgroups:historyscope - Bot must be a member of the channel
- Check channel type (public vs private)
Moltis not connecting
- Verify
app_token(starts withxapp-) is provided - Ensure the App-Level Token has the
connections:writescope - Check that Socket Mode is toggled on in Slack app settings
Best Practices
| Practice | Why |
|---|---|
| Use minimal scopes | Security best practice |
| Test in private channel | Catch issues before public use |
| Document commands | Help team members use the bot |
| Monitor usage | Track bot activity |
Next Steps
- Employee Channels Overview -- Learn about other channels
- WhatsApp Setup -- Add WhatsApp channel
- Tools & Skills -- Extend capabilities
What did you think of this content?