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.

Build an email alert from condition to enabled state.

Before you start

Alerts run during syncs, so you need at least one feed that syncs the data you want to watch. If you haven't built a feed yet, start with Creating Your First Feed.

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#

  1. 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.)

  2. 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.

  3. 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.

  4. 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.

  5. Set a cooldown (optional)

    Cooldown (minutes) is the minimum time between alerts for the same pattern. 0 means every match sends an email.

  6. 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.

The Alert configuration form: a When condition reading Amount greater than 500, an Email alert to section listing workspace members Ada Lovelace, Grace Hopper, and a third member as checkboxes with Ada selected, and a Cooldown (minutes) field set to 60 with the note that 0 means every match.
An Alert: condition, recipients picked from workspace members, and a cooldown.

Cooldown prevents floods

The cooldown is tracked per pattern (for example, per merchant), not per alert. If a backfill suddenly syncs thirty matching transactions from the same merchant, a 60-minute cooldown means you get one email for that merchant, not thirty.

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?

Check four things: (1) the alert is Enabled, (2) it is attached to the right feed in the Dependencies tab, (3) the feed actually synced since you created the alert (alerts evaluate during syncs), and (4) the cooldown isn't suppressing repeats. Then loosen the condition: try 'contains' instead of equals, and confirm the value's spelling.

Use this page with your AI assistant

Every BankSync doc is available as plain Markdown for agents and LLMs.