Butler Automation and Trello Notification Settings: Reliable Alert Targeting Across Watch States

Butler rules execute actions, but whether those actions alert a person depends on that person's own board-watch and account notification settings rather than on the rule author's configuration. No documented rule-level switch exists to mark an automated action as silent, so the same rule can notify one member and stay invisible to another who has unwatched or muted the board.

Under current Atlassian-administered Trello, account settings separate in-app notification preferences from email notification preferences, so a board-level watch change does not guarantee both channels stop. Integrations outside Trello's notification core, such as calendar feed Power-Ups, deliver alerts on their own schedules, bypassing per-board watch settings. Behavior can also vary by plan tier and by whether a rule is card, board, or workspace scoped, so practical verification on a test board is advisable.

• Is there any documented Butler command or board setting that lets a rule author control whether an automated action generates a notification for each affected member?
• When a Butler rule adds a member or posts a comment, does Trello's current notification engine evaluate the recipient's board-watch state and separate email preferences independently, or is there a unified subscription model?
• How do calendar-feed Power-Ups and other connected services interact with Butler-triggered due-date changes when per-board watch settings are inconsistent across team members?