Move Card Automation Action

Move Card Automation Action

The Move Card action automatically relocates cards to different lists when triggers fire. Essential for workflow automation.

Configuration Options

Target List: Select the destination list for the card.

Position:

• Top: Card appears at the top of the list
• Bottom: Card appears at the bottom

Common Use Cases

Automatic progression: When a task is marked complete, move to "Done" list.

Escalation: When a card has been in a list too long, move to "Escalated".

Qualification: When form data indicates a qualified lead, move to "Qualified".

Approval workflow: When approval is granted, move to "Approved".

Loop Prevention

The system prevents infinite loops:

1. Same-list prevention: Cannot move to current list
2. Circular detection: Detects A→B→A patterns
3. Execution limit: Max 10 moves per trigger chain

If a loop is detected, the action is skipped and logged.

Trigger Chaining

When a card moves, it can trigger entry/exit triggers:

1. Exit trigger on source list fires
2. Card moves to destination
3. Entry trigger on destination fires
4. Those triggers may cause more moves

Be mindful of cascading effects.

Example Configurations

Auto-archive completed:

Trigger: Entry to "Done" list
Wait: 7 days
Action: Move to "Archive" list
Position: Bottom

Escalate overdue:

Trigger: Card due_date passed
Condition: Still in "In Progress"
Action: Move to "Escalated" list
Position: Top

Sort by priority:

Trigger: Priority changed to "urgent"
Action: Move to current list (reorder)
Position: Top

Cross-Board Movement

Currently, Move Card only works within the same board. For cross-board workflows, use webhooks or manual processes.

Best Practices

1. Test thoroughly: Unexpected moves are disruptive
2. Document logic: Comment why cards move
3. Use conditions: Only move when appropriate
4. Consider position: Top for urgent, bottom for queue
5. Watch for loops: Plan your trigger chain