Overview
The Slack integration allows organizations to connect Slack workspaces to Engineering Metrics and collect communication and collaboration data for reporting and analytics. Using this integration, organizations can:- Connect Slack workspaces
- Authenticate using Slack API credentials
- Synchronize workspace data
- Configure Slack data scopes
- Analyze collaboration patterns
- Monitor communication metrics
Prerequisites
Before configuring the integration, ensure you have:- Access to the Engineering Metrics Dashboard
- Access to a Slack workspace
- A Slack app installed in your workspace
- A valid Slack Bot Token (
xoxb-...) - For Enterprise Grid deployments, a valid Slack User Token (
xoxp-...) if required - Appropriate permissions to install and configure Slack applications
- Required OAuth scopes configured for the Slack app
Navigate to Slack Connections
- Open the Engineering Metrics Dashboard.
- Navigate to Integration.
- Select Communication Tool Metrics.
- Choose Slack Connections.
Create a New Slack Connection
- Click New Connection.
- The Manage Connections: Slack window will appear.
Configure Connection Details
Connection Name
Enter a unique name for the Slack connection. Examples:- Engineering Workspace
- Internal Communications
- Slack Production
- Team Collaboration
Workspace Name
Enter the name of the Slack workspace. The workspace name helps identify the Slack environment being connected.Workspace ID
Enter the Slack Workspace ID. The Workspace ID uniquely identifies the Slack workspace that will be synchronized.Bot Token
Enter a valid Slack Bot Token (xoxb-...).
The Bot Token is used by Engineering Metrics to securely authenticate with the Slack API and collect workspace data.
Required Bot Token Scopes
The Slack app must be granted all required Bot Token scopes before generating and installing the Bot Token. After modifying scopes, reinstall the Slack app to apply the updated permissions.
Invite the Bot to Channels
Granting the scopes above is not enough on its own — the bot must also be a member of each channel you want tracked before it can read that channel’s history. For every channel you want Engineering Metrics to collect data from, invite the bot directly in Slack:This applies to both public and private channels. Any channel the bot hasn’t been invited to will be excluded from data collection, even if the required scopes are granted.
User Token (Enterprise Grid Only)
For Enterprise Grid workspaces, Engineering Metrics can optionally use a Slack User Token (xoxp-...) to collect additional organizational information.
Required User Token Scopes
A User Token is only required when connecting Enterprise Grid workspaces or when using custom profile field mappings.
Test the Connection
Before saving the connection:- Click Test Connection.
- Wait for the validation process to complete.
Expected Result
- If the configuration is valid, the connection test will succeed.
- If validation fails, verify the Workspace ID and Bot Token before retrying.
Save the Connection
- After successful validation, click Save Connection.
- The Slack connection will appear in the Connections list.
Configure Data Scopes
After creating the connection:- Select the Slack connection.
- Click Add Data Scope.
Only configured data scopes will be included in data collection and reporting.
Managing Data Scopes
Users can:- Add Data Scope
- Associate Scope Config
- Delete Data Scope
Understanding Data Scopes
A data scope defines the Slack workspace data that Engineering Metrics will collect and process. Configured scopes determine which communication and collaboration information becomes available for analytics.Synchronizing Slack Data
Once the connection and data scopes have been configured, Engineering Metrics begins collecting data from the Slack workspace. Collected information may include:- Workspace activity
- User participation metrics
- Communication trends
- Collaboration insights
- Team engagement data
Monitoring Communication Metrics
After synchronization, collected Slack data can be used to analyze:- Team collaboration trends
- Communication activity
- Workspace engagement
- Participation metrics
- Organizational communication patterns
Troubleshooting
Connection Test Failed
Possible causes:- Invalid Bot Token
- Missing required OAuth scopes
- Incorrect Workspace ID
- Slack app has not been reinstalled after permission changes
- Insufficient permissions
- Network connectivity issues
- Verify the Bot Token.
- Confirm the Workspace ID.
- Ensure all required OAuth scopes have been granted.
- Reinstall the Slack app after updating permissions.
- Retry the connection test.
Data Not Appearing
Possible causes:- Missing permissions
- Data scopes not configured
- Bot not invited to the relevant channels (
/invite @your-app-name) - Synchronization delay
- Verify scope configuration
- Confirm Slack permissions
- Confirm the bot has been invited to every channel you expect data from
- Allow time for synchronization to complete
Synchronization Issues
Possible causes:- Authentication failures
- API access restrictions
- Invalid credentials
- Verify connection settings
- Confirm token validity
- Re-test the connection
Best Practices
- Use descriptive connection names.
- Grant only the required OAuth scopes.
- Reinstall the Slack app whenever OAuth scopes are modified.
- Invite the bot to every channel you want tracked.
- Configure only the required data scopes.
- Regularly validate Slack credentials.
- Monitor synchronization activity regularly.
- Review communication analytics periodically.

