Skip to main content Skip to complementary content
Already have an account? Sign in

Slack (v1)

Last updated: 9/15/2026

Slack integration summary

Stitch’s Slack integration replicates data from a single Slack workspace using the Slack Web API. To replicate data from multiple workspaces, create an additional Slack integration for each workspace.

Refer to the Schema section for a list of objects available for replication.

Slack feature snapshot

A high-level look at Stitch's Slack (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Beta

Supported by

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-slack

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Slack

Step 1: Create a Slack app and retrieve a verification token

Step 1.1: Create the app

  1. Navigate to the Slack App site.
  2. Click Create an App.
  3. Enter a name for the app and select the workspace you want to replicate data from.
  4. Click Create App.

Step 1.2: Grant relevant scopes to the app

Next, you’ll grant the required permissions to the app you created in the previous step.

The add permission by scope or API method menu, expanded, in the Bot Token Scopes section of the Slack App Scopes page
The add permission by scope or API method menu, expanded, in the Bot Token Scopes section of the Slack App Scopes page

  1. The app you created should be selected in the drop-down menu near the top-left corner of the page. If it isn’t, select it.
  2. Click Features > OAuth & Permissions in the left side menu.
  3. Scroll to the Scopes section.
  4. In the Bot Token Scopes section, click the Add an OAuth Scope button.
  5. In the field that appears, search for the following scopes:
    • channels:history
    • channels:join
    • channels:read
    • files:read
    • groups:read
    • links:read
    • reactions:read
    • remote_files:read
    • remote_files:write
    • team:read
    • useergroups:read
    • users.profile:read
    • users:read
    • users:read.email

    Slack will automatically save the changes each time a scope is added.

  6. Repeat steps 4 and 5 until all the scopes have been added.

Step 1.3: Install the app to your workspace

After the required scopes are added to the app, you’ll need to install it to your Slack workspace. This is required to successfully connect to Stitch.

  1. Scroll up to the OAuth Tokens & Redirect URLs section of the OAuth & Permissions page.
  2. In this section, click the Install App to Workspace button.
  3. Complete the steps that follow to install the app or submit a request to your Workspace Owner(s) for approval.

Step 1.4: Retrieve the app's bot user OAuth access token

After the app is successfully installed to your Slack workspace, a Tokens for Your Workspace section containing a Bot User OAuth Access Token field will display on the page:

The Bot User OAuth Access Token in the Tokens for Your Workspace section of the OAuth Tokens & Redirect URLs App page in Slack
The Bot User OAuth Access Token in the Tokens for Your Workspace section of the OAuth Tokens & Redirect URLs App page in Slack

Keep the token readily available for the next step.

Step 2: Add Slack as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Slack icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Slack” would create a schema called stitch_slack in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Token field, paste the bot user OAuth access token you copied from Step 1.4.
  6. Check the Join public channels box if you’d like to replicate data for all public channels in the workspace you’re connecting. Otherwise, only data for channels you’ve personally joined will be replicated.
  7. Check the Include private channels box if you’d like to replicate data for private channels in the workspace.
  8. Check the Exclude archived channels box if you don’t want to replicate data from archived channels.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Slack integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Slack’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Slack integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Slack integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab
    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Slack, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Slack replication

Workspace replication

Stitch can only replicate data from one Slack workspace at a time. In order to replicate multiple workspaces, you will need to create integrations for each workspace.

Slack table reference

channel_members

The channel_members table contain info about members of channels in your Slack workspace. Channels include conversations, channels, and direct messages in your Slack workspace.

Replication Method

Full Table

Primary Keys

channel_id

user_id

Useful links

Slack documentation

channel_members schema on GitHub

Slack API method

channels

The channels table contains info about the channels in your Slack workspace. This includes conversations, channels, and direct messages.

Note: Some types of channels - for example, private or archived channels - will be replicated only if the appropriate settings are configured in the integration’s settings. Refer to the Slack setup steps for more info.

Replication Method

Full Table

Primary Key

id

Useful links

Slack documentation

channels schema on GitHub

Slack API method

files

The files table contains info about Slack team files.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated

Useful links

Slack documentation

files schema on GitHub

Slack API method

messages

The messages table contains the history of messages and events in conversations in your Slack workspace.

Replication Method

Key-based Incremental

Primary Keys

channel_id

ts

Replication Key

ts

Useful links

Slack documentation

messages schema on GitHub

Slack API method

remote_files

The remote_files table contains info about remote files added to Slack.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated

Useful links

remote_files schema on GitHub

Slack API method

teams

The teams table contains info about teams in your Slack workspace.

Replication Method

Full Table

Useful links

teams schema on GitHub

Slack API method

threads

The threads table contains info about conversation threads in your Slack team.

Note: While this table uses Full Table, it’s not truly replicated in full during each replication job. Each time a message in a thread is updated, the entire thread and all the messages it contains will be replicated in full. This means that while only updated threads are replicated, they are replicated in full whenever they’re updated.

Replication Method

Full Table

Primary Keys

channel_id

thread_ts

Useful links

Slack documentation

threads schema on GitHub

Slack API method

user_groups

The user_groups table contains info about user groups from your Slack team.

Replication Method

Full Table

Primary Key

id

Useful links

user_groups schema on GitHub

Slack API method

users

The users table lists contains info about the users in your Slack team. This includes deactivated and deleted users.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated

Useful links

users schema on GitHub

Slack API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!