Screen new HubSpot contacts for data breach exposure
The moment a new contact lands in HubSpot, we check their email against known data breaches and flag the high-risk ones so your team can act fast.
Integrations
Have I Been Pwned
HubSpot
Slack Bot
Type
Categories
- Operations
- Customer Support
Run this automatically whenever a new contact is created in HubSpot. HubSpot sends an outgoing webhook for new contacts, so use that as the trigger. From the webhook payload, read the new contact's email address and their HubSpot contact record ID.
Check the contact's email against Have I Been Pwned. Call Get Breaches for Account and Get Pastes for Account with that email. Have I Been Pwned returns an empty 'not found' result when an address is clean, so if both calls come back with no breaches and no pastes, treat the contact as clean and stop right there: do not write a note, do not change any field, and do not send any alert.
If there are breaches or pastes, write a short plain-language risk summary an account owner can read at a glance. Name each breach, say when it happened, and list which classes of data were exposed (for example email addresses, passwords, phone numbers, physical addresses, or credit card and bank details). Lead with the most sensitive exposures so the risk is obvious in the first line.
Attach that summary to the contact with HubSpot's Create Note, associated with the contact record so it shows up on their timeline. Then record the risk on the contact with Update Contact: set a breach-risk property to high when passwords or financial data were exposed, and to medium or low for other breaches based on how sensitive the exposed data is.
Only alert a human when the exposed data includes passwords or financial data such as credit card numbers or bank account details. In that case, identify the contact's owner in HubSpot, look up their Slack account by their email address, and send them a direct message with Slack Bot's Send a Message. Summarize the breach risk and recommend the customer reset their passwords and turn on multi-factor authentication. If the owner cannot be matched to a Slack user, post the same alert to a designated security or customer-success channel instead. For breaches that do not involve passwords or financial data, skip the Slack alert to keep the noise down: the note and the risk field are enough.
What it does
- Automatically checks every new HubSpot contact's email against a database of known data breaches and leaks.
- Writes a plain-language risk summary onto the contact record listing which breaches they appeared in, when, and what kind of data was exposed.
- Marks each contact with a breach-risk level so your team can spot the highest-risk customers at a glance.
- Sends a Slack alert to the contact's owner only when passwords or financial details were exposed, so no one gets spammed with low-risk noise.
What you’ll need
- A HubSpot account where new contacts are created.
- A Have I Been Pwned subscription (their breach-checking service requires a paid key).
- A Slack workspace for the alerts.
- A field on your HubSpot contact record to store a breach-risk level (a simple custom property).
How to customize it
- Change what counts as high risk, for example treat any exposed password as urgent or add more data types to the sensitive list.
- Choose who gets the Slack alert: the contact owner, a shared security channel, or your customer-success team.
- Adjust the wording of the risk summary and the labels used for the risk levels on the contact.
Use cases
- Lead Enrichment
- Notifications & Alerts
