Automate Basics
Operations

Archive Trello Cards After They Have Been Done for 30 Days

By

· Updated · 5 min read

To automatically archive completed Trello cards after 30 days, start the clock when a card enters Done, not when it was created. Use Trello’s Butler automation, then test that moving a card back into active work cancels or resets the archive.

Hand moving a card between groups on a sunlit worktable
Image: AI-generated illustration.

To automatically archive completed Trello cards after 30 days, start the clock when a card enters Done, not when it was created. Use Trello’s Butler automation, then test that moving a card back into active work cancels or resets the archive.

Completion starts the archive clock

A Trello card should become eligible for archiving 30 days after it enters Done, not 30 days after someone created it. A card can sit in active work for weeks before completion. Using its creation date could archive it almost as soon as the work is finished.

Decide what Done means on your board before building the automation. If your team has several finished lists, choose whether each one counts as completion. Also decide whether moving a card back to active work cancels its completed status. Those choices determine which card movement should start, stop and restart the clock.

Trello’s built-in automation, often called Butler, is enough for a straightforward board with one Done list. You do not need an outside automation service just to clean up old completed Trello cards. If your workflow starts in another tool, such as a message captured through a Slack-to-Trello card workflow, keep that card’s creation event separate from its eventual move to Done. The archive clock should follow the work’s completion, regardless of where the card came from.

A dedicated archive date makes the rule testable

The clearest Butler rule sets an archive date when a card moves into Done. In Trello’s Automation area, create a rule triggered by moving a card into your Done list. Have the rule set the card’s due date to 30 days from that move. Then create a due-date automation that archives the card when that date arrives, but only if the card is still in Done. Check the available trigger and condition choices in your board’s editor before enabling it.

In this setup, the due date means “archive after this date,” not “finish the work by this date.” Make that meaning clear to anyone who uses the board. A due-date trigger without a Done-list restriction is unsafe: it could archive active cards that happen to have ordinary deadlines.

Do not use this approach if your team already relies on Trello due dates for work deadlines. Replacing a real deadline with an archive date would make the board less useful. Instead, check whether your board’s scheduled automation offers a way to archive cards by how long they have been in Done. That measures time in the completed list without changing card deadlines. If the editor cannot express that condition, do not substitute card age for completion age.

Reopening a card must cancel its pending archive

A reopened card should not be archived on the date set during its earlier visit to Done. Add another Butler rule for a card moved out of Done into active work. For the dedicated archive-date setup, that rule clears the due date. When the card later moves back into Done, the entry rule gives it a fresh date 30 days away.

The move out of Done is the important event. Changing a label, adding a comment or unchecking an item may signal reopening to a person, but those actions will not reset this clock unless you explicitly build automation for them. Ask the team to move reopened work out of Done, or revise the rules to match the action people actually take.

If you chose a scheduled command based on time in the Done list instead, check how that command treats a card that leaves and re-enters the list. The intended result is that the card gets a new full waiting period. Do not assume that a command based on card creation or an old date will do that. The same reopening test applies whichever automation method you choose.

A sample card reveals mistakes before live cards move

Test the archive workflow with a disposable card before turning it loose on finished work. Move the card into Done and check that the entry rule sets the expected future date. Move it back to active work and confirm that the pending archive date disappears. Then return it to Done and confirm that the date is set again from the new completion event.

To test the archive action without waiting 30 days, use a separate sample card with a due date shortly in the future and watch what the due-date automation does. Keep that card in Done for one run. For another run, move it out of Done before the trigger fires. The active card should remain unarchived. A date set in the past may not behave like a newly reached date, so a near-future test is clearer.

If you use a scheduled time-in-list command, test with a temporary schedule and a short eligibility period if the editor permits it, then restore the intended settings. Confirm what happened in Trello’s automation activity or run history. Check for a skipped command, an unmet condition or an automation limit rather than assuming the rule ran because the card did not move.

Archive only when the board still needs the record

Automatic archiving is a cleanup step, not a substitute for deciding which records to keep. Trello archives remove cards from the board view without treating them as newly created work. Before enabling the rule across a busy board, decide whether completed cards contain approvals, handover details or attachments that colleagues still need to see.

If important files need their own home, put that process in place before the card disappears from everyday view. For example, saving email attachments to a folder automatically addresses file storage, while the Trello rule addresses board clutter. Neither process should quietly stand in for your workplace’s retention requirements.

Review the first cards the automation archives and ask teammates whether Done now means what the rule assumes. Look for cards moved into Done temporarily, cards reopened without being moved out, and cards whose due dates were changed by hand. Those are reasons to adjust the workflow, not to make the archive trigger more aggressive. For a single Done list and no competing use for due dates, the built-in rule is the simple option. More complex boards need a clearer definition of completion before they need another tool.

Frequently asked questions

Can Butler archive cards 30 days after completion rather than creation?

Yes, if you define completion as a card moving into Done and build the automation around that event. One approach sets an archive date 30 days later, then archives the card when that date arrives. Restrict the archive action to cards still in Done so ordinary active cards cannot be archived by mistake.

What happens if I reopen a completed Trello card?

Reopening should cancel the pending archive. Move the card out of Done and use a rule to clear its dedicated archive date. Moving it back into Done should set a fresh date. Test those movements with a sample card, because changing only a label or comment will not affect rules based on list movement.

What if my team already uses Trello due dates for deadlines?

Do not replace work deadlines with archive dates. Check whether your board’s scheduled automation can select cards by how long they have been in Done, and test whether leaving and re-entering Done resets eligibility. If that condition is unavailable, keep archiving manual until you have a reliable way to record completion separately.

Why did my completed Trello card not archive?

Check whether the card reached the required date, remains in Done and meets every condition on the archive automation. Then inspect the automation activity for a skipped or failed run and check whether an automation limit applies. Test with a disposable card before changing rules that affect the whole board.

For you

Learn to do this with AI, free

Short courses for people who aren't engineers: ChatGPT, Claude, prompting and automation. Every lesson is free, with no card.

Start a free course

For companies

Make an AI or automation tool?

List it in the directory for $9.99, refunded in full if it isn't approved, or claim its page if it is already here.

Tools in this piece

Drafted with AI assistance and checked automatically before publishing. Tools and prices change; check the official source before you act.

Get the next one by email

One email, most weeks: what changed in AI for people who use it at work, and what to do about it.

One email, most weeks. What actually changed and what to do about it. Unsubscribe in one click.