Advanced Analytica Advanced Analytica: IBOM
← All connectors
Slack logo

Source connector

Slack

Set up Slack as a source and move its data into your chosen destination.

Version 3.2.28 certified generally available

Slack

Set up the Slack source connector and find its reference information on this page.

Prerequisites

Before you begin, make sure you have:

  • Administrator access to an active Slack Workspace
  • Slack App OAuth (preferred) or Bot Token

Setup guide

Step 1: Set up Slack

Follow these instructions to create a Slack app. Airbyte can only replicate messages from channels containing the app.

:::info If you’re using a Slack Bot Token, skip this section. :::

:::warning OAuth-only rate limit note: When authenticating through OAuth, the Slack source temporarily limits the Channel Messages and Threads streams after an HTTP 429 response. Each stream drops to one request per minute. The connector returns to full speed after five consecutive successful responses. Consider creating a separate connection for these streams, preventing throttling from slowing other streams. See the Rate limiting section for details.

This OAuth-specific throttle does not apply when you authenticate using a Bot Token. :::

To create a Slack App, read this tutorial or follow these instructions.

  1. Go to your Apps.
  2. Click Create New App. Select From Scratch.
  3. Name your app and select your Slack workspace. Click Create App.
  4. In the navigation menu, select OAuth & Permissions.
  5. Go to Scopes. In Bot Token Scopes, select these scopes:
 channels:history
 channels:join
 channels:read
 files:read
 groups:read
 links:read
 reactions:read
 remote_files:read
 team:read
 usergroups:read
 users:read
 users.profile:read
  1. At the top of the “OAuth & Permissions” page, click Install to Workspace. This generates a Bot User OAuth Token. Copy it for later if you’re using bot token authentication.
  2. Go to your Slack instance. For each public channel, go to Info, More, and select Add Apps.
  3. Search for your new app. If you’re using Slack’s desktop version, you may need to restart it before the new App appears. Add the App to every channel you want to sync data from.

:::note You don’t need a refresh token when authenticating to Slack with a bot token. Bot tokens never expire. Learn more about refresh tokens here. :::

Step 2: Set up the Slack connector

For Airbyte Cloud:

  1. In the navigation bar, click Sources.
  2. Click New source.
  3. Find and click Slack.
  4. Click Authenticate your Slack account. Log in and authorise Airbyte to access your Slack account.
  5. Toggle join_channels to join all public channels. Otherwise, you can sync only channels containing the bot. If unset, manually add the bot to every channel you want to sync messages from. This feature requires the channels:join OAuth scope.
6. **Start Date**: Data from before this date won't be extracted. 7. **Threads Lookback window (Days)**. This is the number of past days you want to sync data from. 8. (Optional) **Channel filter**: List the channel names without the leading `#` to limit which channels you sync. If you don't specify channels, Airbyte replicates data from all channels. 9. (Optional) **Include private channels**: Toggle on to sync data from private channels. You must manually add the bot to private channels, even when **Join all channels** is toggled on. 10. (Optional) **Include archived channels**: Toggle on to include archived channels in the sync. By default, the Slack API response excludes archived channels, reducing API calls for downstream streams. Enable this option if you need to sync data from archived channels. 11. (Optional) **Ignore messages with no replies in threads stream**: Toggle on to skip messages without replies (`reply_count=0`) in the Threads stream. This reduces unnecessary `conversations.replies` API calls and can significantly speed up syncs for workspaces with many messages. It's disabled by default, so the Threads stream contains records for every message. 12. Click **Set up source**. Add the App created in Step 1 to each channel containing data you want to sync.

