Slack Integration

Learn how to collect evidence from Slack using Strike Graph's flexible Bridge integration

Written By Micah

What is the Slack Integration?

The Slack integration allows you to use Strike Graph's Bridge-style integration to collect evidence directly from Slack's Web API for your compliance needs. This integration uses OAuth authentication through the standard "Add to Slack" authorization flow, connecting your Slack workspace to Strike Graph so you can collect evidence of your team's communication policies, user access, and channel activity.

With this integration, you can gather evidence from your Slack workspace, including:

  • Workspace member lists and user details

  • Channel listings and membership

  • Message history from specific channels

  • User group configurations

  • Team and workspace information

Evidence collection is read-only: Strike Graph will never post messages, modify channels, or make changes to your Slack workspace.

Two Ways to Collect Evidence from Slack

The Slack integration supports two evidence collection methods:

Slack API requests let you call specific Slack Web API methods and collect the response as evidence. This approach gives you full control over exactly which endpoint to call and what parameters to include.

Script Runner provides curated, pre-built scripts that handle common evidence collection scenarios. Scripts can combine multiple API calls, filter and format the output, and produce evidence that is ready for auditor review. Script Runner is equally powerful to direct API requests and is often the faster path to well-formatted evidence.

If your organization has access to Script Runner, both options appear as tabs when you attach evidence using this integration.

Setting Up the Slack Integration

Prerequisites

  • A Slack workspace where you have permission to install apps

  • Appropriate permissions within Strike Graph to manage integrations

Connect your Slack workspace

  1. Navigate to Integrations in the main Strike Graph menu.

  2. Find the Slack integration card and click Add Integration.

  3. You'll be redirected to Slack to authorize Strike Graph.

  4. Sign in to your Slack account if prompted.

  5. Select the Slack workspace you want to connect and click Allow.

  6. You'll be redirected back to Strike Graph with the integration now active.

Once connected, your Slack integration will appear in the integration list with an "Active" status. Each workspace requires its own connection, so if you need to collect evidence from multiple Slack workspaces, you can add additional integrations.

Collecting Evidence Using Slack API Requests

Step 1: Select an evidence object

  1. Navigate to the evidence object where you want to add Slack data.

  2. Click the Attach button to open the attachment options (or configure Automated Collection).

  3. Select your Slack integration from the list of available sources.

Step 2: Configure your API request

The Slack evidence collection form has two main components:

HTTP Method

Slack evidence collection supports GET requests only. This ensures that evidence collection remains strictly read-only.

API Route

Enter the Slack Web API method you want to call, along with any query parameters. Review the Slack Web API documentation for the full list of available methods. Strike Graph supports a curated set of read-only methods for evidence collection.

Example API routes:

  • users.list — Get all members of the workspace

  • conversations.list?types=public_channel — Get public channels

  • conversations.history?channel=C0123456789&limit=15 — Get recent messages from a specific channel

  • conversations.members?channel=C0123456789 — Get members of a specific channel

  • team.info — Get workspace information

  • usergroups.list — Get user groups

Note: Some methods require parameters. For example, conversations.history requires a channel parameter with the channel's ID. You can find channel IDs by first running conversations.list and noting the id field for the channel you need.

Supported Slack API methods

The following Slack Web API methods are available for evidence collection:

  • auth.test — Test authentication and get workspace identity

  • conversations.history — Get message history from a channel

  • conversations.info — Get details about a channel

  • conversations.list — List channels in the workspace

  • conversations.members — Get members of a channel

  • conversations.replies — Get a thread's replies

  • emoji.list — List custom emoji

  • team.info — Get workspace information

  • usergroups.list — List user groups

  • users.conversations — List channels a user is in

  • users.getPresence — Get a user's presence status

  • users.info — Get details about a user

  • users.list — List all workspace members

Step 3: Submit your request

  1. Click Submit to execute the API request.

  2. Strike Graph will process your request and collect the data.

  3. Once complete, the evidence will be attached to your evidence object.

Collecting Evidence Using Script Runner

If your organization has Script Runner enabled, a Scripts tab will appear alongside the Slack tab when attaching evidence.

Script Runner provides pre-built scripts tailored to common compliance evidence needs. To use Script Runner:

  1. Navigate to the evidence object and open the attachment options.

  2. Select your Slack integration.

  3. Switch to the Scripts tab.

  4. Search for a script that matches your evidence needs, or describe what you're looking for.

  5. Select a script to preview its details and expected output.

Channel selection for Script Runner

Some scripts (such as the message-sample script) require you to select a Slack channel to sample from. A channel picker will appear when the selected script needs one. The channel is chosen per collection, so you can run the same script against different channels for different evidence items.

If a script requires channel access and the Strike Graph bot has not yet been invited to the channel, you'll see a prompt. To invite the bot, open the channel in Slack and run /invite @StrikeGraph, then use the Verify channel button to confirm the bot can read the channel's messages.

Most workspace-level scripts (such as listing all users or groups) do not require a channel selection and will collect data from across the entire workspace.

For more details on using Script Runner, see the Script Runner overview.

Troubleshooting

Authentication issues

If you receive authentication errors, the Slack app may have been uninstalled from your workspace or the token may have been revoked.

  1. Click the Reconnect button next to your Slack integration in the Integrations Manager.

  2. Follow the "Add to Slack" flow to reconnect your workspace.

  3. Try your evidence collection again.

Bot not in channel

If you receive a "bot not in channel" error when collecting message history or running a channel-specific script, the Strike Graph bot needs to be invited to that channel. Open the channel in Slack, run /invite @StrikeGraph, and try again.

Rate limiting

Slack enforces rate limits on API requests. If you encounter a rate limit error, wait a few minutes before trying again. This is most likely to occur when collecting large volumes of data in a short period.

Unsupported API method

Not all Slack Web API methods are available for evidence collection. If you receive an error about an unsupported method, check the list of supported methods above and verify you are using one of the allowed read-only methods.

Need More Help?

If you encounter any issues with your Slack Bridge integration or have questions about specific API methods, please contact our support team through the in-app messenger. We're here to help you make the most of your compliance automation.