Automatically Move Trello Cards to a Target List When a Due Date Is Set

Desired Outcome

When any card on a Trello board receives a due date, it should automatically be moved from its current list into a pre‑defined list—e.g., Due Soon. This keeps the board focused on imminent tasks and reduces manual re‑organization.

Prerequisites

• Board administrator or owner permissions.
• Butler Power‑Up enabled for the board. If it’s not active, add it via the board’s Power‑Ups menu.
• A target list already created on the board (named or otherwise). The rule will reference this list by its name or ID.
• Understanding of Trello’s rule syntax: trigger → action.

Focused Procedure

1. Open Butler. On the board, click the Butler button in the top bar and choose Rules.
2. Create a new rule. Click + New rule and give it a descriptive name, e.g., Move card to Due Soon on due date set.
3. Set the trigger. In the trigger section, choose When a due date is set on a card. This will fire immediately after the due date field is populated.
4. Define the action. In the action section, select Move the card to list and pick the target list from the dropdown (e.g., Due Soon). If the list name is ambiguous, use the list’s ID by clicking Show more options and entering the ID.
5. Save the rule. Click Save. The rule is now active for the board.
6. Test the rule. Create a test card in any list, set a due date, and observe the movement. The card should appear in the target list within a few seconds.

Expected Checks

• Card movement. After setting the due date, the card must reappear in the target list. If it doesn’t, double‑check the rule’s target list name.
• Butler activity log. Open Butler → Activity and look for an entry that reads: "Moved card 'Card Name' to list 'Due Soon' because a due date was set." This confirms the rule fired.
• Due date retention. Verify that the card’s due date remains unchanged after the move.
• No error messages. The rule editor should not display any syntax errors or warnings.

Recovery Options

If the rule fails to fire:

• Check Butler quota. Each board has a monthly automation quota. Exceeding it delays or blocks new rule executions. View the quota at Butler → Settings → Quota.
• Rule conflict. Ensure no other rule is moving the same card to a different list at the same time. Disable or adjust conflicting rules.
• Permission issue. Verify that you are still an admin and that the board’s Power‑Up hasn’t been disabled.
• Test with a new card. Sometimes existing cards have hidden metadata that interferes. Create a brand‑new card to confirm the rule works.

Limitations & Practical Checks

• Butler rules run per board; if you have multiple boards, repeat the setup on each.
• Moving cards via Butler does not trigger card‑based webhooks automatically. If you rely on external integrations that watch for card movements, add a separate rule to send a webhook or adjust your integration to listen for the card’s due‑date change.
• Test in a non‑production board first. A misconfigured rule could clutter your main board with unintended moves.
• To confirm the rule is effective, after a few days of operation, review the Butler activity log for consistent entries. If none appear, revisit the trigger.

Conclusion

By following this guide, you’ll automate the relocation of due‑date cards to a dedicated list, keeping your Trello board tidy and ensuring that upcoming tasks are always front‑and‑center. The rule is simple, requires no code, and can be adapted to any board with minimal effort.