Appearance
Trello
Manage boards, lists, and cards with the Trello API.
| Detail | Value |
|---|---|
| Category | Project Management |
| Base URL | https://trello.com/1 |
| Authentication | API Key (Query) |
| Endpoints | 6 |
| Connector key | trello |
Using Trello in a workflow
- Go to Connections and click New Connection.
- Pick Trello from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /members/me/boards | List boards for the authenticated user |
GET /boards/{id}/lists | Get lists on a board |
GET /boards/{id}/cards | Get cards on a board |
POST /cards | Create a new card |
PUT /cards/{id} | Update a card |
POST /cards/{id}/actions/comments | Add a comment to a card |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /members/me/boards
List boards for the authenticated user
| Detail | Value |
|---|---|
| Operation ID | pm.listBoards |
| Method | GET |
| Path | /members/me/boards |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trello connection from the Connection dropdown.
- In the Operation dropdown, select
pm.listBoards. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Trello API reference.
GET /boards/{id}/lists
Get lists on a board
| Detail | Value |
|---|---|
| Operation ID | pm.getBoardLists |
| Method | GET |
| Path | /boards/{id}/lists |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trello connection from the Connection dropdown.
- In the Operation dropdown, select
pm.getBoardLists. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Trello API reference.
GET /boards/{id}/cards
Get cards on a board
| Detail | Value |
|---|---|
| Operation ID | pm.getBoardCards |
| Method | GET |
| Path | /boards/{id}/cards |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trello connection from the Connection dropdown.
- In the Operation dropdown, select
pm.getBoardCards. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Trello API reference.
POST /cards
Create a new card
| Detail | Value |
|---|---|
| Operation ID | pm.createCard |
| Method | POST |
| Path | /cards |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
name | string |
idList | string |
desc | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trello connection from the Connection dropdown.
- In the Operation dropdown, select
pm.createCard. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Trello API reference.
PUT /cards/{id}
Update a card
| Detail | Value |
|---|---|
| Operation ID | pm.updateCard |
| Method | PUT |
| Path | /cards/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Request Body
| Field | Type |
|---|---|
name | string |
desc | string |
idList | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trello connection from the Connection dropdown.
- In the Operation dropdown, select
pm.updateCard. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Trello API reference.
POST /cards/{id}/actions/comments
Add a comment to a card
| Detail | Value |
|---|---|
| Operation ID | pm.addComment |
| Method | POST |
| Path | /cards/{id}/actions/comments |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | string | Yes |
Request Body
| Field | Type |
|---|---|
text | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Trello connection from the Connection dropdown.
- In the Operation dropdown, select
pm.addComment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Trello API reference.