Signals
A signal is a workspace rule that fires when an account (or related entity) meets a defined condition—often on a metric threshold, a prediction state, or another modeled attribute. Signals bridge analytics and action: they can appear on Timeline, drive Notifications, inform CRM sync mappings, and power AI agents triggers when you need more than a single static alert.
Common signal patterns
| Pattern | Example use |
|---|---|
| Metric threshold | “Support tickets opened in 7d > 5” for proactive outreach. |
| Prediction-based | “Churn outcome with high confidence” to prioritize QBRs. |
| Stage or funnel | “Account dropped two stages in 30d” for RevOps review. |
| Composite | Combine properties and metrics when your workspace supports richer rule builders. |
Exact operators depend on the metric type (numeric, categorical, windowed).
Where signals surface for day-to-day users
- Accounts filters — Narrow the grid to accounts that currently satisfy (or recently triggered) selected signals, depending on how your workspace wires filters.
- Timeline — Toggle Include signals to see firings alongside behavioral events on an account.
- Notifications — Built-in Slack or Teams posts can subscribe to signal-driven events.
- CRM sync — Optional outbound fields may include signal state when mapped.
For branching playbooks or LLM summarization, prefer AI agents over stacking dozens of overlapping signals.
Related
- Accounts view — signal-aware filtering.
- Timeline — include signal events in the feed.
- Metrics — what thresholds measure.
- Notifications — channel delivery.
- Predictions — prediction-backed conditions.