> 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/faq.md).

# FAQ

<details>

<summary>Can I export data from multiple Trello boards at once?</summary>

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.

</details>

<details>

<summary>How do I export Trello custom fields?</summary>

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.

</details>

<details>

<summary>Can I get the creation date of a Trello card?</summary>

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.

</details>

<details>

<summary>Can I export a specific Trello list rather than the whole board?</summary>

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.

</details>

<details>

<summary>Why do I see more cards in my export than on my Trello board?</summary>

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.

</details>

<details>

<summary>What's the difference between Board cards and Cards updates?</summary>

**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.

</details>

<details>

<summary>Can I use the Start date filter with all three entities?</summary>

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.

</details>

<details>

<summary>Can I send Trello data to an AI tool for analysis?</summary>

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.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](/sources/category/project-management/trello/data-overview.md) article. For help with missing fields or connection errors, check [Common Issues](/sources/category/project-management/trello/common-issues.md). For tips on setting up your data flow effectively, see [Best Practices](/sources/category/project-management/trello/best-practices.md).
{% endhint %}


---

# 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/faq.md?ask=<question>&goal=<endgoal>
```

`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.