> 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/data-overview.md). # 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 | {% hint style="info" %} 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. {% endhint %} ## 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 {% tabs %} {% tab title="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 {% endtab %} {% tab title="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 {% endtab %} {% tab title="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 {% endtab %} {% endtabs %} ## 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 --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.coupler.io/sources/category/project-management/trello/data-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.