Best Practices

Recommended setup

Always start with a full column export

Leave the Columns field empty on your first run to see every field Trello returns — including custom fields. Once you know the exact column names, add them to the Columns filter for cleaner, focused exports.

Use the Board URL from your browser

Copy the board URL directly from the address bar while viewing the board in Trello. Don't use a shared or shortened link — the full URL is what Coupler.io needs to identify the board correctly.

Combine entities with Join for richer reports

Board cards alone don't show checklist progress. Add Checklist items as a second source in the same data flow and use the Join transformation on card ID to see cards alongside their subtask completion status.

Data refresh and scheduling

Use Start date to keep incremental exports lean

For Cards updates on active boards, set a Start date to avoid re-pulling the entire activity history on every refresh. This is especially useful for boards with months of card history.

Append for historical tracking

If you need a running log of card changes over time, use Append mode with the Cards updates entity. Each scheduled run will add new activity rows without overwriting previous data.

Performance optimization

Split multi-board reporting into one flow with Append

Trello's API is board-scoped. To report across multiple boards, add each board as a separate source in the same data flow and use the Append transformation to combine them into one output table.

Filter archived cards in your destination

Coupler.io exports both active and archived cards. If your dashboard or report should only show active work, add a filter on the `closed` column in your destination rather than relying on the Trello board view.

Common pitfalls

Don't rely on column names from memory or documentation — Trello's API field names are case-sensitive and may differ from what you see in the Trello UI. Always verify column names from an actual export before using the Columns filter.

Do

• Copy the board URL directly from the browser address bar

• Run a full export first to discover all available column names

• Use the Checklist items entity separately when you need subtask data

• Filter closed = true rows in your destination to exclude archived cards

Don't

• Assume custom field names match what you see in the Trello card UI

• Use the same data flow for both Board cards and Cards updates — keep entities in separate sources for clarity

• Expect Power-Up data from third-party integrations to appear in exports

• Enter column names manually without verifying them from a real export first