Can an alert use more than one delivery channel?
Yes. Combine instant email, hourly/daily/weekly digests and a webhook on a Matching data alert. Choose the recipients and timing for each channel, with matches also visible in the Alerts feed.
Get notified about changes and deadlines.
Spot delivery changes, approaching deadlines and unanswered emails without repeatedly checking your records. Combine alert conditions, choose email, digests or webhooks, and control how often your team is notified.
| Update received | Delivery date |
|---|---|
| 10 October | 18 October |
| 14 October | 22 October |
- Alert condition
- Delivery date changes
- Only when
- Order status is Active
- Notify
- Operations team
- Channel
- Instant email
Check data as it changes or on a schedule
Check changes as they happen
Choose the emails or data you want to watch, then describe what deserves attention. Get notified when an active order’s delivery date changes, a price rises beyond your threshold or a required detail is missing. Combine conditions so the notification fits the work your team cares about.
Wait for several matching changes before notifying the team when one update is not enough. For a change alert using one group of conditions, choose a count across the saved list or separately for each tracked supplier or order over 24 hours or seven days. Each change contributes to the count, and the period restarts when you save or re-enable the alert.
- Watch new emails or items, changed details and missing values. Set a minimum amount for a numeric change.
- Open the matching information and the conditions behind an alert when you review it.
Check deadlines and email activity on a schedule
Get a prompt before a notice deadline or find sent emails still waiting for a reply. Scheduled checks look for the dates and email activity you choose, even when no new message has arrived.
- Renewal review: an active agreement’s notice deadline is within 30 days.
- Unanswered mail: a sent email has had no reply for more than three days.
- Reply activity: a message has more than ten replies, or its first reply took longer than seven days.
Configure notifications
-
Choose email, digests or webhooks
Choose an immediate email, a regular digest or a webhook for another system. Combine channels on a Matching data alert when different recipients need different ways to receive the update. Each match is also available in the Alerts feed.
- Instant email: notify selected team members and include links to the matching item and supporting information.
- Digest email: gather matches into hourly, daily or weekly summaries. Choose daily or weekly delivery times in your organization’s timezone.
- Webhook: send alert data to a connected system through an authenticated HTTPS endpoint.
-
Keep repeated matches from filling the inbox
Group repeated matches for the same item and conditions over an hour, day or seven days. Choose how often each channel can notify your team and set a minimum gap between notifications.
Keep all individual matches in the feed, including ones that did not send another notification. A repeat notification requires a new match after the chosen interval; use follow-up due dates and reminders for ongoing tasks.
-
See what an alert would catch before you enable it
Preview matching examples and, where available, estimated notifications. See who would receive them and why other recipients are excluded, while the alert stays inactive.
After enabling the alert, review delivered, skipped, failed and retrying runs in Delivery history. Retry eligible failed deliveries using the recorded match.
- Preview estimates help you choose the setup; delivery history records what was actually sent.
Review patterns in the Alerts feed
Spot unusual weekly changes
Spot changes in weekly activity, the concentration of a category or the average of an amount. Choose a prepared dataset of extracted rows or tracked items for a Weekly change alert, then select the measure you want to watch.
Compare completed weeks against a baseline built from enough retained history. Review unusual weeks and their supporting measurements in the Alerts feed. Weekly change alerts appear in the feed; email and webhook notifications use Matching data alerts.
See signals without writing a rule
See unusual activity in your connected sources or a drop in how often an extracted field is filled in. Ambient signals use the available history to highlight these patterns without asking you to set up an alert rule.
Review the measurements and supporting information in the Alerts feed to decide what needs investigation. Ambient signals appear there without sending external notifications.
Optional follow-up
Create follow-up when someone needs to act
Add an optional follow-up action to a Matching data alert when a change needs someone to act. Give the request an owner and, when useful, a due date. Keep notes and the outcome beside the information that prompted it.
Use it to confirm a revised delivery date, review a notice deadline or answer a request for evidence. Your team records the decision and completes the follow-up.
Common questions
Can we check a rule before it sends notifications?
Yes. Preview matching examples, notification estimates where available and who would receive them. The preview leaves the alert inactive and sends nothing. Grouping and repeat settings can reduce the notifications sent compared with the estimate.
Do weekly changes and ambient signals send emails too?
Weekly changes and Ambient signals appear in the Alerts feed. Set up a Matching data alert for a supported condition when you want email or webhook notifications.
Catch the update your team needs to act on
Try a changed delivery date, an approaching notice deadline or an unanswered email. See the matching information and choose how your team should hear about it.