> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/project-management/trello-community.md).

# Trello Community

Connect Trello boards, cards, checklists, and activity logs to Google Sheets or BigQuery via Coupler.io for centralized project reporting.

Trello is a visual project management tool that uses boards, lists, and cards to help teams organize tasks and workflows. Connecting Trello to Coupler.io lets you pull your project data — cards, checklists, activity logs, and more — into any destination for reporting and analysis.

## Why connect Trello to Coupler.io?

* **Centralize project data** — combine boards, cards, checklists, and user activity in one place
* **Track team productivity** — analyze card movement, action history, and workload across boards
* **Build live dashboards** — send Trello data to Google Sheets, Looker Studio, BigQuery, or AI tools like ChatGPT and Claude
* **Merge with other sources** — use Join or Append transformations to combine Trello data with time-tracking, CRM, or finance data

## Prerequisites

* A Trello account (free or paid)
* Access to the boards you want to export — you must be a member of those boards
* A Coupler.io account

## Quick start

{% hint style="success" %}
Start with the **Cards** entity for your most active board. It gives you the richest dataset and the clearest picture of task status right away.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** From your Coupler.io dashboard, click **Add data flow**. Search for **Trello Community** and select it as your source.
{% endstep %}

{% step %}
**Authorize your Trello account.** Click **Connect** and sign in to Trello via OAuth. Grant Coupler.io read access to your boards and organizations. If you manage multiple Trello accounts, make sure you sign in with the correct one.
{% endstep %}

{% step %}
**Choose an entity.** Select what you want to export — Boards, Cards, Actions, Checklists, Lists, Users, or Organizations. You can add multiple sources within the same data flow to pull several entities at once.
{% endstep %}

{% step %}
**Choose a destination.** Pick where your data should land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like Claude, ChatGPT, Gemini, Cursor, Perplexity, or OpenClaw.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync. Once it completes successfully, your Trello data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Entities overview

| Entity        | Description                                                         |
| ------------- | ------------------------------------------------------------------- |
| Boards        | Trello boards with their settings, members, and metadata            |
| Organizations | Workspaces that group multiple boards and teams                     |
| Actions       | Full activity log — card moves, edits, comments, and more           |
| Cards         | Individual tasks including status, due dates, labels, and assignees |
| Checklists    | Subtask lists attached to cards, with completion status             |
| Lists         | Columns within a board that organize cards into stages              |
| Users         | Members and collaborators with access to boards                     |

## Trello Community data overview

Trello Community gives you access to seven entities covering the full structure of your Trello workspace — from high-level organization data down to individual checklist items and user activity.

## Entities

| Entity        | What it contains                                                                  |
| ------------- | --------------------------------------------------------------------------------- |
| Boards        | Board name, ID, description, settings, member count, URL                          |
| Organizations | Workspace name, ID, display name, member list, website                            |
| Actions       | Activity type, actor, target object, timestamp, data payload                      |
| Cards         | Card name, description, list, board, due date, labels, assignees, checklist count |
| Checklists    | Checklist name, card ID, items with completion status                             |
| Lists         | List name, board ID, position, archived status                                    |
| Users         | Member ID, username, full name, email, avatar URL, membership type                |

## Available fields

#### Boards

| Field          | Description                                      |
| -------------- | ------------------------------------------------ |
| id             | Unique board identifier                          |
| name           | Board name                                       |
| desc           | Board description                                |
| closed         | Whether the board is archived                    |
| idOrganization | Parent organization ID                           |
| shortUrl       | Short URL to the board                           |
| prefs          | Board preferences (background, visibility, etc.) |

#### Organizations

| Field       | Description                    |
| ----------- | ------------------------------ |
| id          | Unique organization identifier |
| displayName | Organization display name      |
| name        | Organization slug              |
| desc        | Organization description       |
| url         | Organization URL               |
| memberships | Member list with roles         |

#### Actions

| Field           | Description                                                   |
| --------------- | ------------------------------------------------------------- |
| id              | Unique action identifier                                      |
| type            | Action type (e.g., createCard, updateCard, commentCard)       |
| date            | Timestamp of the action                                       |
| idMemberCreator | ID of the user who performed the action                       |
| data            | Nested object with context (card name, list name, board name) |

#### Cards

