Slack
Slack credentials are essential for authenticating with Slack services in your Boltic workflows. Whether you're setting up triggers to listen for Slack events or activities to send messages, proper credential configuration is the foundation of your Slack integration.
Overview
Slack integration in Boltic enables you to:
- Listen for events in your Slack workspace (messages, mentions, reactions)
- Send messages to channels and users
- Manage channels and workspace interactions
- Automate workflows based on Slack activities
How to Add Slack Credentials
There are two ways to configure Slack credentials in Boltic:
Method 1: From Trigger/Activity Configuration
- When configuring a Slack Trigger or Slack Activity
- Click "Add New" next to the Slack Credentials field
- Fill the authentication form and save
Method 2: From Boltic Dashboard
- Navigate to Boltic Dashboard
- Click on "Integrations"
- Go to "Sources" section
- Click "Add New Source"
- Search for "Slack" and select it
- Complete the authentication setup
Setting up credentials from the Dashboard allows you to reuse the same configuration across multiple workflows.
Authentication Methods
Boltic provides two authentication methods for Slack integration:
1. OAuth (Recommended)
Best for: Most users, especially those new to Slack integrations
How it works:
- Click the OAuth option during setup
- You'll be redirected to Slack's authorization page
- Accept the requested permissions
- Automatically redirected back to Boltic with credentials saved
Advantages:
- ✅ Simple setup - No manual token management
- ✅ Automatic scope handling - Boltic requests only necessary permissions
- ✅ Secure authentication - OAuth2 standard security
- ✅ Easy revocation - Can be revoked directly from Slack settings
When to use:
- Quick setup for standard use cases
- Teams without dedicated Slack app requirements
- When you want Boltic to handle permission management
2. Access Token (Advanced)
Best for: Advanced users with custom Slack apps
How it works:
- Create your own Slack app
- Generate a bot token from your app
- Manually enter the token in Boltic
Advantages:
- ✅ Full control - Manage your own Slack app
- ✅ Custom permissions - Configure exactly the scopes you need
- ✅ Enterprise compliance - Use your organization's Slack app
- ✅ Advanced features - Access to all Slack API capabilities
When to use:
- Need specific scopes not covered by OAuth
- Enterprise environments with strict app policies
- Custom branding requirements (your app name/icon)
- Advanced Slack API features
Setting Up Access Token Method
If you choose the Access Token method, follow these detailed steps:
Step 1: Create a Slack App
- Go to Slack API: Your Apps
- Click "Create New App"
- Choose "From scratch"
- Provide:
- App Name: Choose a descriptive name (e.g., "Company Boltic Integration")
- Workspace: Select your target Slack workspace
- Click "Create App"
Step 2: Configure Bot Token Scopes
- In your app settings, navigate to "OAuth & Permissions"
- Scroll to "Scopes" section
- Under "Bot Token Scopes", add the required scopes:
Essential Scopes for Basic Functionality
app_mentions:read - Detect app mentions
channels:history - Read public channel messages
channels:read - Access public channel info
chat:write - Send messages
groups:history - Read private channel messages
groups:read - Access private channel info
users:read - Read user information
Additional Scopes for Advanced Features
channels:manage - Manage public channels
groups:write - Manage private channels
users:read.email - Access user email addresses
For the complete list of required scopes and their purposes, see our Slack Scopes Reference.
Step 3: Install App to Workspace
- Click "Install App to Workspace"
- Review the permissions
- Click "Allow" to authorize
Step 4: Copy Bot Token
- After installation, you'll see the "Bot User OAuth Token"
- Copy the token (starts with
xoxb-
) - Keep this token secure - treat it like a password
Step 5: Configure in Boltic
- Return to your Boltic credential setup
- Select "Access Token" method
- Paste your bot token
- Save the configuration
Security Best Practices
Token Management
- Never share bot tokens in code repositories or documentation
- Rotate tokens regularly for enhanced security
- Use environment-specific apps for dev/staging/production
- Monitor token usage and revoke unused tokens
Access Control
- Grant minimum required scopes - only add scopes you actually need
- Regular audit - review which channels your bot has access to
- Remove from unused channels - clean up bot presence periodically
- Monitor bot activity - check logs for unauthorized usage
Workspace Security
- Verify app installations - ensure only authorized apps are installed
- Review app permissions - audit what data apps can access
- Use Slack's native security features - enable 2FA, SSO where available
Troubleshooting
Common Issues
1. Invalid Token Error
Problem: "Invalid auth token" or similar authentication errors
Solutions:
- Verify token starts with
xoxb-
(bot token) - Check token wasn't truncated when copying
- Ensure app is installed in the correct workspace
- Verify token hasn't been revoked
2. Missing Scope Errors
Problem: missing_scope
errors during workflow execution
Solutions:
- Check the required scopes list
- Add missing scopes in your Slack app's OAuth settings
- Reinstall the app after adding scopes
- Verify scopes match your workflow requirements
3. OAuth Redirect Issues
Problem: OAuth flow doesn't complete or redirects to wrong page
Solutions:
- Ensure you're using a supported browser
- Check for popup blockers
- Clear browser cache and cookies
- Try incognito/private browsing mode
4. Bot Not Receiving Events
Problem: Triggers not firing despite proper setup
Solutions:
- Verify bot is added to relevant channels (
/invite @YourBot
) - Check webhook URL is configured correctly in Slack app
- Ensure app has required event subscriptions enabled
- Validate workflow is enabled and properly configured
Getting Help
If you continue experiencing issues:
- Check workflow logs - Look for specific error messages
- Verify Slack app settings - Ensure all configurations match requirements
- Test with simple workflows - Start with basic message sending
- Review Slack's API documentation - For advanced troubleshooting
Credential Management
Updating Credentials
- OAuth: Re-authorize through the OAuth flow to refresh
- Access Token: Generate new token and update in Boltic
Sharing Credentials
- Credentials can be shared across multiple workflows
- Use descriptive names for easy identification
- Consider creating separate credentials for different environments
Backup and Recovery
- Document your setup - Keep records of app configurations
- Export important settings - Save Slack app configurations
- Test restore procedures - Ensure you can recreate setups if needed
Next Steps
Once your Slack credentials are configured:
- Set up Slack Triggers - Learn how to create Slack triggers
- Configure Slack Activities - Send messages and manage channels
- Test your integration - Start with simple workflows
- Monitor performance - Check logs and optimize as needed
Start with OAuth for quick setup, then consider migrating to Access Token method if you need advanced features or custom branding.