Per-board rules that run actions when something happens. Pick a trigger (card.created, card.moved, card.due_soon, card.completed, card.commented, plus cross-app events from CRM and Booking Hub), add optional conditions (label is X, list is Y, due date is in range), then pick the actions to run in order.
Actions cover the practical work: move to a list, add or remove a label, assign someone, set a due date with a relative shortcut like +3d, post a comment, add a checklist item, or send a notification. Every rule has a Test rule dry-run so you can verify before enabling. Every run writes to an audit log so you can debug what fired and what didn't.
Key Benefits
Ten triggers covering card lifecycle events plus three cross-app triggers from CRM and Booking Hub.
Dry-run *Test rule* against any card before enabling — see the planned actions without executing them.
Per-rule audit log shows trigger, conditions matched, each action's outcome, and the first error if any.
Disabled rules don't count toward your plan's active-rule cap — park rules instead of deleting them.
Use Cases
Auto-stamp completion
Trigger: card.moved. Condition: listId = Done. Actions: set custom field "Completed at" = now, add label "Archived", post a comment "✅ Completed by {triggering_user}".
Overdue escalation
Trigger: card.due_passed. Condition: label ≠ Snoozed. Actions: add label "Overdue", notify each assignee, post a comment with the new due date if you also chain a set_due_date action.
CRM-driven moves
Trigger: crossapp.lead.status_changed → Won. Actions: move the linked card to Done on the Sales board, add label "Closed", notify the rep. Your sales team drives Task Hub without ever opening it.