| Field       | Description                             |
| ----------- | --------------------------------------- |
| id          | Unique card identifier                  |
| name        | Card title                              |
| desc        | Card description                        |
| idList      | List the card belongs to                |
| idBoard     | Board the card belongs to               |
| due         | Due date                                |
| dueComplete | Whether the due date is marked complete |
| labels      | Labels attached to the card             |
| idMembers   | Assigned member IDs                     |
| pos         | Card position within the list           |
| closed      | Whether the card is archived            |

#### Checklists

| Field      | Description                                               |
| ---------- | --------------------------------------------------------- |
| id         | Unique checklist identifier                               |
| name       | Checklist name                                            |
| idCard     | Parent card ID                                            |
| checkItems | Array of checklist items with state (complete/incomplete) |
| pos        | Checklist position on the card                            |

#### Lists

| Field   | Description                  |
| ------- | ---------------------------- |
| id      | Unique list identifier       |
| name    | List name                    |
| idBoard | Board the list belongs to    |
| closed  | Whether the list is archived |
| pos     | List position on the board   |

#### Users

| Field      | Description                     |
| ---------- | ------------------------------- |
| id         | Unique member identifier        |
| username   | Trello username                 |
| fullName   | Member's full name              |
| email      | Email address (if accessible)   |
| avatarUrl  | Profile picture URL             |
| memberType | Role type (normal, admin, etc.) |

## Common field combinations

* **Cards + Lists** — join on `idList` to see each card's current stage in your workflow
* **Cards + Users** — join on `idMembers` to see workload per team member
* **Actions + Cards** — join on card ID within `data` to build a full card history log
* **Checklists + Cards** — join on `idCard` to track subtask completion rates per task

## Use cases by role

{% tabs %}
{% tab title="Project managers" %}

* Track card distribution across lists to spot bottlenecks in your workflow
* Use the Actions entity to audit who moved or modified cards and when
* Monitor overdue cards by filtering on `due` and `dueComplete` fields
* Combine Cards and Users to see individual workloads and flag team members with too many open tasks
  {% endtab %}

{% tab title="Engineering teams" %}

* Export sprint boards to Google Sheets or BigQuery for velocity tracking over time
* Use Checklists data to measure subtask completion rates per card or per assignee
* Append data from multiple boards across projects using the Append transformation
* Send board activity to an AI destination like ChatGPT to generate sprint summaries automatically
  {% endtab %}

{% tab title="Operations" %}

* Pull Organizations and Users data to audit team membership and access across workspaces
* Use Actions to track onboarding task completion across multiple team boards
* Combine Trello Cards with data from other sources (e.g., CRM or finance tools) using Coupler.io's Join transformation
* Build automated reporting dashboards in Looker Studio using refreshed Trello data
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **Actions** entity can return a large volume of records for active boards — use the **Start date** parameter to limit the export window
* **Board IDs** can be found in the board's URL: `trello.com/b/{BOARD_ID}/{board-name}`
* Fields inside the `data` object in Actions are nested — you may need to flatten them in your destination
* Archived cards (`closed: true`) and archived lists are included in exports by default — filter them out in your destination if needed
* Email addresses in the Users entity are only returned if your account has permission to view member emails within the organization

## Trello Community common issues

### Connection issues

<details>

<summary>OAuth authorization fails or redirects to an error page</summary>

Make sure you're signed in to the correct Trello account before clicking **Connect**. If you manage multiple Trello accounts, Trello may authorize the wrong one. Sign out of all Trello sessions, then reconnect using the account that has access to your target boards.

</details>

<details>

<summary>Connection succeeds but no boards appear in the entity settings</summary>

This usually means the authorized account isn't a member of any boards. Check that the Trello account you connected is added as a member to the boards you want to export. Board visibility alone doesn't grant API access — you must be a board member.

</details>

### Missing data

<details>

<summary>Cards from certain boards are missing from the export</summary>

If you've specified board IDs in the **Board IDs** parameter, only those boards will be exported. Double-check the board IDs by looking at the board URLs in Trello (`trello.com/b/{BOARD_ID}/...`). Leave the field empty to export from all accessible boards.

</details>

<details>

<summary>Actions data is incomplete or only shows recent activity</summary>

The **Actions** entity respects the **Start date** parameter. If you set a recent start date, older actions won't be included. Adjust the start date using the date picker to extend the export window back as far as you need.

