Signal rules — custom triggers.
Signal rules let you turn a multi-condition signal pattern into a persistent monitor. "VP Data hire AND Snowflake added in same 30-day window" → automatic alert + brief. Where Saved searches are about firmographic + persona criteria, Signal rules are about signal-pattern logic.
TL;DR
If [signal pattern] then [alert / auto-brief / both]. Rules combine signal types with AND/OR logic, time windows, and ICP thresholds. Most useful patterns: signal combos that don't exist as built-in detections (e.g., "funding + departure of incumbent vendor" — your specific churn-displacement pattern).
01What signal rules are
Custom multi-condition triggers. A rule defines: signals to watch + Boolean logic + time window + optional ICP filter + action when matched.
Different from saved searches: searches are about account criteria (firmographic + persona). Rules are about signal patterns over time. Use rules when "this combination of signals firing within X days" is what you're hunting.
02Rule syntax
The rule builder uses visual blocks (not code), but the underlying logic is straightforward:
AND [Signal B] occurs within [N days]
AND account ICP score >= [threshold]
THEN [alert · auto-brief · push to CRM · webhook]
Supports AND, OR, NOT logic; time windows (same day · 7 / 14 / 30 / 60 / 90 days); optional ICP and account-ownership filters.
03Common rule patterns
04What rules can do
- Alert: Slack, email, in-app, webhook (Pro+)
- Auto-brief: generate a brief immediately on match (Pro+ — counts against monthly quota)
- Auto-tag: apply a workspace tag to the account (e.g., "hot")
- Push to CRM: create or update account in your CRM with rule-generated note
- Queue for review: stage the match in a "pending" list instead of acting
05Performance and limits
| Tier | Active rules | Actions per rule |
|---|---|---|
| Free | 2 | Alert only |
| Pro | 10 | Alert + auto-brief + auto-tag |
| Company | 50 | All actions + webhook |
Rules evaluate continuously. Match latency is <5 minutes from the second signal firing.