Use this file to discover all available pages before exploring further.
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.
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.
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.
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.
How do filter conditions work on triggers?
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.
What is the difference between a trigger filter and a branch condition?
Trigger filters decide whether the automation runs at all. Branch conditions run inside the automation and route records down different paths based on criteria you define.
