Miro Stale Board Cleanup with Kestra

id: miro-stale-board-cleanup
namespace: company.team
description: |
  Sweep a Miro team for boards that have not been modified in a configurable
  number of days and delete them, but only when an explicit confirmation
  input is set to true. Deletion in Miro is permanent, so the flow fails
  fast without confirmation and posts an audit summary to Discord.

inputs:
  - id: team_id
    type: STRING
    description: Miro team ID to sweep for stale boards.
  - id: stale_days
    type: INT
    defaults: 90
    description: A board whose last modification is older than this many days is
      considered stale and will be deleted.
  - id: confirm_delete
    type: BOOL
    defaults: false
    description: Miro board deletion is permanent and cannot be undone. The flow
      fails immediately unless this is explicitly set to true.

tasks:
  - id: confirm_gate
    type: io.kestra.plugin.core.flow.If
    description: Refuse to run the sweep unless the operator explicitly confirmed
      deletion, so a casual execution can never destroy boards.
    condition: "{{ inputs.confirm_delete == false }}"
    then:
      - id: abort_unconfirmed
        type: io.kestra.plugin.core.execution.Fail
        description: Fail the execution before any board is listed or deleted; deletion
          is irreversible and requires confirm_delete set to true.
        errorMessage: "Stale board cleanup aborted: confirm_delete is false. Re-run with
          confirm_delete set to true to permanently delete stale boards."

  - id: list_boards
    type: io.kestra.plugin.miro.boards.List
    description: List the first page of boards in the target team; each returned
      board object carries its last-modified timestamp for the staleness check.
    token: "{{ secret('MIRO_ACCESS_TOKEN') }}"
    teamId: "{{ inputs.team_id }}"
    limit: 50

  - id: sweep_stale
    type: io.kestra.plugin.core.flow.ForEach
    description: Iterate over the listed boards; each iteration receives one board
      object as a JSON string in taskrun.value.
    values: "{{ outputs.list_boards.boards }}"
    tasks:
      - id: check_stale
        type: io.kestra.plugin.core.flow.If
        description: Compare the board's modifiedAt date against the cutoff. Both sides
          are formatted as yyyy-MM-dd strings, which order correctly under
          string comparison, keeping the date logic simple and visible.
        condition: "{{ (fromJson(taskrun.value).modifiedAt | date('yyyy-MM-dd')) <
          (now() | dateAdd(0 - inputs.stale_days, 'DAYS') | date('yyyy-MM-dd'))
          }}"
        then:
          - id: delete_board
            type: io.kestra.plugin.miro.boards.Delete
            description: Permanently delete the stale board. This cannot be undone; the
              confirm_gate task guarantees the operator opted in.
            token: "{{ secret('MIRO_ACCESS_TOKEN') }}"
            boardId: "{{ fromJson(parent.taskrun.value).id }}"

  - id: notify
    type: io.kestra.plugin.discord.DiscordIncomingWebhook
    description: Post an audit summary naming the team, the scanned board count, and
      the staleness threshold, so every sweep leaves a visible record.
    url: "{{ secret('DISCORD_WEBHOOK_URL') }}"
    payload: |
      {
        "content": "Miro stale board sweep finished for team {{ inputs.team_id }}: scanned {{ outputs.list_boards.size }} of {{ outputs.list_boards.total }} boards, deleting those untouched for more than {{ inputs.stale_days }} days. Per-board results are on execution {{ execution.id }}."
      }

errors:
  - id: alert_failure
    type: io.kestra.plugin.discord.DiscordIncomingWebhook
    description: Alert Discord when the sweep fails or is aborted, including the
      unconfirmed-run guard, so every stopped sweep is visible.
    url: "{{ secret('DISCORD_WEBHOOK_URL') }}"
    payload: |
      {
        "content": "Miro stale board cleanup stopped in flow {{ flow.id }} (execution {{ execution.id }}). Either confirm_delete was false or a task failed; check the execution logs before re-running."
      }

triggers:
  - id: quarterly
    type: io.kestra.plugin.core.trigger.Schedule
    description: Run the sweep on the first morning of each quarter. Leave disabled
      unless the confirm_delete default has been deliberately reviewed, since
      scheduled runs use input defaults.
    cron: "0 6 1 */3 *"
    disabled: true

