Source connector

Slack connector

Slack integration for databases, warehouses and BI tools

Team messaging across channels and workspaces. Datrise captures Slack entities such as channels, messages, users, threads, reactions and channel memberships, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Slack Web API authenticates with OAuth 2.0, incremental runs key on oldest / latest timestamp parameters on conversations.history, and Slack caps calls at Four tiers per method per workspace/app: Tier 1 ~1+/min, Tier 2 20+/min, Tier 3 50+/min, Tier 4 100+/min; as of 2025-05-29, non-Marketplace-approved apps are limited to 1 request/minute on conversations.history and conversations.replies.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `slack_channels`) with a schema derived from the Slack API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Slack pipeline page, and join the waitlist to get the Slack connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Slack data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
channels	slack_channels	Upsert by primary key, incremental on updated-at
messages	slack_messages	Append-only, incremental by timestamp
users	slack_users	Upsert by primary key, incremental on updated-at
threads	slack_threads	Upsert by primary key, incremental on updated-at
reactions	slack_reactions	Upsert by primary key, incremental on updated-at
channel memberships	slack_channel_memberships	Upsert by primary key, incremental on updated-at

Slack API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Slack Web API
Authentication	OAuth 2.0 — Apps install via OAuth2 to obtain bot (xoxb-) or user (xoxp-) tokens; legacy workspace tokens were fully deprecated in August 2021.
Pagination	cursor — cursor / next_cursor in response_metadata for most list methods; conversations.history additionally supports oldest/latest Unix-timestamp windows.
Rate limit	Four tiers per method per workspace/app: Tier 1 ~1+/min, Tier 2 20+/min, Tier 3 50+/min, Tier 4 100+/min; as of 2025-05-29, non-Marketplace-approved apps are limited to 1 request/minute on conversations.history and conversations.replies.
Incremental cursor	oldest / latest timestamp parameters on conversations.history — Most Slack resources (users, channels) have no modified-since filter; only conversation message history supports time-bounded incremental pulls.
Webhooks	Yes — Events API
Bulk export	No
Deletes detectable	Yes — message_deleted / channel-related events via the Events API; there is no REST endpoint that lists deleted messages after the fact.

Official API reference

What bites when replicating Slack

conversations.history defaults to a `limit` of 100 messages per page (max 999), but for apps created after 2025-05-29 without Marketplace approval the max/default `limit` drops to 15 and the method throttles to 1 request per minute.
Events API deliveries are capped at 30,000 per workspace per app per 60 minutes; exceeding this triggers an `app_rate_limited` notification.
Legacy workspace tokens were fully deprecated in August 2021, so integrations must use OAuth2-issued `xoxb-`/`xoxp-` tokens instead.
Rate limits are enforced per method per workspace/team per app across four tiers (Tier 1 ~1/min up to Tier 4 100+/min), so throttling on a Tier 2 method like conversations.list does not affect calls to a Tier 3 method.

Compare this against every other documented API

Popular destinations for Slack

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Slack connector FAQ

What Slack data does the connector extract?: 6 objects: channels, messages, users, threads, reactions and channel memberships. Each lands in its own table with types preserved; history-style objects (1: messages) load as append-only streams.
Is the Slack integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Slack data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Slack → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Slack pipeline with guided onboarding

Join the waitlist to get priority access for Slack integrations with guided setup, schema-aware mapping, and production-grade incremental sync.