> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slant.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Triggers
> Reference for all automation trigger types — the events that start an automation.
A trigger defines when an automation runs. Every automation has exactly one trigger. When the trigger's conditions are met, the automation starts and runs through its actions in order.
Most triggers support an optional **filter group** — a set of conditions that narrow which records activate the automation. For example, a "Household created" trigger can be filtered to only fire for clients in a specific tier.
## Household triggers
### Household created
Runs when a new household is created.
| Field | Description |
| ------------------ | --------------------------------------------------------------------------- |
| **Household type** | Required. Choose **Prospect** or **Client**. |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Tag added
Runs when a tag is added to a household.
| Field | Description |
| ---------- | ----------------------------------------------------------------------------------------------- |
| **Tags** | Required. Select one or more tags. The automation fires when any of the selected tags is added. |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Prospect promoted to client
Runs when a prospect is promoted to a client.
| Field | Description |
| ---------- | --------------------------------------------------------------------------- |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Magic button (household)
Adds a custom button to household records. The automation runs when someone clicks the button. See [Magic buttons](/platform/automations/magic-buttons) for details.
| Field | Description |
| ------------------ | ------------------------------------------------------ |
| **Household type** | Required. Choose **Prospect** or **Client**. |
| **Title** | Required. The label shown on the button. |
| **Description** | Required. A short explanation of what the button does. |
| **Icon and color** | Required. Choose an icon and color for the button. |
## Task triggers
### Task created
Runs when a new [task](/activity/tasks/overview) is created.
| Field | Description |
| ---------- | ---------------------------------------------------------------------- |
| **Filter** | Optional. Add conditions to narrow which tasks trigger the automation. |
### Task completed
Runs when a task is marked as completed.
| Field | Description |
| ---------- | ---------------------------------------------------------------------- |
| **Filter** | Optional. Add conditions to narrow which tasks trigger the automation. |
## Meeting triggers
### Meeting scheduled
Runs when a new [meeting](/activity/meetings/overview) is scheduled.
| Field | Description |
| ---------- | ------------------------------------------------------------------------- |
| **Filter** | Optional. Add conditions to narrow which meetings trigger the automation. |
### Meeting completed
Runs when a meeting is marked as completed.
| Field | Description |
| ---------- | ------------------------------------------------------------------------- |
| **Filter** | Optional. Add conditions to narrow which meetings trigger the automation. |
### Magic button (meeting)
Adds a custom button to meeting records. See [Magic buttons](/platform/automations/magic-buttons) for details.
| Field | Description |
| ------------------ | ------------------------------------------------------ |
| **Title** | Required. The label shown on the button. |
| **Description** | Optional. A short explanation of what the button does. |
| **Icon and color** | Optional. Choose an icon and color for the button. |
## Opportunity triggers
### Opportunity created
Runs when a new [opportunity](/activity/opportunities/overview) is created.
| Field | Description |
| ---------- | ------------------------------------------------------------------------------------------------------------------ |
| **Filter** | Required. Must include a pipeline condition so the automation only fires for opportunities in a specific pipeline. |
### Stage moved
Runs when an opportunity moves to a different stage.
| Field | Description |
| ---------- | ------------------------------------------------------------------------------------------------------------------ |
| **Filter** | Required. Must include a pipeline condition so the automation only fires for opportunities in a specific pipeline. |
## Project triggers
### Project created
Runs when a new [project](/activity/projects/overview) is started.
| Field | Description |
| ---------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Project type** | Required. Select one or more project types. The automation fires when a new project of any selected type is created. |
### Milestone changed
Runs when a project moves into a milestone.
| Field | Description |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Project type** | Required. Select one or more project types. |
| **Milestone entered** | Required. Select one or more milestones. Options are limited to the milestones in the selected project types. |
### Project completed
Runs when a project is marked complete.
| Field | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Project type** | Required. Select one or more project types. The automation fires when a project of any selected type is completed. |
## Reminder triggers
Reminder triggers fire at a configurable number of days (or other interval) before a date-based event. They are useful for proactive outreach — birthday cards, review preparation, follow-ups.
### Birthday reminder
Runs a set number of days before a person's birthday.
| Field | Description |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Timing** | Required. Choose when to trigger: same day, 1–3 days before, 5 days before, 1 week before, 2 weeks before, or 1 month before. Default: 1 week before. |
| **Filter** | Optional. Add conditions to narrow which people trigger the automation. |
### Client review reminder
Runs before a client's annual review date.
| Field | Description |
| ---------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Timing** | Required. Choose when to trigger: 1 week, 2 weeks, 3 weeks, 1 month, 2 months, or 3 months before. Default: 2 weeks before. |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Client anniversary reminder
Runs before a client's anniversary date.
| Field | Description |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Timing** | Required. Choose when to trigger: same day, 1–3 days before, 5 days before, 1 week before, 2 weeks before, or 1 month before. Default: 1 week before. |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Client touchpoint reminder
Runs relative to a client's next touchpoint due date.
| Field | Description |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Timing** | Required. Choose when to trigger: same day, 1–3 days before, 5 days before, 1 week before, or 2 weeks before. Default: same day. |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Client custom date reminder
Runs relative to a date stored in a custom date field on the household. This lets you create reminders for any date you track — tax deadlines, policy renewals, or other important dates.
| Field | Description |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Custom field** | Required. Select which date custom field to use. |
| **Recurrence** | Required. Choose **Annual** (triggers every year on the same month and day) or **Exact date** (triggers once on the specific date). Default: annual. |
| **Timing** | Required. Choose when to trigger: same day, 1–3 days before, 5 days before, 1 week before, 2 weeks before, or 1 month before. Default: 1 week before. |
| **Filter** | Optional. Add conditions to narrow which households trigger the automation. |
### Meeting reminder
Runs before a scheduled meeting.
| Field | Description |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Timing** | Required. Choose when to trigger: 30 minutes, 1 hour, 2 hours, 24 hours, morning of, 1–3 days before, 5 days before, 1 week before, or 2 weeks before. Default: 1 hour before. |
| **Filter** | Optional. Add conditions to narrow which meetings trigger the automation. |
## System triggers
### Email received
Runs when an email is received on a connected email integration.
| Field | Description |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Email integration** | Required. Select which connected email account to monitor. |
| **Trigger for** | Required. Choose **Emails from unknown senders** (the default) or **Emails from existing contacts**. |
| **Only continue if...** | Add conditions with **Add condition** to narrow which emails trigger the automation, such as filtering by the sender's email address. Required when **Trigger for** is set to **Emails from unknown senders**; optional for **Emails from existing contacts**. |
When **Trigger for** is **Emails from unknown senders**, you must add at least one sender condition under **Only continue if...** before you can save. This keeps the automation from running on every inbound email. When **Trigger for** is **Emails from existing contacts**, the condition is optional.
## FAQ
No. Each automation has exactly one trigger. If you need the same actions to run for different events, create a separate automation for each trigger.
Filters let you narrow which records activate the automation. You can combine multiple conditions with AND/OR logic. Only records that match all filter criteria will trigger the automation.
Trigger filters decide whether the automation runs at all. [Branch](/platform/automations/actions#branch) conditions run inside the automation and route records down different paths based on criteria you define.