Trello

Trello is a visual project management tool that organizes work into boards, lists, and cards. Teams use it to track tasks, assign responsibilities, and manage workflows across projects. Connecting Trello to Coupler.io lets you pull your board data into spreadsheets, dashboards, or AI tools — automatically and on a schedule.

Why connect Trello to Coupler.io?

• Export board cards, card activity, and checklist items into Google Sheets, Excel, BigQuery, or Looker Studio

• Send Trello data to AI tools like ChatGPT, Claude, or Gemini to summarize progress, flag blockers, or generate reports

• Combine data from multiple Trello boards using the Append transformation

• Keep your destination always up to date with scheduled refreshes

Prerequisites

• A Trello account with access to the board(s) you want to export

• The URL of the Trello board you want to connect (you'll need this during setup)

• Coupler.io account (free plan works)

Quick start

If you want a ready-made report, check if a Trello template is available in the Coupler.io template gallery — it can save you setup time.

How to connect

1

Create a new data flow. In Coupler.io, click Add data flow, then search for and select Trello as your source.

2

Authorize your Trello account. Click Connect and sign in to Trello via OAuth. Coupler.io will ask for permission to read your boards — approve it.

3

Select an entity and enter your board URL. Choose what you want to import — Board cards, Cards updates, or Checklist items. Then paste the URL of the Trello board you want to pull data from. You can find the board URL in your browser's address bar when viewing the board in Trello.

4

Choose a destination. Select where you want your data to go — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini. Follow the prompts to connect your destination account.

5

Run your data flow. Click Run to do a manual run. Once it completes successfully, your Trello data will appear in your destination.

Trello data overview

Coupler.io can pull three types of data from Trello. Each maps to a different part of your Trello workflow — the cards themselves, the history of changes to those cards, and the detailed checklist tasks inside them.

Available entities

Entity	Best for
Board cards	Snapshot of current board state — task tracking, reporting, status overviews
Cards updates	Audit trail and timeline analysis — who moved what, and when
Checklist items	Granular task tracking — subtask completion rates, team workload

Board cards

Card details

Field	Description
id	Unique card identifier
name	Card title
desc	Card description
idList	ID of the list the card belongs to
idBoard	ID of the board
due	Due date
dueComplete	Whether the due date is marked complete
dateLastActivity	Timestamp of the most recent activity on the card
closed	Whether the card is archived
url	Direct link to the card

Card metadata

Field	Description
labels	Labels assigned to the card (name and color)
idMembers	Member IDs assigned to the card
idChecklists	IDs of checklists attached to the card
shortLink	Short URL identifier for the card
pos	Card's position within its list

Custom fields created with the Trello Custom Fields Power-Up are not always exported automatically. If you don't see your custom field columns, run a full export first to see all available column names, then use the Columns filter to select the ones you need.

Cards updates

Activity fields

Field	Description
id	Unique action ID
type	Type of action (e.g., updateCard, commentCard, addMemberToCard)
date	Timestamp of the action
idMemberCreator	ID of the member who performed the action
data.card.name	Name of the card the action was performed on
data.listBefore	List the card was moved from
data.listAfter	List the card was moved to

Checklist items

Checklist fields

Field	Description
id	Unique checklist item ID
name	Checklist item text
state	Completion state (complete / incomplete)
idChecklist	ID of the parent checklist
idCard	ID of the card the checklist belongs to
pos	Position of the item within the checklist

Common metric combinations

• Board cards + Checklist items — Join on idCard to see cards alongside their subtask completion rates

• Board cards + Cards updates — Join on card ID to build a full card history report, including current state and all changes

• Board cards from multiple boards — Use the Append transformation to combine cards from several boards into one unified dataset

Use cases by role

Project managers

• Export Board cards to Google Sheets or Looker Studio to build sprint dashboards showing card status, assignees, and due dates

• Use Cards updates to see how long cards spent in each list, helping you identify bottlenecks in the workflow

• Send board data to ChatGPT or Claude to generate automated project status summaries

Team leads

• Export Checklist items to track individual task completion across team members

• Append cards from multiple boards to get a consolidated view of work across all your teams' projects

• Use the Start date filter to pull only recently created cards for weekly reporting

Operations

• Schedule regular exports of Board cards to BigQuery for long-term project analytics

• Use Cards updates to build an audit log of who changed what and when — useful for compliance or retrospectives

• Aggregate checklist completion rates by list or label to report on delivery health

Platform-specific notes

• Trello's API returns data for one board at a time — use the Append transformation to combine multiple boards in a single data flow

• The Start date parameter filters cards by creation date, not last activity date

• Power-Up fields (including Custom Fields) may appear as nested JSON or may require the Columns filter to isolate specific fields

• Archived cards are included in exports by default (closed: true) — filter them out in your destination if you only want active cards

• Labels are returned as an array — in spreadsheet destinations, they may appear as comma-separated values or in a structured format depending on your destination

Trello common issues

Connection issues

"Invalid credential" error when connecting Trello

This usually means the OAuth token has expired or was revoked. Disconnect your Trello account from Coupler.io and reconnect it by going through the OAuth flow again. Make sure you're logged in to the correct Trello account in your browser before reconnecting.

Connected to the wrong Trello account

Coupler.io connects to whichever Trello account is currently active in your browser. If you have multiple Trello accounts, log out of Trello first, then sign in to the correct account before authorizing Coupler.io.

Missing data

Custom fields are missing from the export

Trello Custom Fields (from the Custom Fields Power-Up) aren't always included in the default export. First, run an export without any column filters to get all available fields. Then identify the exact column names for your custom fields and enter them in the Columns parameter to include them going forward.

Custom Fields from third-party Power-Ups (other than Trello's own Custom Fields Power-Up) may not be accessible via the Trello API at all.

Some columns aren't appearing in the output

If you've specified column names in the Columns field, double-check the spelling — column names are case-sensitive. The safest approach is to run a full export first (leave Columns empty), copy the exact column names from the output, and paste them back into the Columns field.

Cards from a specific list are missing

Coupler.io exports all cards from the entire board, not individual lists. If certain cards are missing, check whether they've been archived in Trello — archived cards have closed: true and may need to be filtered in your destination. Also confirm you've entered the correct board URL.

Checklist items aren't showing up

Checklist items are a separate entity from Board cards. Make sure you've selected Checklist items as the entity in your data flow — they won't appear in a Board cards export.

Permission errors

"Board id was not found" error

This error means the board URL you entered is incorrect, the board has been deleted, or the connected Trello account doesn't have access to that board. Verify the board URL by opening the board in Trello and copying the URL directly from the browser. Also confirm the authorized account is a member of that board.

Can't access a private board

Private Trello boards require the connected account to be a member. Ask the board owner to add your Trello account, then retry the data flow.

Data discrepancies

Card count in Coupler.io doesn't match what I see in Trello

Trello's board view hides archived cards by default, but the API includes them. This is the most common reason for a higher card count in your export. Filter rows where closed = true in your destination to match what you see in Trello.

Labels appear as a long string instead of separate values

Trello returns labels as an array object. In spreadsheet destinations, this may render as a JSON-formatted string. You can parse this in Google Sheets using a formula, or use Coupler.io's column selection to pull specific label subfields if available.

Rate limits

Exports are slow or timing out for very large boards

Trello's API applies rate limits that can slow down exports from boards with thousands of cards or a long activity history. If you're hitting this, try using the Start date parameter to limit the data range, or split large boards into separate data flows by entity type.

Trello FAQ

Can I export data from multiple Trello boards at once?

Yes — add each board as a separate source within the same data flow, then use the Append transformation to combine them into a single output. Each source needs its own board URL.

How do I export Trello custom fields?

Custom fields from Trello's Custom Fields Power-Up are included in the API response, but they may not appear unless you run a full export first (with no Columns filter). Once you've identified the exact column names in your output, add them to the Columns field in your data flow settings. Note that custom fields from third-party Power-Ups are generally not accessible via the Trello API.

Can I get the creation date of a Trello card?

Trello doesn't return a dedicated createdAt field, but the creation date is encoded in the card's id (Trello uses timestamp-based IDs). Some users decode this from the ID. Alternatively, the Cards updates entity includes action timestamps — the first createCard action for a card represents its creation date.

Can I export a specific Trello list rather than the whole board?

No — the Trello API returns data at the board level, not the list level. Coupler.io exports all cards from the board. You can filter by the idList column in your destination to isolate cards from a specific list. To find the list ID, check the exported data or use the Trello API directly.

Why do I see more cards in my export than on my Trello board?

The export includes archived cards by default (closed: true). Your Trello board view hides these. Add a filter in your destination to exclude rows where closed equals true to match the board view.

What's the difference between Board cards and Cards updates?

Board cards gives you a current snapshot of every card on the board — its title, list, labels, members, due date, and so on. Cards updates gives you a history of actions taken on cards — who moved a card, added a comment, changed a due date, etc. Use Board cards for status reporting and Cards updates for activity tracking or audit logs.

Can I use the Start date filter with all three entities?

The Start date parameter filters data by the entity's creation date. It works most predictably with Cards updates, where each action has a clear timestamp. For Board cards, it filters by the card creation date. For Checklist items, behavior may vary — test with a sample run to confirm results for your board.

Can I send Trello data to an AI tool for analysis?

Yes — Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send your Board cards or Cards updates data directly to these tools to generate project summaries, identify blockers, or answer questions about your board data.

For details on what fields are available in each entity, see the Data Overview article. For help with missing fields or connection errors, check Common Issues. For tips on setting up your data flow effectively, see Best Practices.