Source connector

Trello connector

Trello integration for databases, warehouses and BI tools

Kanban boards for tasks and lightweight project tracking. Datrise captures Trello entities such as boards, lists, cards, members, and activity logs, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Trello REST API v1 authenticates with API key, OAuth 2.0, incremental runs key on since (board actions), and Trello caps calls at 300 requests per 10 seconds per API key, 100 requests per 10 seconds per token, plus a separate 100 requests per 900 seconds cap on `/1/members/*` calls.

Of the 5 objects, 4 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 `trello_boards`) with a schema derived from the Trello 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 Trello pipeline page, and join the waitlist to get the Trello connector (Work management) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Trello 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
boards	trello_boards	Upsert by primary key, incremental on updated-at
lists	trello_lists	Upsert by primary key, incremental on updated-at
cards	trello_cards	Upsert by primary key, incremental on updated-at
members	trello_members	Upsert by primary key, incremental on updated-at
activity logs	trello_activity_logs	Append-only, incremental by timestamp

Trello API: setup facts for the connector

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

API	Trello REST API v1
Authentication	API key, OAuth 2.0 — Most integrations pair an application API key with a user token issued through Trello's authorize flow; Trello also still supports signing requests via OAuth 1.0 for legacy Power-Ups.
Pagination	keyset — `GET /boards/{id}/actions` pages the activity log with `since`/`before` action-ID or date cursors and `limit` (default 50, max 1,000 per call).
Rate limit	300 requests per 10 seconds per API key, 100 requests per 10 seconds per token, plus a separate 100 requests per 900 seconds cap on `/1/members/*` calls
Incremental cursor	since (board actions) — There is no `modified_since` filter on cards themselves; incremental sync means walking `GET /boards/{id}/actions?since=...` (the activity log) and replaying `createCard`/`updateCard`/`deleteCard` events to reconstruct state.
Webhooks	Yes — Webhooks
Bulk export	No
Deletes detectable	Yes — A `deleteCard` action appears in the board's action log (and in webhook deliveries), but archiving is a separate `updateCard` action with `closed: true` in its `data`, so the two must be distinguished explicitly.

Official API reference

What bites when replicating Trello

Card state changes surface only as entries in the board-level action log (`GET /boards/{id}/actions`), capped at `limit=1000` per call, not as a per-card `modified_since` filter, so full incremental sync means replaying `createCard`/`updateCard`/`deleteCard` events rather than querying cards directly.
`deleteCard` is a distinct action type from archiving (`updateCard` with `closed: true` in its `data`), and a `deleteCard` payload carries only the card ID, not its prior field values, so a connector must have captured the card before deletion to know what was lost.
Rate limits are enforced separately per API key (300 req/10s) and per token (100 req/10s), so a multi-tenant connector sharing one API key across many user tokens can exhaust the key-level budget even when no single token is over its own limit.
Webhook callback URLs are validated with a synchronous HTTP HEAD request at creation time and must return 200 immediately, and a webhook auto-disables after 30 consecutive days of failed deliveries (with over 1,000 failed attempts), silently going quiet unless the connector polls webhook health.

Compare this against every other documented API

Popular destinations for Trello

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

Trello connector FAQ

What Trello data does the connector extract?: 5 objects: boards, lists, cards, members and activity logs. Each lands in its own table with types preserved; history-style objects (1: activity logs) load as append-only streams.
Is the Trello 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 Trello data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Trello → destination pair has its own page with the object-to-table mapping.

Related Work management sources

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

Early access

Launch your Trello pipeline with guided onboarding

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