# Triggers

> The complete trigger reference — form submitted, lead captured, card created, card moved, call missed, voicemail left, call ended — and how trigger filters narrow each one.

Triggers are the **Starts when** panel of a workflow. A workflow can listen for several; each trigger can be narrowed with filters (a specific form, a specific board and column). When the event fires, the workflow runs with the person's context — name, phone, email — available as variables in every step.

## The trigger reference

| Trigger | Fires when | Filter |
| --- | --- | --- |
| A form is submitted | Somebody fills a [CRM form](/docs/crm/forms) — yours embedded anywhere, or a partner's site posting through a [Connections key](/docs/crm/connections) | Any form, or one specific form |
| The AI captures a lead | A conversation — chat, call, or text — produced a lead via the [lead tool](/docs/ai/tools) | — |
| A card lands on a board | A new deal appears in a column, created by anyone or anything | Any board, or one board + column |
| A card moves to a column | Somebody — human or AI — drags a deal, or a tool moves it | Board + destination column |
| A call goes unanswered | The number rang and nobody — human or AI — picked up | — |
| A voicemail is left | The caller spoke after the beep; the transcript is available to the run | — |
| A call ends | The [receptionist](/docs/doors/ai-receptionist) finished with somebody; summary and extracted variables available | — |

## Card triggers are the cadence engine

Because *card moved* is a trigger, the board **is** the sequence: *New* → intro email; *Contacted* → day-2 SMS; *Warm* → WhatsApp. Managing the relationship becomes drag-a-card, and the drag can come from a human or from the AI mid-conversation.

> **SEVERAL TRIGGERS, ONE WORKFLOW:** A "we missed you" workflow usually listens for both *call goes unanswered* and *voicemail left* — same steps, two ways in. Add both in the Starts when panel rather than cloning the flow.