> ## Documentation Index
> Fetch the complete documentation index at: https://usepike.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Trello

> Two-way sync between Trello and Pike: boards, lists, cards and labels become projects, phases, tasks and categories, and Pike hours show on cards.

The Trello integration connects the boards you choose to Pike [projects](https://usepike.com/docs/project/overview.md) and syncs their cards both ways as Pike [tasks](https://usepike.com/docs/tasks/overview.md). Your team keeps planning on Trello boards, and edits made to a task in Pike show on the card. Pike adds what Trello does not track (time, allocations, cost and margin per board) and shows logged and planned hours on each card.

## At a glance

| | |
| - | - |
| **Direction** | Two-way for cards, lists, labels and checklists. Trello to Pike for boards. Pike to Trello for hours logged and planned, as Custom Fields on each card |
| **Who sets it up** | Workspace admins connect. Admins and finance users change sync settings |
| **Plan** | All plans |
| **Sync** | Every 3 hours. On the Enterprise plan, changes sync in real time. |
| **Source of truth** | Trello for card content (name, description, list, members, dates, labels, checklists), edited in either system. Pike for time, allocations, rates and cost |

## Before you start

You need:

* The workspace admin role in Pike.
* A Trello account that is a normal member of every board you want in Pike. Pike reads and writes with that account's access: boards the account cannot open do not appear in the board picker, and changes from Pike cannot reach a board where the account is only an observer. Use a shared account or a Trello Workspace admin, so the connection does not depend on one person's job.
* Custom Fields on the boards where you want Pike hours on cards. Custom Fields depend on your Trello plan. Without them, everything else syncs.
* Pike members for the people who work on your cards. You match Trello members to Pike members during setup. See [Members](https://usepike.com/docs/members/overview.md).

## Connect Trello

**1. Open the integration**

Go to **Workspace settings → Integrations → Trello** and click **Add
integration**.

**2. Authorize Pike in Trello**

A Trello window opens. Sign in with the account from **Before you start**
and click **Allow**. Pike asks for **read** and **write** access to your
boards, and **account** access to the connecting member's own name and
email. The authorization does not expire. You can revoke it any time in
Trello under **Settings → Applications**.

**3. Select boards**

Under **Boards**, pick the Trello boards to connect. For each board, choose
**Create new project** or link it to an existing Pike project. Set the Pike
team and, if you want, the customer for each new project.

**4. Choose the mapping**

Under **Mapping**, choose whether Trello lists become **Phases** (the
default) or **Statuses**, and whether labels become categories by **Label
name** (the default), by **Label color**, or not at all. See
[Mapping](#mapping).

**5. Match members**

Under **Members**, check the suggested Pike member for each Trello member on
the selected boards. Pike suggests a match by full name. Trello shares email
addresses only for the connecting account, so confirm each match.

**6. Choose what Pike sends**

In the **What syncs with Trello** card, leave **Send** on for lists, cards
and labels to write Pike edits back to Trello, and turn on **Send** for
hours to show Pike hours on each card.

**7. Import**

Click **Import data**. Projects import first, then tasks. When the import
finishes, two-way sync starts.

The integration page shows **Connected**, the Trello account name, **Last synced** and **Next sync**.

## What syncs

| Trello | Pike | Direction |
| - | - | - |
| Boards | Projects | Trello to Pike |
| Lists | Phases, or statuses | Both ways |
| Cards | Tasks | Both ways |
| Labels | Categories | Both ways |
| Checklists | Checklist | Both ways |
| Custom Fields **Pike logged** and **Pike planned** | Hours logged and allocated on the task | Pike to Trello |

### Boards

| Trello field | Pike field | Notes |
| - | - | - |
| Board name | Project title | Only for projects Pike creates. A linked project's title does not change |
| Board ID | Trello board ID | Shown on the project as the Trello marker |
| Closed board | Project marker | The project is marked **Removed in Trello** and stops syncing |

Pike sets customer, team, billing type, budget and rates on the project. Trello has no fields for them, and Pike does not create or rename boards.

### Lists

| Trello field | Pike field | Notes |
| - | - | - |
| List name | Phase name, or status | Follows the **Lists become** setting |
| List order | Phase order | When lists become phases |
| List | Status, through the mapping | When lists become statuses. Each list maps to a Pike project status |
| New list | New phase | A phase added in Pike on a connected project creates a list at the right of the board |

### Cards

| Trello field | Pike field | Notes |
| - | - | - |
| Card ID | Trello card ID | Stored on the task. Every sync matches on it |
| Card name | Task title | Both ways |
| Description | Description | Both ways. Trello Markdown carries over as rich text |
| List | Phase, or status | Both ways. Moving a task to another phase or status in Pike moves the card |
| Members | Assignees | Both ways, through the member match |
| Start date | Start date | Both ways |
| Due date | Due date | Both ways |
| Due date complete | Status **Done** | Both ways, when lists become phases. An open card has the status **To Do** |
| Checklists | Checklist | Both ways. Items and their done state. See [Checklist](https://usepike.com/docs/tasks/checklist.md) |
| Labels | Categories | Both ways. Follows the **Labels become** setting |
| Archived or deleted | Task marker | The task is marked **Removed in Trello** and stops syncing |

A task created in Pike on a connected project creates a card on the board, in the list that matches its phase or status, and stores the new card ID. To create the card straight away, click **Create in Trello** on the task.

### Labels

| Trello field | Pike field | Notes |
| - | - | - |
| Label name | Category | The default. Labels with the same name on different boards share a category |
| Label color | Category | When **Labels become** is set to **Label color**. Useful for unnamed labels |

A category is a task label that time reports group by. Time logged on a card with the label **Design** rolls up under the **Design** category in [time reports](https://usepike.com/docs/time/admin.md), across every connected board. A category added to a task in Pike adds the label on the card, and creates the label on the board when it does not exist.

### Hours on cards

With **Send** on for hours, Pike adds two number Custom Fields to each connected board and updates them on every card:

| Custom Field | Value |
| - | - |
| **Pike logged** | Hours logged on the task in Pike, approved and unapproved |
| **Pike planned** | Hours allocated on the task across its assignees |

Your team sees burn on the card without opening Pike. Pike sends hours only. Rates, cost, billable status and margin never go to Trello.

## Mapping

The **Mapping** card on the integration page sets how Trello structure becomes Pike structure. The settings apply to the whole workspace, and every connected board uses them.

| Setting | Options | Default |
| - | - | - |
| **Lists become** | **Phases** or **Statuses** | **Phases** |
| **Labels become** | **Label name**, **Label color** or **Off** | **Label name** |

**Phases** suits boards where lists are stages of a client project, such as Discovery, Design and Build. Each list becomes a [phase](https://usepike.com/docs/project/creating.md#phases), and phase completion follows the cards in it.

**Statuses** suits boards where lists are a workflow, such as To do, Doing and Done. Under **Status mapping**, pick a Pike project status for each Trello list. Pike suggests a status from the list name. When two lists map to the same status, a task moved to that status in Pike goes to the leftmost of them. See [Manage statuses](https://usepike.com/docs/project/overview.md).

A change to the mapping applies to every synced card on the next sync.

## Matching and duplicates

Pike stores the Trello card ID on every task it imports or creates in Trello, and matches on that ID on every sync. A re-sync, **Sync now** or a second **Import data** never creates a duplicate task or card.

* A board matches the Pike project you linked it to in setup. A board set to **Create new project** creates one project and links it.
* A card matches the task with the same Trello card ID. A card with no linked task creates a new task in the board's project.
* A task created in Pike on a connected project creates one card and stores its ID. Pike does not create a second card for the same task.
* A list matches a phase in the project with the same name before Pike creates a new phase.
* A label matches a category with the same name, or the same color when **Labels become** is **Label color**, before Pike creates a new category.
* A Trello member matches the Pike member you confirmed under **Members**. A new Trello member on a card appears under **Members** as unmatched until someone picks a Pike member.

## Which system wins

| Entity | Synced both ways | Pike owns, never sent to Trello |
| - | - | - |
| Projects | Nothing. Trello owns the board and its name | Customer, team, billing type, budget, rates and project members |
| Tasks | Title, description, list, members, dates, checklist and labels | Time entries, allocations, hourly rates, billable status, cost |
| Phases | Phase name and order, when lists become phases | Phase dates and colors |
| Categories | Which categories a card has | How categories group time in reports |

When the same field changes in both systems between two syncs, the most recent change wins, and the other value appears in the task's history. On the Enterprise plan, changes sync in real time, so conflicts are rare.

## Sync schedule

Pike syncs Trello every 3 hours. On the Enterprise plan, changes sync in real time. **Import data**, **Sync now**, **Refresh** and **Create in Trello** run straight away on every plan. See [How sync works](https://usepike.com/docs/integrations/how-sync-works.md).

| Action | Where | What it does |
| - | - | - |
| **Import data** | The integration page | The first full import: projects, then tasks |
| **Sync now** | The integration page | A full two-way sync of every connected board |
| **Refresh** | A task with the Trello marker | Fetches that card from Trello now |
| **Create in Trello** | A task on a connected project | Creates the card now instead of on the next sync |

The top of the integration page shows **Last synced** and **Next sync** with their times, or **Real-time** in place of **Next sync** on Enterprise. On Enterprise, Pike registers a Trello webhook on each connected board, and Trello notifies Pike of a card change within seconds.

## Sync settings

While Trello is connected, the **What syncs with Trello** card is below the top button row on the integration page. Toggles save immediately. Only admins and finance users can change sync settings and the mapping.

| Entity | Read | Send |
| - | - | - |
| Boards | Yes | Not available |
| Lists | Yes | Yes |
| Cards | Yes | Yes |
| Labels | Yes | Yes |
| Hours | Not available | Yes, as **Pike logged** and **Pike planned** |

New connections start with **Read** on for boards, lists, cards and labels, **Send** on for lists, cards and labels, and **Send** off for hours. Turning **Read** off stops updates from Trello for that entity, and the records already imported stay in Pike. Turning **Send** off stops Pike edits from reaching Trello, and the Trello-owned fields for that entity show as read-only in Pike with the Trello marker.

## Sync issues

A card that fails to sync in either direction appears in **Sync issues** on the integration page with the card, the direction, the reason and **Retry**. Pike also retries every failed card on the next scheduled sync. Workspace admins receive an email when a sync has new issues.

## How it works

```mermaid theme={"system"}
sequenceDiagram
  participant Team as Team in Trello
  participant Trello
  participant Pike
  participant Lead as Project lead in Pike
  Team->>Trello: Move the card Homepage copy to the Design list
  Trello->>Pike: Card change, on the next sync or in real time
  Pike->>Pike: Match on the Trello card ID, move the task to the Design phase
  Lead->>Pike: Log 3 hours and set the due date to Friday
  Pike->>Trello: Due date Friday, Pike logged 3
  Trello-->>Team: Card shows the new due date and 3 hours logged
```

## Use it in Pike

### Log time against Trello cards

Every synced card is a Pike task, so members pick it in the [timer or timesheet](https://usepike.com/docs/time/entry.md) like any other task. Hours logged on the card count toward the project budget, the phase and the card's categories, and show on the card as **Pike logged**.

### See margin per board

Each connected board is a Pike project with its own customer, rates and budget. Open the project's **Finance** tab to see budget burn and margin from the time logged on its cards. See [Project finance](https://usepike.com/docs/project/project-finance.md).

### Plan in Pike, work in Trello

Resource managers add tasks, set dates and assign people in Pike. The cards appear on the board with the same members and due dates, and the team keeps working from Trello while capacity is planned in Pike. See [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md).

### Report time by label

Labels become categories across every board. A time report grouped by category shows how many hours went into **Design**, **Copy** or **Revisions** for the month, on every client board at once.

### Copy a closed board once

For a one-off copy of a board you do not want to keep in sync, such as a closed client board, use the [Trello column mapping](https://usepike.com/docs/integrations/csv.md#trello) on the CSV page. A CSV import does not store Trello card IDs, so connect the board later only if you are ready to link the existing tasks by hand.

## Deletes and removed records

An integration never deletes Pike data. A card archived or deleted in Trello is marked **Removed in Trello** on the task. The task stays in Pike with its time entries, allocations and history, and stops syncing. A closed or deleted board marks its project **Removed in Trello** the same way. An archived list's phase stays in Pike and stops updating.

Pike never deletes Trello cards. Deleting or archiving a synced task in Pike archives its card in Trello, where a board member can restore it.

## Troubleshooting

| Symptom | Fix |
| - | - |
| A board is missing from the board picker | The connected Trello account is not a member of the board. Add the account to the board in Trello, then reopen **Boards**. |
| A card did not update | Check that **Read** is on for cards, then click **Refresh** on the task. |
| A Pike edit did not reach Trello | Check that **Send** is on for that entity and that the connected account is a normal member of the board, not an observer. Then click **Retry** in **Sync issues**. |
| A task has no assignee | The Trello member has no Pike match. Match them under **Members**, then click **Retry** in **Sync issues**. |
| **Pike logged** is missing on cards | **Send** is off for hours, or Custom Fields are not available on the board. Turn on Custom Fields in Trello, then click **Sync now**. |
| Cards show the wrong phase or status | Check **Lists become** and the **Status mapping** under **Mapping**. Changes apply on the next sync, or click **Sync now**. |
| Two categories for one label | The label has a different name on two boards. Rename one label so both match, then click **Sync now**. |
| **Sync issues** lists an access error | The authorization was revoked under **Settings → Applications** in Trello, or the account left the board. Click **Reconnect** and authorize again. |
| **Sync issues** lists a rate limit | Trello limits how many requests one connection makes in a short window. Pike waits and retries on its own, and large first imports take longer for this reason. |

## Limits

* Pike does not create, rename or close Trello boards. Create each board in Trello first.
* One Trello board connects to one Pike project, and one project connects to one board.
* Time entries, rates, cost, billable status and margin stay in Pike. Only hour totals go to Trello, and only when **Send** is on for hours.
* Card comments, attachments, other Custom Fields and Power-Up data do not sync.
* Pike reads and writes only the boards the connected Trello account is a member of.
* The mapping is set per workspace. Every connected board uses the same **Lists become** and **Labels become** settings.
* A card marked **Removed in Trello** stops syncing, even if someone restores it in Trello.
* Pike stays within Trello's API rate limits for each connection, so a first import of very large boards runs over several minutes.

## Disconnect

Go to **Workspace settings → Integrations → Trello** and click **Disconnect**. Syncing stops in both directions, and every project, phase, task, category and time entry stays in Pike with its history. Cards stay in Trello as they are, with their last **Pike logged** and **Pike planned** values. Reconnecting the same Trello account relinks boards and cards by their Trello IDs.

## Related

* [How sync works](https://usepike.com/docs/integrations/how-sync-works.md): The schedule, real-time sync, **Refresh** and sync issues.
* [Permissions and access](https://usepike.com/docs/integrations/permissions-and-access.md): Who connects, who changes sync settings and who sees synced data.
* [Migration](https://usepike.com/docs/integrations/migration.md): Every source tool and its route into Pike.
* [Task properties](https://usepike.com/docs/tasks/properties.md): The fields a task has, including phase, status and label.
* [Project finance](https://usepike.com/docs/project/project-finance.md): Budget burn and margin from logged time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.