Reset a Recurring Trello Ops Checklist with Weekly Nudges and Fresh Due Dates

Standing checklist cards are the cheapest ops process there is, and the easiest to let rot. This blueprint keeps one alive on a schedule: every Monday it posts a dated nudge comment through io.kestra.plugin.trello.cards.Comment, pushes the card's due date one week out with io.kestra.plugin.trello.cards.Update, and pins the card to the top of its list. The comment history becomes a log of every cycle that ran, and the due date never silently expires.

How it works

1. A disabled-by-default Schedule trigger fires every Monday at 08:00.
2. nudge_comment (io.kestra.plugin.trello.cards.Comment) posts a reset message stamped with {{ now() | date('yyyy-MM-dd') }}, so the card's comment thread doubles as an audit trail of completed cycles.
3. push_due_date (io.kestra.plugin.trello.cards.Update) sets due to {{ now() | dateAdd(7, 'DAYS') }} and pos: top, restarting the clock and surfacing the card.
4. notify confirms the reset in Discord, and the errors block raises a distinct alert when the reset fails, because a checklist that stops nagging looks exactly like a checklist that is done.

One honest limitation: the Trello plugin exposes card creation, update, move, and comment tasks, but no task that lists or searches cards. The flow therefore works on card ids you provide as inputs rather than discovering overdue cards itself. For a small set of standing cards that is exactly enough; duplicate the two Trello tasks or loop over an array input to cover more cards.

What you get

• A recurring checklist that re-arms itself with a fresh due date every cycle.
• A dated comment per cycle, turning the card history into a record of when resets ran.
• A Discord confirmation and a distinct failure alert, so both outcomes are visible.
• A pattern that extends from one standing card to a handful with one loop.

Who it's for

• Ops teams running weekly hygiene checklists, backups, access reviews, or on-call handovers from a board.
• Team leads who want recurring process without a dedicated task manager.
• Anyone whose standing card currently depends on someone remembering to bump it.

Why orchestrate this with Kestra

Trello can hold a checklist but cannot re-date it on a schedule. Kestra brings the cron trigger, the date arithmetic for the comment stamp and the new due date, secret management for the API credentials, and an execution history proving every cycle ran, or alerting when one did not.

Prerequisites

• A standing checklist card on a Trello board, and its card id for the checklist_card_id input.
• A Trello API key and token from https://trello.com/power-ups/admin.
• A Discord incoming webhook for cycle confirmations 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 checklist_card_id to your standing card.
2. Execute the flow once manually and check the comment, the new due date, and the Discord note.
3. Set disabled: false on the weekly trigger and adjust the cron to your cycle.

How to extend

• Cover several standing cards by switching the input to an array and looping with io.kestra.plugin.core.flow.Loop.
• Change the cadence to daily or monthly by editing the cron and the dateAdd amount together.
• Reopen an archived checklist card at the start of each cycle by adding closed: false to the update task.
• Move the card back to a "This week" list each cycle with io.kestra.plugin.trello.cards.Move.

Links

• Trello plugin documentation
• Trello REST API documentation