Overview
Trello is a visual project management and collaboration platform that enables teams to organize work using boards, lists, and cards. It is commonly used by operations, product, marketing, and project teams to track tasks, workflows, and progress.
The Trello integration within the Wrk platform allows you to automate task and workflow management by interacting with Trello boards, cards, lists, and members through the Trello REST API using prebuilt Wrk Actions.
This document provides an overview of how Trello integrates into Wrk, how authentication works, general API behaviour, and a full list of available Wrk Actions.
Authentication
Trello uses API key and token-based authentication for all API requests.
When connecting Trello in Wrk, users must provide:
Input | Description |
API Key | Your Trello developer API key |
API Token | Your Trello user access token |
How to Obtain API Credentials
Generate an API Key:
Visit: https://trello.com/app-key
Copy your API key
Generate an API Token:
From the same page, click “Generate a Token”
Authorize access to your Trello account
Copy the generated token
Important Notes
API tokens do not expire by default but can be revoked manually.
Permissions are tied to the user who generated the token.
If access is revoked or permissions change, the connection must be reconfigured in Wrk.
General API Behaviour
Entity Structure
Trello is built around a hierarchical structure:
Boards — Top-level containers for workflows
Lists — Columns within boards (e.g., To Do, In Progress)
Cards — Individual tasks within lists
Each entity includes:
id— Unique identifier (string)name— Display namedesc— Description (cards only)idBoard,idList— Relationship references
These IDs must be used exactly as returned when calling Wrk Actions.
Pagination
Trello uses limit-based pagination for list endpoints.
Common parameters include:
limit— Number of results to return (default varies by endpoint)before/since— Used for cursor-based navigation
Example:
limit=50— returns up to 50 itemsbefore=<card_id>— returns items before a specific card
Unlike offset-based pagination, Trello relies on object IDs or timestamps for navigating large datasets.
Filtering and Querying
Many Trello endpoints support filtering via query parameters.
Examples:
cards=openorcards=all— filter card statesmembers=true— include member datafields=name,desc— limit returned fields
Filtering helps reduce payload size and improves performance in automated workflows.
Field Selection
Trello allows selective field retrieval using the fields parameter.
Example:
fields=name,desc,idList
This ensures:
Smaller response sizes
Faster API calls
Predictable output structure for downstream steps
Rate Limiting
Trello enforces API rate limits per API key and token.
Limits are applied per user and per application
Excessive requests may result in HTTP 429 Too Many Requests
To avoid throttling:
Use filtered requests instead of full dataset retrieval
Avoid unnecessary polling
Batch operations where possible
Available Wrk Actions
Add a label to a card in Trello
Add a member to a card in Trello
Add a new comment to a card in Trello
Create a new card in Trello
Create a reaction for an action in Trello
Delete a card in Trello
Delete an action’s reaction in Trello
Delete an action in Trello
Retrieve a board from Trello
Retrieve a card from Trello
Retrieve a list from Trello
Retrieve a member from Trello
Retrieve actions for a list from Trello
Retrieve actions of a board from Trello
Retrieve an action’s reaction from Trello
Retrieve an action’s reactions from Trello
Retrieve an action from Trello
Retrieve cards in a list from Trello
Retrieve memberships of a board from Trello
Retrieve the board a list is on from Trello
Search for members in Trello
Search Trello
Update a card in Trello
Update a comment action in Trello
Update a list in Trello
Additional Resources
Trello REST API Reference:
https://developer.atlassian.com/cloud/trello/rest/Authentication Guide:
https://developer.atlassian.com/cloud/trello/guides/rest-api/authorization/