# 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