Skip to content

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

Updated on 2026-10-04

Trello — connector

Reads cards, lists, members and a board's action history via Trello's REST API and loads into the Bronze layer.

On this page (15)

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


What it is#

Reads cards, lists, members and a board's action history via Trello's REST API and loads into the Bronze layer.

Supported ingestion modes:

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

What it's for#

Bring Trello 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 of the plan).
  • Access: requires an active workspace — with a past-due, suspended or canceled subscription, the run is blocked.
  • Shutdown: ingestion runs can be temporarily disabled (maintenance or incident). When that happens, the UI indicates the feature is unavailable at the moment.

Prerequisites#

  • A Trello account with access to the data you want to ingest.
  • In Trello, create a Power-Up at trello.com/power-ups/admin to obtain the API key and, on the same screen, generate a token for your user (link 'Token'). Provide the board ID (in the URL: trello.com/b/<ID>/…), the key and the token — the token is encrypted and never shown again.

Credentials#

Authentication method: API key generated in the provider's panel, sent in header/parameter.

Sensitive fields. They are encrypted (AES-256-GCM) and never appear in the connection config, pipeline definition, export or 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, made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Token (tokenApi) — User token generated from the API key.

Secrets are never re-displayed and go through redaction on any error/log (raw token, URL-encoded and in JSON).

Form fields#

CampoRótuloTipoObrigatórioObservação
boardIdID do quadrotextosimO trecho da URL do quadro depois de trello.com/b/ (o ID curto também funciona).
chaveApiChave de API (key)textosimChave do Power-Up (Trello a chama de 'key'). Não é secreta sozinha — só vale junto com o token.
tokenApi 🔒Tokensenha/segredosimsegredo (cifrado; cofre externo opcional); Token do usuário gerado a partir da chave de API.

Step-by-step#

  1. In the Dados → Conexões menu, use Nova conexão.
  2. Choose Trello 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. Then, 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)
boardId = <boardId>
chaveApi = <chaveApi>
tokenApi = •••••• (cifrado — nunca exibido)

Expected result#

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

Limits and costs#

  • Pagination: hard ceiling 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.1 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 by 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 stored. The external credentials vault is optional and enabled per connection; without it, the encrypted value remains 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 hit 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 lacking 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 it happens on consecutive runs, open a support ticket indicating the connector and the resource.
  • Empty record path — the response arrived without records in the expected location. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

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

Related#


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

Related links