Automate Due Dates on New Trello Cards with Butler Rules

Problem: due dates slip when cards are created manually

Teams that create cards fast often forget to set a due date. The result is invisible deadlines and manual cleanup. A Butler rule can assign a due date automatically on creation so every card starts with a consistent deadline without extra clicks.

Butler is Trello’s built-in automation. A rule is a trigger plus one or more actions. The trigger defines when it runs, the action defines what it does. Rules run on the board where they are created.

Desired outcome

Every new card added to a chosen board receives a due date calculated from its creation time, e.g., +7 days from creation. The rule is enabled, visible in the board’s Butler list, and does not interfere with existing workflows.

Prerequisites

• Board admin rights on the target board. Non-admins cannot create or edit Butler rules.
• Butler power-up enabled on the board. In Trello, Butler is accessed via the board menu button labeled Butler.
• A clear due-date pattern. Decide the offset and whether it applies to all lists or only specific lists.

Rule conflicts are a practical risk. Multiple rules can fire on "a card is created". If another rule also sets a due date, the last executed action wins and the result is unpredictable.

Create the auto-due-date rule

Open the target board in Trello web. Click the Butler button in the board menu at the top of the board.

1. Choose Create rule. Butler offers a builder for rules and a command-line style builder.
2. Set the trigger. Select "A card is created". Add a scope if needed, for example "in list {list name}" or "in board {board name}". Scoping reduces unintended matches.
3. Add the action. Select "Set due date". Choose a relative date such as +7 days from creation. The offset is entered as a number of days. You can also set a specific time of day if your workflow requires it.
4. Name the rule descriptively, e.g., "Auto due +7d on new cards". A clear name helps future audits.
5. Save and enable the rule. Butler shows the rule in the board’s Butler rules list with status enabled.

Example configuration summary: Trigger = A card is created in board {board name}; Action = Set due date to +7 days from now. This is a board-level rule, not per-list unless scoped.

Expected checks

Validate the rule without assuming it works.

• Open the Butler rules list for the board and confirm the new rule is listed, enabled, and shows the correct trigger and action text.
• Create a test card in the scoped list. Open the card and check the due date field. It should reflect creation date plus the configured offset.
• Open the board calendar view. The test card should appear on the expected date.
• Check the board activity feed. Butler logs rule executions as automation events. An entry for the rule name when the card was created indicates the rule fired.

If the due date is missing, review the trigger scope and action parameters. If the rule is listed but not firing, confirm it is enabled.

Recovery and limitations

Butler rules change board behavior. Recovery options are edit, disable, or delete.

• Edit the rule via the Butler rules list to change offset, scope, or add conditions.
• Temporarily disable Butler for the board to restore fully manual due-date handling.
• Delete the rule if it is no longer needed. Deletion is permanent for that rule definition.

Limitations to plan for: Butler cannot set a due date in the past relative to creation. Relative dates are calculated at execution time, so time zone differences between Trello server time and your local view can shift the displayed date by a day. Rules do not retroactively update existing cards, only cards created after the rule is enabled.

Keep the rule list small and named consistently to avoid hidden conflicts. Review rules quarterly when board processes change.