</details>

<details>

<summary>Archived cards or lists are missing</summary>

Archived cards and lists are included in exports by default. If you're not seeing them, check whether filters are applied in your destination (e.g., a Google Sheets filter or a BigQuery query with a `WHERE closed = false` clause).

</details>

### Permission errors

<details>

<summary>"Unauthorized" or "403" error after a previously working data flow</summary>

Trello OAuth tokens can expire or be revoked — for example, if you changed your Trello password or revoked app access in your Trello account settings. Go to your data flow's source settings in Coupler.io and reconnect your Trello account.

</details>

<details>

<summary>User emails are not returned in the Users entity</summary>

Trello only returns email addresses for members if your account has organization-level admin permissions. If you're a regular board member, the email field will be empty. Contact your Trello workspace admin for elevated access.

</details>

### Data discrepancies

<details>

<summary>Card counts in the export don't match what I see in Trello</summary>

Trello's board view may hide archived cards by default, while Coupler.io exports them. Filter your exported data on `closed = false` to match what you see on screen. Also check that your Board IDs parameter includes all relevant boards.

</details>

<details>

<summary>Checklist item counts look wrong compared to the card view</summary>

Checklists are exported as a separate entity from Cards. The `checkItems` field in Checklists contains an array — if your destination flattens this array, you may see one row per checklist item rather than one row per checklist. This is expected behavior; aggregate by checklist ID to get totals.

</details>

### Rate limits

<details>

<summary>Data flow fails with a rate limit error</summary>

Trello's API enforces rate limits, especially for large workspaces with many boards and actions. If you hit a rate limit, reduce the scope of your export by specifying only the board IDs you need, or set a more recent start date to limit the Actions volume. Re-run the data flow once the limit resets.

</details>

## Trello Community FAQ

<details>

<summary>Can I connect multiple Trello accounts to Coupler.io?</summary>

Yes. You can authorize multiple Trello accounts and use them in separate data flows. When adding a new source, choose **Add another account** during the OAuth step to connect a different Trello account. This is useful if you manage boards across separate personal and organizational Trello accounts.

</details>

<details>

<summary>How do I find my Trello board ID?</summary>

Open the board in Trello and look at the URL: `trello.com/b/{BOARD_ID}/{board-name}`. The short alphanumeric string between `/b/` and the board name slug is your board ID. You can enter multiple board IDs in Coupler.io — one per line.

</details>

<details>

<summary>Can I export data from private boards?</summary>

Yes, as long as the Trello account you authorized in Coupler.io is a member of that private board. Board visibility (public vs. private) doesn't affect what Coupler.io can access — membership does.

</details>

<details>

<summary>What's the difference between Cards and Actions?</summary>

Cards give you the current state of each task — its title, list, due date, assignees, and labels. Actions give you the full history of changes — every move, edit, comment, and attachment across your boards. Use Cards for snapshot reporting and Actions for audit trails or trend analysis.

</details>

<details>

<summary>Can I combine Trello data with data from other tools?</summary>

Yes. Coupler.io supports Join, Append, and Aggregate transformations. You can join Trello Cards with time-tracking data (e.g., from Toggl or Harvest), append boards from multiple projects, or merge Trello user data with your CRM. Just add multiple sources to the same data flow.

</details>

<details>

<summary>Do archived cards and lists get included in the export?</summary>

Yes, they are included by default. The `closed` field is set to `true` for archived items. Filter on `closed = false` in your destination or using Coupler.io's data transformation settings if you only want active cards and lists.

</details>

<details>

<summary>Can I use Trello data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send your Cards or Actions data directly to these tools to generate sprint summaries, flag blockers, or analyze team workload — all without manual exports.

</details>

<details>

<summary>Why does my data flow run slowly when exporting Actions?</summary>

The Actions entity can contain a very large number of records on active boards. Use the **Start date** parameter to limit the export to a recent window, and specify only the board IDs you need. See the best practices guide for more tips on keeping runs fast.

{% hint style="info" %}
For more tips on optimizing your Trello data flows, see [Best Practices](https://docs.coupler.io/sources/category/project-management/trello-community/best-practices.md). For help with errors, see [Common Issues](#trello-community-common-issues).
{% endhint %}

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/project-management/trello-community.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
