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

Answer to the Core Questions

1. Can a Butler rule author force a silent or forced‑notify action? No. Butler does not expose a rule‑level or board setting that lets the author suppress or guarantee notifications for a specific member. All notifications resulting from a Butler action are routed through Trello’s standard notification engine, which respects the recipient’s own watch and channel preferences.

2. How does Trello evaluate notifications for a Butler rule that adds a member or posts a comment? The engine processes automated actions exactly as it does manual ones. For each affected member:

• It checks the board‑watch status: if the member is unwatching or has muted the board, the activity is not shown in the board activity feed.
• It then applies the member’s account‑level in‑app and email notification preferences independently. A member can be watching the board but have email notifications turned off (or vice‑versa). The rule’s action will appear in‑app if that channel is enabled, and an email will be sent only if the email channel is enabled.

3. How do calendar‑feed Power‑Ups and other connected services react to Butler‑triggered due‑date changes when watch settings differ? Power‑Ups poll Trello data on their own schedule (usually every few minutes). A Butler change to a due date updates the card’s metadata; the next Power‑Up sync will pick up that change. Alerts generated by the Power‑Up (e.g., calendar invites or reminders) are governed by the Power‑Up’s configuration and are not filtered by the board‑watch state or by Trello’s email preferences. Therefore, a member who has muted the board may still receive a calendar alert if the Power‑Up’s settings allow it.

Likely Behavior and Practical Verification

Because the notification logic is version‑sensitive and can vary by plan tier (Free, Business Class, Enterprise), it’s best to confirm the behavior in a controlled environment:

1. Create a test board and add two test accounts.
   • Account A: Watch the board, enable both in‑app and email notifications.
   • Account B: Unwatch or mute the board, disable email notifications (but keep in‑app on to see the difference).
2. Set up a simple Butler rule that triggers on a card being moved to a list and performs:
   • Adds Account B as a member to the card.
   • Posts a comment on the card.
3. Run the rule and observe:
   • Account A should see the comment in‑app and receive an email.
   • Account B should see the comment in‑app (if the in‑app channel is on) but receive no email, and the board activity feed should not show the event if the board is muted.
4. Change the due date of the card via another Butler rule and monitor the calendar Power‑Up (e.g., Google Calendar). Verify that the calendar feed updates on its next sync and that any reminder alerts are sent according to the Power‑Up’s settings, regardless of the board‑watch state.

Repeat the test after toggling each account’s in‑app and email preferences to confirm the independent filtering.

Missing Diagnostic Detail

To fine‑tune the recommendation, could you confirm which Trello plan you’re using (Free, Business Class, or Enterprise)? Plan tier can influence default notification behavior and Power‑Up limits.