Kanban Exit Triggers
Exit triggers execute automatically when a card leaves a list. Use them for cleanup, notifications, and transitional workflows.
How Exit Triggers Work
- A card is moved out of a list
- Exit triggers for the source list activate
- Conditions are evaluated
- Actions execute if conditions pass
Creating an Exit Trigger
- Click the list menu (⋮)
- Select Triggers → + Add Exit Trigger
- Configure trigger settings
- Add conditions and actions
- Save and activate
Common Exit Trigger Use Cases
Leaving "In Progress":
- Remove "working" tag
- Log time spent in list
- Clear assignee if moving back
Leaving "Review":
- Condition: Moving to "Done" (approved)
- Action: Add "approved" tag
- Action: Notify stakeholders
Leaving "Negotiation" (deals):
- Action: Update deal probability
- Action: Add negotiation notes
- Action: Update expected close date
Exit vs Entry: When to Use Each
| Scenario | Use |
|---|---|
| Welcome email when card arrives | Entry |
| Cleanup when card leaves | Exit |
| Notify on status change | Both |
| Set due date on arrival | Entry |
| Archive data on departure | Exit |
Create powerful workflows by using both:
Example: Task Tracking
- "To Do" → "In Progress" (Entry): Start timer, assign
- "In Progress" → "Review" (Exit): Stop timer, remove "working" tag
- "Review" Entry: Notify reviewer
- "Review" → "Done" (Exit): Log completion, celebrate
Execution Order
When a card moves between lists:
- Exit triggers from source list run first
- Entry triggers on destination list run second
Priority within each:
- Higher priority numbers run first
- Same priority runs alphabetically by name
Preventing Loops
The system prevents infinite loops:
- A trigger cannot move a card back to its source
- Circular movements are detected and blocked
- Maximum 10 trigger executions per card move