Old boards pile up until finding the current one means scrolling past two years of abandoned brainstorms, and every abandoned board is also an unwatched surface still sharing whatever was pasted onto it. This blueprint automates the cleanup with the caution deletion deserves. The flow lists a team's boards with io.kestra.plugin.miro.boards.List, compares each board's modifiedAt timestamp against a configurable staleness cutoff, and deletes the stale ones with io.kestra.plugin.miro.boards.Delete. Because Miro deletion is permanent and cannot be undone, an If guard fails the execution before anything is listed unless the confirm_delete input is explicitly true, and a Discord summary records every sweep.

How it works

confirm_gate (io.kestra.plugin.core.flow.If) checks the confirm_delete boolean first. When false, the nested io.kestra.plugin.core.execution.Fail task stops the execution with a clear message before any Miro call is made.
list_boards (io.kestra.plugin.miro.boards.List) fetches up to 50 boards for the team, exposing the page as {{ outputs.list_boards.boards }} plus total and size scalars.
sweep_stale (io.kestra.plugin.core.flow.ForEach) iterates the board objects; inside the loop each board arrives as a JSON string, decoded with fromJson(taskrun.value).
check_stale compares modifiedAt against now() minus stale_days. Both sides are rendered as yyyy-MM-dd strings, which sort correctly under plain string comparison, so the date logic stays one readable line.
delete_board runs only inside the If branch and reads the board ID with fromJson(parent.taskrun.value).id, since tasks nested under an If inside a ForEach reach the loop value through parent.
notify posts a Discord audit summary with the scanned counts and threshold; the errors block reports stopped or failed sweeps, including unconfirmed runs.
A disabled-by-default quarterly Schedule trigger is included; scheduled runs use input defaults, so confirm_delete defaulting to false keeps even an accidentally enabled schedule harmless.

What you get

A workspace where the board list reflects current work, swept on your threshold, not by hand.
A hard confirmation gate, so the destructive path requires a deliberate true and fails safe otherwise.
Per-board delete results in the execution tree, an audit trail of exactly what was removed and when.
A Discord record of every sweep for whoever asks where a board went.

Who it's for

Workspace admins whose Miro team has accumulated years of one-off boards.
IT teams reducing the number of forgotten surfaces that still share company content.
Ops engineers who want lifecycle policies for collaboration tools, not just for infrastructure.

Why orchestrate this with Kestra

A cleanup script with a delete call in a loop is exactly the kind of automation that needs guardrails: typed inputs with safe defaults, a fail-fast confirmation gate, per-iteration visibility into what was deleted, and a permanent execution history. Kestra provides all of that declaratively, and the same flow serves as both the quarterly job and the documented, repeatable manual procedure.

Prerequisites

A Miro OAuth access token with boards:read and boards:write scopes.
The Miro team ID to sweep.
A Discord incoming webhook for audit summaries.

Secrets

MIRO_ACCESS_TOKEN: Miro OAuth 2.0 access token.
DISCORD_WEBHOOK_URL: Discord incoming webhook URL.

Quick start

Add the two secrets to your Kestra namespace.
Execute the flow with confirm_delete left false and confirm it fails fast with the guard message.
Create a throwaway team or use a test token scope, run with confirm_delete true and a high stale_days, and verify the Discord summary and per-board results.
Only then consider enabling the quarterly trigger.

How to extend

Sweep more than 50 boards by paging with the task's offset property across repeated runs.
Replace deletion with a softer action, a boards.Update renaming stale boards with an ARCHIVE prefix, keeping the same loop and gate.
Post the would-be deletions to Discord first and require a second execution to delete, a two-phase dry run.
Exclude protected boards by filtering on a name convention with the List task's query property.

Stale Miro Board Cleanup with a Confirmation Gate

How it works

What you get

Who it's for

Why orchestrate this with Kestra

Prerequisites

Secrets

Quick start

How to extend

Links

Tasks

Share this Blueprint

Create a Blueprint

New to Kestra?

Stale Miro Board Cleanup with a Confirmation Gate

How it works

What you get

Who it's for

Why orchestrate this with Kestra

Prerequisites

Secrets

Quick start

How to extend

Links

Tasks

Share this Blueprint

Create a Blueprint

More Business Blueprints

Klaviyo Pre-Send Recipient Estimation Alert

LinkedIn Analytics to Warehouse-Ready JSONL

Alert LINE when a flow breaches its duration SLA

Watch one critical flow and report its result to LINE

React to New LinkedIn Comments with Discord Alerts

Weekly Klaviyo Campaign Performance Report to Slack

New to Kestra?