Kanban Entry Triggers

Kanban Entry Triggers

Entry triggers automatically execute actions when a card enters (is moved into) a list. Use them to automate repetitive tasks and ensure consistency.

How Entry Triggers Work

1. A card is moved into a list (or created in a list)
2. The system checks for active entry triggers
3. Conditions are evaluated (if any)
4. If conditions pass, actions execute in priority order

Creating an Entry Trigger

1. Click the list menu (⋮)
2. Select Triggers → + Add Entry Trigger
3. Configure:
   • Name: Descriptive name for the trigger
   • Conditions: Optional rules for when to run
   • Actions: What to do when triggered
   • Priority: Execution order (higher runs first)

Available Actions

Entry triggers can execute any of these actions:

• Update Card: Change title, description, priority, deal value, dates
• Add Note: Attach a note to the card
• Add Tag: Apply tags to the card
• Move to List: Move card to another list
• Assign Card: Assign to a user
• Auto-Assign: Round-robin assignment
• Send Email: Send email notification
• Send Chat: Send a chat message
• Send Notification: In-app notification

Example Entry Triggers

"In Progress" list entry:

• Action: Assign card to kanban owner
• Action: Add "working" tag
• Action: Send notification to assignee

"Review" list entry:

• Condition: Card has "urgent" tag
• Action: Send email to reviewer
• Action: Update priority to High

"Won" list entry (for deals):

• Action: Update deal_status to "won"
• Action: Set actual_close_date to today
• Action: Send celebration notification

AI-Powered Decisions

Enable AI to make trigger decisions:

1. Toggle Use AI Decision
2. Enter a decision prompt
3. AI evaluates each card
4. Trigger only fires if AI approves

Example prompt: "Should this lead be assigned to the sales team? Only if the email mentions budget or timeline."

Best Practices

1. Name clearly: "On Enter: Assign to Sales Team"
2. Use conditions: Avoid triggering on every card
3. Set priorities: Control execution order
4. Test first: Use a test card before going live
5. Monitor: Check execution history regularly