In-app notifications
Every background job, scheduled run, and credit alert lands in a shared team inbox in the dashboard — zero setup, visible to your whole organization.
In-app notifications
Long-running work shouldn't need babysitting. Batch enrichments, exports, scheduled searches, and lookups all run in the background. When they finish (or fail), the Notifications bell in the dashboard sidebar tells your team. No polling, no configuration, no wondering whether the export is done yet.
How it works
- One inbox for the whole organization. Notifications are org-wide: every member sees the same feed, so nobody has to forward "the batch finished" to the person who kicked it off.
- On by default. Joining an organization is the setup — there's nothing to enable.
- The bell shows an unread count; clicking a notification takes you to the relevant page (the finished export, the saved-search run, the tracker list).
- Each event notifies once — duplicate alerts for the same run are suppressed.
What notifies you
| Area | You're notified when |
|---|---|
| Batch jobs | A batch contact enrichment or batch live enrichment finishes — or fails |
| Searches | An async combined search, Google Maps search, or local business search completes |
| Lookups | GitHub lookups, GitHub → LinkedIn matching, domain lookups, and social-media lookups finish |
| Exports | A prospect or company CSV export is ready (or the export failed) |
| Audiences | An audience build or enrichment finishes |
| Saved searches | A saved search run completes (with what changed and what it cost), and a heads-up before each scheduled run |
| Trackers | A tracker list refresh completes, and a heads-up about a day before one is due |
| Contact reveal | A contact reveal completes |
| Job changes | A person on a job-change list changed jobs, one notification per person. For new setups, watch job changes with a tracker list |
| Credits | Your balance runs low (below) |
Failures notify too. A batch that errors out is something you want to hear about immediately, not discover at the end of a quiet afternoon; failure notifications look just like completions, with the failure called out.
Credit alerts
When your organization drops to 10% or less of its billing period's credits, you get an in-app alert (and an email). At zero, the wording escalates to out-of-credits. The alerts are deliberately polite:
- at most 3 per billing period,
- at least 7 days apart,
- and skipped entirely when your balance hasn't changed since the last one.
The email version carries an unsubscribe link (org-level). Unsubscribing stops the credit emails only. In-app alerts keep working, so the signal never fully disappears. See Billing & credits for what to do when the alert fires: top-ups, auto top-up, plan changes.
Notifications vs webhooks
Same moments, different audiences:
| In-app notifications | Webhooks | |
|---|---|---|
| For | Your team, in the dashboard | Your systems, at your HTTPS endpoint |
| Format | Human-readable alert | Machine-readable JSON payload |
| Setup | None | Register an endpoint and pick events |
Most events fire both channels. A few lean one way: saved-search completions are notification-and-email first, and credit alerts don't have a webhook (if your integration needs to react to those, poll the relevant read endpoints).
What also arrives by email
Some events send an email too, so the person who needs the result gets it without opening the dashboard:
| Event | |
|---|---|
| Credits running low | To every member of the organization (one unsubscribe link stops these for everyone) |
| A credit top-up completes, or auto top-up hits its cap | A confirmation for your records |
| A CSV export is ready (audience companies or prospects, full lists) | Download links, to the person who asked for the export |
| A saved search run finishes, and the heads-up before a scheduled run | What changed and what it cost |
| A Google Maps area search, domain lookup, or Mosaic run finishes | Download links for the results |
| Tracked people change jobs | A digest listing the moves |
Notifications go to the dashboard and email only; there's no built-in Slack or Teams delivery. To post events into a chat tool, point a webhook at it, directly or through an automation tool.
What you can't configure (yet)
There are no per-category mute switches or per-user notification preferences: the feed is intentionally shared and always-on. The one control that exists today is the credit-email unsubscribe described above. If notification preferences matter for your team, tell us — this section will change when they ship.
Use cases
- Ops lead running batch pipelines: kick off a 50,000-row enrichment, close the tab; the whole team knows when it lands, including the one who consumes the output.
- AE waiting on an export: the ads-format CSV announces itself instead of being refreshed for.
- Admin catching credit burn: the 10% alert arrives while there's still budget to act, and it won't nag three times a week while you're deciding.
Credits
Notifications are free — they're a byproduct of work you've already paid for, never a charged operation.
Webhooks & Notifications
Get notified when background jobs finish — machine-readable webhooks for your systems, configurable in the dashboard or through the API.
Job changes
Find out when the people you care about change jobs. Use Tracker for new integrations; job-change lists stay available for existing ones.