Triggers & Conditions
Complete reference for all available workflow triggers and conditions in Command Center.
Available Triggers
Triggers are events that start a workflow. Every workflow must have exactly one trigger.
Data Event Triggers
Record Created
Fires when a new record is created (client, account, household, transaction, etc.)
Record Updated
Fires when an existing record is modified. Can be configured for specific fields.
Field Value Changed
Fires when a specific field changes value (e.g., segment changed, status updated).
Threshold Crossed
Fires when a numeric value crosses above or below a defined threshold (e.g., AUM > $1M).
Time-Based Triggers
Scheduled (Recurring)
Runs on a schedule - daily, weekly, monthly, or custom cron expression.
Date-Based
Fires based on date fields - birthdays, anniversaries, renewal dates (with offset options).
Inactivity Timer
Fires when a specified time has passed since last activity (e.g., no contact in 90 days).
External & Manual Triggers
Manual Trigger
Run on-demand by a user from a record or bulk selection.
Webhook Received
Fires when an external system sends data to a webhook URL.
Integration Event
Fires based on events from connected systems (CRM update, custodian sync, etc.).
Condition Types
Conditions filter when a workflow's actions should execute. Combine multiple conditions with AND/OR logic.
Field Comparison
Compare field values using operators: equals, not equals, contains, greater than, less than, is empty, is not empty.
Example: Client Segment equals "VIP"
Numeric Range
Check if a number falls within a specified range.
Example: AUM between $500,000 and $1,000,000
Date Comparison
Compare dates or check relative timeframes.
Example: Last Contact Date is more than 90 days ago
List Membership
Check if a value is in a predefined list.
Example: State is in ["CA", "NY", "TX"]
Related Record
Check conditions on related records (e.g., check advisor of a client).
Example: Advisor.Team equals "Private Wealth"
Condition Groups (AND/OR)
Combine multiple conditions with logical operators for complex filtering.
Example: (AUM > $500K AND Segment = "VIP") OR (Account Type = "Trust")
Pro Tips
- Use Field Value Changed triggers when you only want to act on actual changes, not every record update.
- For date-based triggers like birthdays, set an offset (e.g., 7 days before) to give yourself time to act.
- Start with broad conditions and narrow down as you learn which scenarios need different handling.