Build Repeatable Trello Release Checklists with One Card per Item

The most dangerous release checklist is the one rebuilt from memory. This blueprint makes the checklist a versioned artifact: an array input holds the item names, io.kestra.plugin.core.flow.Loop loops over them, and io.kestra.plugin.trello.cards.Create produces one card per item at the bottom of the release list, preserving order. Discord reports the created count, so the release owner can confirm the board is complete before the first step starts.

How it works

1. The checklist_items array input defines the checklist. The defaults cover a typical software release; edit them once and every future run uses the same list.
2. build_checklist (io.kestra.plugin.core.flow.Loop) iterates over the items in order.
3. create_item (io.kestra.plugin.trello.cards.Create) creates each card with {{ item.value }} as the name and pos: bottom, so the column reads top to bottom in checklist order. The description stamps the creating flow and execution for traceability.
4. notify posts the count, computed with {{ inputs.checklist_items | length }}, to Discord.
5. The errors block posts a distinct Discord alert on failure, because a partially built checklist is worse than none, it looks complete.

What you get

• An identical, ordered checklist on the board for every release, built in seconds.
• The checklist definition living in flow inputs, reviewable and versionable like code.
• A created-card count in Discord as a completeness check.
• Cards stamped with the execution that created them, for auditability.

Who it's for

• Release managers who rebuild the same column of cards before every ship.
• Small teams that run releases from a Trello board instead of a release tool.
• Anyone standardizing a repeatable process, releases, onboarding, or event prep, as board cards.

Why orchestrate this with Kestra

Trello stores the cards, but recreating a checklist by hand invites drift, skipped items, and reordered steps. Kestra turns the checklist into data: a loop, an input array, secret management for the API credentials, and an execution history showing exactly which cards each release run created.

Prerequisites

• A Trello board with a release list, and that list's id for the release_list_id input.
• A Trello API key and token from https://trello.com/power-ups/admin.
• A Discord incoming webhook for the summary and failure alerts.

Secrets

• TRELLO_API_KEY: Trello API key.
• TRELLO_API_TOKEN: Trello API token.
• DISCORD_WEBHOOK_URL: Discord incoming webhook URL.

Quick start

1. Add the three secrets to your Kestra namespace and set release_list_id to your release column.
2. Adjust the checklist_items defaults to your release process.
3. Execute the flow and confirm the cards appear in order, then check the count in Discord.

How to extend

• Add per-item due dates by switching the input to structured entries and passing due on the create task.
• Kick the flow off from CI by adding a Webhook trigger, so cutting a release branch builds the board.
• Name the checklist per release by adding a version input and prefixing name with it.
• Pair with the deploy pipeline mover blueprint so the same board also tracks the deploy stages.

Links

• Trello plugin documentation
• Trello REST API documentation