Workflow triggers

Triggers define when a workflow runs. Each workflow has exactly one trigger. This reference covers all available trigger types.

​

Event triggers

Event triggers fire when something happens in Slant.

​

Tag added

Fires when a specific tag is added to a household. Use cases:

• Start onboarding when “New client” tag is added
• Trigger follow-up when “Hot lead” tag is applied

​

Household created

Fires when a new client or prospect is created. Use cases:

• Welcome email for new prospects
• Initial task creation for new clients

​

Prospect promoted

Fires when a prospect is converted to a client. Use cases:

• New client onboarding sequence
• Celebration notification to team
• Create client-specific project

​

Attribute updated

Fires when a specific field changes on a record. Use cases:

• Alert when AUM crosses a threshold
• Update tier when client status changes

​

Email received

Fires when an email is received from a client or contact. Use cases:

• Auto-create task when client emails
• Route support inquiries

​

Record created

Fires when any record of a specific type is created. Use cases:

• Notify team when high-value opportunity created
• Validate task assignments

​

Meeting scheduled

Fires when a meeting is added to the calendar. Use cases:

• Create prep tasks for client meetings
• Send pre-meeting materials

​

Meeting completed

Fires when a meeting is marked as complete. Use cases:

• Create follow-up tasks
• Update review due date

​

Recording finished

Fires when a meeting recording finishes processing. Use cases:

• Notify that recording is ready
• Trigger transcript processing

​

Schedule triggers

Schedule triggers run on a regular basis.

​

Recurring

Runs on a schedule (daily, weekly, monthly). Use cases:

• Daily task summary
• Weekly pipeline review
• Monthly billing reminders

​

Date reminder

Fires relative to a date field (before, on, or after). Use cases:

• Birthday reminders (7 days before)
• Review due reminders (1 week before)
• Anniversary acknowledgments

​

Manual triggers

Manual triggers are activated by user action.

​

Magic button

Appears as a button on household records. Runs when clicked. Use cases:

• Quick actions like “Schedule review”
• On-demand processes like “Generate report”
• Ad-hoc workflows like “Send thank you”

​

Trigger conditions

Most triggers support conditions to filter when they fire:

​

Add conditions

​

Condition operators

​

Multiple conditions

Combine conditions with AND/OR logic:

• AND — All conditions must be true
• OR — Any condition can be true

​

Trigger data

Each trigger provides data that actions can use: Access this data in actions using variables like household.name.

​

Best practices

1. Be specific — Use conditions to avoid running on unwanted records
2. Test first — Verify triggers fire when expected
3. Consider volume — High-frequency triggers can create many runs
4. Document — Note why the trigger was chosen
5. Review periodically — Ensure triggers still match your needs

​

Next steps