For Airbyte Open Source:

  1. In the navigation bar, click Sources.
  2. Click New source.
  3. Find and click Slack.
  4. Click Sign in via Slack (OAuth). Enter the Access Token, Client ID, and Client Secret. Alternatively, enter the Bot Token from Step 1.
  5. Toggle join_channels to join all public channels. Otherwise, you can sync only channels containing the bot. If unset, manually add the bot to every channel you want to sync messages from. This feature requires the channels:join OAuth scope.
  6. Start Date: Data from before this date won’t be extracted.
  7. Threads Lookback window (Days). This is the number of past days you want to sync data from.
  8. (Optional) Channel filter: List the channel names without the leading # to limit which channels you sync. If you don’t specify channels, Airbyte replicates data from all channels.
  9. (Optional) Include private channels: Toggle on to sync data from private channels. You must manually add the bot to private channels, even when Join all channels is toggled on.
  10. (Optional) Include archived channels: Toggle on to include archived channels in the sync. By default, the Slack API response excludes archived channels, reducing API calls for downstream streams. Enable this option if you need to sync data from archived channels.
  11. (Optional) Ignore messages with no replies in threads stream: Toggle on to skip messages without replies (reply_count=0) in the Threads stream. This reduces unnecessary conversations.replies API calls and can significantly speed up syncs for workspaces with many messages. It’s disabled by default, so the Threads stream contains records for every message.
  12. Click Set up source. Add the App created in Step 1 to each channel containing data you want to sync.

Supported sync modes

The Slack source connector supports these sync modes:

FeatureSupported?
Full Refresh SyncYes
Incremental SyncYes
NamespacesNo

Supported streams

The Slack source connector uses the Conversations API for most streams.

Performance considerations

Slack rate limits restrict the connector. After an HTTP 429 response, the connector follows the Slack API’s Retry-After header. It waits for the specified duration before retrying.

Sync only the channels you need. Specify the channel_filter in the Slack configuration settings.

For large syncs, including historical data, try increasing the number of concurrent threads. The default is 2. A higher value could trigger Slack rate limits, so monitor the logs for rate-limit errors.

Data type map

Integration TypeAirbyte Type
stringstring
numbernumber
arrayarray
objectobject

Limitations and troubleshooting

Expand to see details about Slack connector limitations and troubleshooting.

Connector limitations

Rate limits

Slack has rate limit restrictions.

Channel Messages and Threads rate limits

OAuth authentication: For apps authenticated through OAuth, the connector applies a stricter budget to:

After an HTTP 429 response on these streams, the connector temporarily drops to one request per minute. After five consecutive successful responses, it automatically returns to its normal request rate. Another 429 during recovery resets the counter.

This throttle can slow syncs containing other streams. Consider creating a separate connection for Channel Messages and Threads. This prevents impacts on Users, Channels, and Channel Members.

Bot Token authentication: This OAuth-specific throttle does not apply when using a Slack Bot Token. Only Slack’s general rate limits apply. Both conversations.history and conversations.replies are Tier 3 methods, allowing at least 50 requests per minute.

Troubleshooting

  • Find common Slack source connector issues on the Airbyte Forum here.

Threads stream performance

For faster Threads stream syncs, consider enabling the Ignore messages with no replies in threads stream (threads_ignore_no_replies) option. By default, the Threads stream calls the conversations.replies API for every message, including messages without replies. In many workspaces, most messages have no replies. These unnecessary API calls consume the rate-limit budget.

  • Set to true to improve sync performance when you only need replies from messages with threaded conversations. Depending on your workspace, this can reduce API calls by up to 89%.
  • Keep as false (default) when the Threads stream must include records for every message, including unthreaded messages. This retains the current behaviour, where every message appears in the Threads stream output.

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Changelog

