Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Slack — connector

Reads a channel's messages (including threads and reactions), the list of channels, and workspace users via the Slack Web API and loads them into the Bronze layer.

On this page (15)

Read before: ../conectores.md (state map) and fichas.md (index of fichas).


What it is#

Reads a channel's messages (including threads and reactions), the list of channels, and the workspace users via the Slack Web API and loads them into the Bronze layer.

Supported ingestion modes:

  • Nós buscamos — Nós buscamos os dados na sua fonte.

What it's for#

Bring Slack data into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language question wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation by workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources in the plan).
  • Access: requires an active workspace — with billing overdue, suspended or cancelled, the run is blocked.
  • Shutdown: ingestion runs can be temporarily turned off (maintenance or incident). When this happens, the screen indicates the feature is unavailable at the moment.

Prerequisites#

  • A Slack account with access to the data you want to ingest.
  • In Slack, create an app at api.slack.com/apps, give it the bot scopes channels:history, channels:read, users:read and users:read.email, install it in the workspace and copy the Bot User OAuth Token (xoxb-…). Add the app to the channel (/invite @app). Get the channel ID (Channel Details → ID) and paste the token — it is encrypted and never shown again.

Credentials#

Authentication method: Access token pasted by you. It is encrypted (AES-256-GCM) and never shown again, nor appears in logs or error messages.

Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the config of the connection, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving this connection's credential to the external credentials vault is an explicit choice, done per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Bot User OAuth Token (tokenBot) — In the app's OAuth & Permissions, after installing in the workspace.

Secrets are never re-displayed and are redacted in all errors/logs (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
channelIdID do canaltextosimEm Detalhes do canal, no rodapé (começa com C ou G). O app precisa estar no canal.
tokenBot 🔒Bot User OAuth Tokensenha/segredosimsegredo (cifrado; cofre externo opcional); Em OAuth & Permissions do app, após instalar no workspace.

Step by step#

  1. In the Dados → Conexões menu, use Nova conexão.
  2. Choose Slack in the catalog.
  3. Fill the form fields (see the table above).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In the review, Publicar (agenda desligada) creates version 1 without running anything. After that, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values are fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
channelId = <channelId>
tokenBot = •••••• (cifrado — nunca exibido)

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, rows appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~0.3 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Scope per workspace: each customer reads and writes only to their own datalake (<prefix>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being written. The external credentials vault is optional and enabled per connection; without it, the encrypted value is stored in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: all errors/logs go through secret redaction (raw, URL-encoded and in JSON).
  • Production does not mock: a path that would fall into a mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or missing necessary permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If this happens in consecutive runs, open a support ticket with the connector and resource information.
  • Empty record path — the response arrived without records where expected. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor runs in the observability por conector (error rate, p50/p95, freshness).
  • A schema change at the source is flagged by schema drift (new column = info; removed column/type changed = attention).

Related#


Last review: 2026-10-04. Ficha generated automatically from the product's connector catalog.

Related links