Triggers
Manual plus the five trigger kinds and what each one fires on.
A trigger defines what causes an automation to run. The automation builder's Trigger field offers a kind select — manual, or one of five event kinds carried over from the pipeline's earlier rule engine.
Manual
No event — the automation only runs when an editor clicks Run now on the automations list. This is the default for a new automation, and the only kind that doesn't need a condition.
Research completed (cr_completed)
Fires when a client research record moves to the completed state. This is the most common trigger for scoring-based automation.
Use this trigger to:
- Draft an outreach sequence after a research run completes.
- Notify a team member when a high-priority prospect is researched.
Condition: an optional score threshold — the automation only fires when the propensity score is at or above the value you set. Leave it blank to fire on any completion.
Score crossed threshold (score_crossed)
Fires when a client's propensity score crosses a threshold, either upward or downward.
Use this trigger to:
- Alert the team when a prospect crosses from "medium" to "high" propensity.
- Trigger re-research when a score drops significantly (suggesting the prospect's situation has changed).
Condition: a required score threshold (0–100) and direction (above / below).
Stage dwell exceeded (stage_dwelled)
Fires when a deal has been in a stage for longer than a specified number of days.
Use this trigger to:
- Notify the deal owner when a deal goes quiet.
- Automatically draft a follow-up sequence for stalled deals.
Condition: a required number of dwell days, and an optional stage ID to scope the trigger to one specific stage (leave blank to match any stage).
Signal event received (signal_event)
Fires when a signal arrives for a client you are tracking. Signals come from configured signal sources such as company news.
Use this trigger to:
- Re-research a client when their company announces a funding round.
- Draft outreach when a company news signal matches a kind you care about.
Condition: an optional signal kind (funding, leadership change, press, M&A, layoff, product launch, other) — leave blank to match any signal kind.
No activity for N days (nth_day_no_touch)
Fires when a deal has had no activity logged for N consecutive days. Similar to stage dwell, but based on outreach/activity cadence rather than pipeline stage.
Use this trigger to:
- Surface deals that have gone quiet after initial contact.
- Remind the team to follow up with high-propensity prospects that haven't been touched recently.
Condition: a required number of days without activity.
See also: conditions, steps, overview.