Expand to review
VersionDatePull RequestSubject
3.2.282026-11-1088808Update dependencies
3.2.272026-10-0688029Update dependencies
3.2.262026-09-2987330Update dependencies
3.2.252026-09-2886496Preserve thread parent checkpoints on restart and skip archived channels the bot cannot join
3.2.242026-09-2286814Update dependencies
3.2.232026-09-1586208Update dependencies
3.2.222026-09-0885654Update dependencies
3.2.212026-08-2783796Fix sync failure when the optional channel_filter config field is not set
3.2.202026-08-1884839Accept fractional epoch cursor values for the threads stream
3.2.192026-08-1884762Update dependencies
3.2.182026-08-1184106Update dependencies
3.2.172026-07-2883194Update to CDK 7.23.8 (fixes AirbyteCustomCodeNotPermittedError for bundled custom components) and remove the temporary Cloud version override
3.2.162026-07-281082Roll Cloud back to 3.2.14 — 3.2.15 is built on SDM 7.23.7, which breaks bundled custom components
3.2.152026-07-2883082Update dependencies
3.2.142026-07-2182582Update dependencies
3.2.132026-07-1482022Update dependencies
3.2.122026-06-3081255Update dependencies
3.2.112026-06-2380627Update dependencies
3.2.102026-06-1680042Update dependencies
3.2.92026-06-0979480Update dependencies
3.2.82026-06-0278986Update dependencies
3.2.72026-04-3077628Improve threads_ignore_no_replies filter to also check thread_ts, reducing unnecessary conversations.replies API calls
3.2.62026-04-3077607Improve error handling for Slack API ok=false responses: add catch-all for unrecognized errors and expand error code coverage
3.2.52026-04-2977601Surface missing OAuth scope as config error instead of silently failing channel joins
3.2.42026-04-2877531Use RATE_LIMITED action for rate-limit filters, add failure_type classification, and remove generic ok=false catch-all in favor of default HTTP status handling
3.2.32026-04-2877450Update dependencies
3.2.22026-04-2776985Allow OAuth API budget to recover after transient 429 rate limits instead of permanently throttling the sync
3.2.12026-04-2776981Remove unused OAuth scopes (im:history, mpim:history, im:read, mpim:read) not exercised by any stream. New OAuth installs see a narrower consent screen; existing tokens are unaffected.
3.2.02026-04-2776982Exclude archived channels by default; add include_archived_channels config option to opt in
3.1.242026-04-2776980Reduce channels stream page size from 1000 to 999 to comply with Slack API spec
3.1.232026-04-2476984Detect Slack API ok=false responses as errors to prevent silent data loss
3.1.222026-04-2476983Honor Slack’s Retry-After header on HTTP 429 responses for all streams
3.1.212026-04-2176477Scope the non-member channel filter to only channel_messages and threads so channel_members and channels keep syncing every public channel
3.1.202026-04-2176760Update dependencies
3.1.192026-04-2076297Rename “API Token” to “Bot Token” in connector spec and docs
3.1.182026-04-1576324Skip non-member channels when auto-join is disabled to prevent cursor pollution
3.1.172026-04-1376276Rename “concurrent workers” to “concurrent threads” in connector spec
3.1.162026-04-0276052Skip joining archived channels that are rejected by the Slack API
3.1.152026-04-0275905Add configurable option to skip conversations.replies API calls for messages with no replies, reducing unnecessary API usage
3.1.142026-03-2775197Add declarative OAuth with oauth_connector_input_specification and granular scopes
3.1.132026-03-2475329Update dependencies
3.1.122026-03-1074598Update dependencies
3.1.112026-02-2473948Update dependencies
3.1.102026-02-1773564Update dependencies
3.1.92026-02-1073208Update dependencies
3.1.82026-02-0369495Update dependencies
3.1.72025-10-2968772Update dependencies
3.1.62025-10-2168282Update dependencies
3.1.52025-10-1467767Update dependencies
3.1.42025-10-0767449Update dependencies
3.1.32025-10-0667084Update dependencies
3.1.22025-09-3066566Update to CDK v7
3.1.12025-09-2466640Update dependencies
3.1.02025-09-1866501Promoting release candidate 3.1.0-rc.1 to a main version.
3.1.0-rc.12025-09-1064160Migrate to manifest-only.
3.0.02025-09-1065937Add migration guide for missing state issue
2.2.02025-09-1066155Promoting release candidate 2.2.0-rc.7 to a main version.
2.2.0-rc.72025-08-2165132Update API budget to depend on auth method (rate limits apply only with OAuth).
2.2.0-rc.62025-08-1464553Add API budget for Threads and Channel Messages streams.
2.2.0-rc.52025-08-0664530Set use_cache = true for Channels and Channel Messages streams.
2.2.0-rc.42025-08-0464486Add backoff strategy for Channels stream.
2.2.0-rc.32025-07-2964107Add custom partition router.
2.2.0-rc.22025-07-2363732Enable progressive rollout.
2.2.0-rc.12025-07-2363278Migrate Threads stream to manifest.
2.1.02025-07-1162930Promoting release candidate 2.1.0-rc.1 to a main version.
2.1.0-rc.12025-07-0762110Bump cdk v6
2.0.22025-07-0562709Update dependencies
2.0.12025-06-2851965Update dependencies
2.0.02025-06-2562055Add breaking change notification for migrating to the new Slack Marketplace application to retain higher rate limits.
1.3.22025-01-1143812Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
1.3.12024-07-2442485Fix MRO error for IncrementalMessageStream
1.3.02024-07-1741994Migrate to CDK v3.5.1
1.2.02024-07-1641970Migrate to CDK v2.4.0
1.1.132024-07-1341863Update dependencies
1.1.122024-07-1041485Update dependencies
1.1.112024-07-0941231Update dependencies
1.1.102024-07-0640839Update dependencies
1.1.92024-06-2540347Update dependencies
1.1.82024-06-2240166Update dependencies
1.1.72025-06-1439343Update state handling for threads Python stream
1.1.62024-06-1239416Respect include_private_channels option in threads stream
1.1.52024-06-1039132Convert string state to float for threads stream
1.1.42024-06-0639271[autopull] Upgrade base image to v1.2.2
1.1.32024-06-0539121Change cursor format for channel_messages stream to %s_as_float
1.1.22024-05-2338619Fix cursor granularity for the channel_messages stream
1.1.12024-05-0236661Schema descriptions
1.1.02024-04-1837332Add the capability to sync from private channels
1.0.02024-04-0235477Migration to low-code CDK
0.4.12024-03-2736579Upgrade airbyte-cdk version to emit record counts as floats
0.4.02024-03-1936267Pin airbyte-cdk version to ^0
0.3.92024-02-1235157Manage dependencies with Poetry
0.3.82024-02-0935131Fixed the issue when schema discovery fails with 502 due to the platform timeout
0.3.72024-01-101234Prepare for airbyte-lib
0.3.62023-11-2132707Threads: do not use client-side record filtering
0.3.52023-10-1931599Base image migration: remove Dockerfile and use the python-connector-base image
0.3.42023-10-0631134Update CDK and remove non iterable return from records
0.3.32023-09-2830580Add bot_id field to threads schema
0.3.22023-09-2030613Set default value for channel_filters during discover
0.3.12023-09-1930570Use default availability strategy
0.3.02023-09-1830521Add unexpected fields to streams channel_messages, channels, threads, users
0.2.02023-05-2426497Fixed lookback window value limitations
0.1.262023-05-1726186Limited the lookback window range for input configuration
0.1.252023-03-2022889Specified date formatting in specification
0.1.242023-03-2024126Increase page size to 1000
0.1.232023-02-2121907Do not join channels that not gonna be synced
0.1.222023-01-2722022Set AvailabilityStrategy for streams explicitly to None
0.1.212023-01-1221321Retry Timeout error
0.1.202022-12-2120767Update schema
0.1.192022-12-0119970Remove OAuth2.0 broken refresh_token support
0.1.182022-09-2817315Always install latest version of Airbyte CDK
0.1.172022-08-2816085Increase unit test coverage
0.1.162022-08-2816050Fix SATs
0.1.152022-03-3111613Add ‘channel_filter’ config and improve performance
0.1.142022-01-269575Correct schema
0.1.132021-11-087499Remove base-python dependencies
0.1.122021-10-076570Implement OAuth support with OAuth authenticator
0.1.112021-08-275830Fix sync operations hang forever issue
0.1.102021-08-275697Fix max retries issue
0.1.92021-07-204860Fix reading threads issue
0.1.82021-07-144683Add float_ts primary key
0.1.72021-06-253978Release Slack CDK Connector
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.