Notification rules — configuration
This reference lists every configurable field of a notification rule. For the setup flow: Set up notification rules.
Event types
| Event | Triggered by | Available fields |
|---|---|---|
| Updates collected | New updates are ingested into the workspace | updates_count |
| Report created | A report was successfully generated (any type) | report_type |
| Scheduled report created | A new scheduled report was set up | schedule_frequency |
| User inactive | A user hasn’t been in the app for a while | inactive_days, user_role |
Condition fields
Conditions are optional. Without conditions the rule fires on every matching event.
updates_count
Available on: Updates collected.
The total number of updates the workspace has collected since it exists.
- Type: integer
- Operators:
=,>= - Typical values:
100,1000,5000,10000
= fires exactly when the number is reached (milestone). >= fires on every update from the threshold — combine with rate limit “Once per team” for a single notification.
report_type
Available on: Report created.
The type of the generated report.
- Type: enum
- Operators:
= - Values:
summary,analysis,list,linkedin_posts,conversation_starters,monthly_market_review
schedule_frequency
Available on: Scheduled report created.
The frequency of the scheduled report that was created.
- Type: enum
- Operators:
= - Values:
daily,weekly,monthly
inactive_days
Available on: User inactive.
Number of days without app activity.
- Type: integer
- Operators:
=,>= - Typical values:
5,14,30
user_role
Available on: User inactive.
Role of the inactive user.
- Type: enum
- Operators:
= - Values:
owner,admin,member
Operators
| Operator | Meaning |
|---|---|
= | Equal (exact value) |
>= | Greater than or equal |
No other operators are currently available. For more complex logic, catch the event with several rules.
Recipients
| Option | Who gets the email |
|---|---|
| Triggering user | The person whose action triggered the rule |
| Team owner | The owner of the workspace |
| All team members | All active members of the workspace |
For event-driven rules without user context (e.g. “Updates collected” is triggered by the collection backend), Triggering user behaves like Team owner.
Rate limits
| Rate limit | Behaviour |
|---|---|
| No limit | Rule fires on every matching event |
| Once per user | Each recipient gets at most one email over the lifetime of the rule |
| Once per team | The whole workspace gets at most one email over the lifetime of the rule |
To restart the rate-limit counter, the rule must be deleted and recreated.
Behaviour on recipient opt-out
Recipients can unsubscribe via the link at the bottom of every reminder or milestone email. The opt-out applies across workspaces for that recipient email address and covers all emails of type Milestone and Inactivity reminder. Report deliveries are not affected — they follow the report configuration.