Alert Enrichments: Get Notified on Matching Data
Set up an Alert enrichment that emails you when synced records match your conditions, with a cooldown to prevent notification floods.
2 min read
On this page
An Alert enrichment watches the data flowing through your feeds and emails you when a record matches your conditions. Unlike a Ruleset, an Alert never changes your data: it only notifies. Typical uses: flag any transaction over a threshold, watch for a specific merchant, or get pinged when a refund lands.
Before you start
How alerts fire#
Alerts are evaluated while a sync runs. Each record the sync processes is checked against the alert's conditions; matching records trigger a notification to your configured recipients. That has one practical consequence: an alert can only be as fresh as the feed it is attached to. A daily feed produces at most daily alerts, while an hourly feed (Professional and above) gets you close to real-time.
Creating an Alert#
Create the enrichment
On the Enrichments tab, click "Add an enrichment" and choose Alert in the New Enrichment dialog. (You can also create one from a feed's Mapping → Enrichments subtab, which attaches it to that feed automatically.)
Pick the data type
Choose which data type the alert watches (for most people, Transactions). The data type determines which fields you can use in conditions.
Build the condition (When)
Use the condition builder to describe what should trigger the alert. For example: Amount greater than 1000. Conditions can combine with AND/OR and nest into groups, exactly like Ruleset conditions, and they can use any field, not just enrichable ones.
Choose recipients (Email alert to)
Tick the workspace members who should receive the email. To alert someone who isn't listed, invite them in Settings → Members first.
Set a cooldown (optional)
Cooldown (minutes) is the minimum time between alerts for the same pattern. 0 means every match sends an email.
Attach and enable
In the Dependencies tab, tick the feeds this alert should watch (or leave it on all compatible feeds), then flip the switch at the bottom from Disabled to Enabled.

Cooldown prevents floods
What the email contains#
The alert email identifies which alert fired and includes the matching record's key details, such as the description, amount, date, category, and account name, so you can usually act without opening BankSync.
Examples worth copying#
Large transactions
Amount greater than 1,000: catch big debits the day they sync.
Watched merchant
Description contains a vendor you're keeping an eye on.
Refund landed
Description contains "REFUND" and Amount greater than 0.
Troubleshooting#
Alert not firing?
Related guides#
- Creating Enrichments: the Ruleset guide, including the shared condition builder.
- Memory: auto-learn: the third enrichment type, which learns your categorizations.
- Setting Up Scheduled Feeds: sync cadence determines how fresh your alerts are.
Use this page with your AI assistant
Every BankSync doc is available as plain Markdown for agents and LLMs.
