> 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/common-issues.md).
# 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.
{% hint style="warning" %}
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.
{% endhint %}
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.
---
# 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/common-issues.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.