Skip to main content

Trello — Application Overview

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:

InputDescription
API KeyYour Trello developer API key
API TokenYour Trello user access token

How to Obtain API Credentials​

  1. Generate an API Key: - Visit: https://trello.com/app-key - Copy your API key
  2. 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 name
  • desc — 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 items
  • before= — 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=open or cards=all — filter card states
  • members=true — include member data
  • fields=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
  • Add a member to a card
  • Add a new comment to a card
  • Create a new card
  • Create a reaction for an action
  • Delete a card
  • Delete an action
  • Retrieve a board
  • Retrieve a card
  • Retrieve a list
  • Retrieve a member
  • Retrieve actions for a list
  • Retrieve actions of a board
  • Retrieve an action
  • Retrieve cards in a list
  • Retrieve memberships of a board
  • Retrieve the board a list is on
  • Search for members
  • Update a card
  • Update a comment action
  • Update a list

Additional Resources​