Skip to main content
Technical Preview

Overview

A client-mode connector for the Trello REST API that turns plant events into visible work. A typical flow opens a card on the maintenance board when an alarm fires, moves it from To do to In progress to Done as the work order progresses, adds comments with live readings, labels it by line, assigns a technician, attaches a dashboard link, ticks lockout checklist items and records asset or downtime values in custom fields. The same connector reads boards, lists and cards back into the broker for andon screens and shift reports, and registers Trello webhooks that post board changes to a Coreflux server connector. One connector carries 38 events (21 GET, 11 POST, 6 PUT; 17 writes, no DELETE). Topics use devops/trello/<object>/<verb>; each response is published on <source topic>/response.
The template was checked against Trello’s OpenAPI definition and a local mock. Thirteen read events were called live, without credentials, against Trello’s public roadmap board, and every event was probed on api.trello.com with a dummy key (each answers invalid key, while unknown paths answer 404). Writes have not run with a real key and token yet, so status stays blocked until an authenticated smoke passes.

Setup

  1. Create a Power-Up in the Trello Power-Up admin portal and generate its API key.
  2. Generate a user token for that key (the Token link next to the key, or https://trello.com/1/authorize?expiration=never&scope=read,write&response_type=token&key=<key>). The token acts as the user who approved it, so use a service account that is a member of the boards you automate.
  3. Keep both in broker secrets (for example TRELLO_API_KEY and TRELLO_TOKEN) and build the header value in a LoT action with GET SECRET. Never retain topics that carry it.

Authentication

Trello takes the key and token either as key and token query parameters or in an Authorization header. This connector uses the header so credentials never appear in URLs or logs. Pass the whole header value in authorization:
Public boards can be read with an empty authorization.

Query parameters and bodies

Trello reads create and update fields from query parameters, so writes pass them URL-encoded in query (for example idList=<listId>&name=Press%207%20overtemperature&pos=top). Reads use query for fields, filter and limits; leave it empty for defaults. Only CardCustomFieldSet takes a JSON body. Values are sent as given, so URL-encode them yourself.

Examples

Open a maintenance card when a press overheats (devops/trello/cards/create):
Trello answers with the new card, including id and shortUrl. Move it to In progress when a technician accepts the work order (devops/trello/cards/update):
Record downtime minutes in a number custom field (devops/trello/cards/custom-fields/set):
Read the open maintenance queue for an andon screen (devops/trello/lists/cards/list):
Send board changes to a Coreflux server connector (devops/trello/webhooks/create):
Trello sends a HEAD request to callbackURL when you create a webhook and only creates it if that answers 200. Each delivery carries an X-Trello-Webhook signature (HMAC-SHA1 of the body plus the callback URL, keyed with your Power-Up secret); check it in the receiving server connector.

Events

Limits

Trello allows 300 requests per 10 seconds per API key and 100 requests per 10 seconds per token, and answers 429 above that. Batch folds up to 10 GET calls into one request. Custom fields need the Custom Fields Power-Up on the board.

Not packaged

  • All DELETE endpoints (boards, lists, cards, labels, checklists, attachments, webhooks) on purpose; archive with closed=true instead.
  • File uploads to cards (multipart); CardAttachmentAddUrl attaches links only.
  • Board membership and Workspace administration, enterprise endpoints, Power-Up plugin data, stickers, emoji, notifications and saved searches.
  • The incoming webhook direction: Trello posts change events to a separate ENABLE_SERVER REST_API connector, which must answer the creation HEAD request and verify X-Trello-Webhook.

Suggested branches

feat/rest-api-route-trello for the broker template and feat/docs-rest-api-trello for this page.
Last modified on October 21, 2026