What happens if a new contact only has a personal email like gmail.com?

We skip those by default. You only get notes and Slack alerts for real business contacts, so your channel stays high signal.

What if the contact has no email and only a company name?

We fall back to BuiltWith's company-to-website lookup to find the most likely root domain, then run the tech-stack scan on that domain instead.

Where does the enrichment actually live inside HubSpot?

It gets saved as a Note on the contact, and also linked to the associated company record. Anyone on your team sees it in the contact timeline the moment they open the record.

Do I need a paid BuiltWith plan for this to work well?

Yes. The deep technology categories, vendor signals, and spend estimates that make the alerts useful live behind BuiltWith's paid Domain lookup. A free key returns a much thinner result.

Can I send the alert somewhere other than Slack?

Yes. When you customize the prompt before generating the workflow, swap the Slack step for email, Microsoft Teams, or a HubSpot task assigned to the right rep.

Auto-Enrich New HubSpot Leads with BuiltWith Tech Stack Data

Build me an agent-style workflow that enriches every new HubSpot contact with their company's tech stack the moment they are created, then alerts my sales team in Slack.

Trigger: a HubSpot outgoing webhook for new contact creation. When the webhook fires, the workflow receives the contact's properties (email, first name, last name, company name, HubSpot contact ID, associated company ID if any) and the agent starts.

Step 1. Read the email address from the contact and extract the domain. If the domain is a personal email provider (gmail.com, googlemail.com, outlook.com, hotmail.com, live.com, yahoo.com, aol.com, icloud.com, proton.me, protonmail.com), stop immediately and exit. We only enrich real company leads.

Step 2. If the contact has no email but does have a company name, call BuiltWith's Company to URL API with the company name to find the most likely root domain. If neither email nor company name is present, stop and exit. Otherwise, use the email domain as the root domain to look up.

Step 3. Call BuiltWith's Domain API Lookup on the root domain. Pull the full technology profile: technologies grouped by category (ecommerce, payments, analytics, CRM, marketing automation, hosting, CDN, ads), the meta block (company name, country, social profiles, employee and revenue estimates), and any spend estimates BuiltWith returns.

Step 4. Reason about fit against my ICP. My ICP is: [REPLACE WITH YOUR ICP, e.g. 'growth-stage ecommerce brands on Shopify Plus doing more than $5M GMV']. Identify the three or four most telling technologies, the ones that signal fit, not generic ones like jQuery or Google Fonts. Assign a fit rating using emoji: 🔥 high fit, 👍 medium fit, ❄️ low fit, with a one-sentence reason.

Step 5. Use HubSpot's Create Note operation to write a structured tech-stack summary into HubSpot. Associate the note with both the contact and the associated company so it appears in both timelines. Format the note body as:

• Tech stack summary (4 to 6 most relevant technologies). • Vendor signals broken out by ecommerce platform, payments, analytics, marketing automation, and CRM. • Estimated tech spend if BuiltWith provided it. • Fit rating with the one-line reason. • Detected company size, country, and social links from BuiltWith's meta block. • Source: BuiltWith Domain API, with the lookup timestamp.

Step 6. Use Slack's Send a Message operation to post a punchy alert to the #new-leads channel. Keep it under five lines so a rep can act on it in seconds:

• Line 1: company name, domain, and fit rating emoji. • Line 2: the three or four most relevant detected technologies, comma-separated. • Line 3: one-line fit reason. • Line 4: a routing suggestion (for example 'Route to ecommerce SDR pod', 'Send to enterprise AE', 'Auto-nurture, low fit'). • Line 5: a link to the HubSpot contact record.

Keep the Slack alert short and scannable. No headers, no preamble, no markdown tables. The HubSpot note is where the long-form detail lives, Slack is where the call to action lives.

Edge cases: if BuiltWith returns no technologies (small site, parked domain, or an error), still post the Slack alert with a '❄️ Unknown stack, manual review' note so the lead does not silently fall through the cracks. If the HubSpot contact has no associated company yet, attach the note to the contact only.

What it does

Watches HubSpot for brand new contacts and instantly looks up the company website behind their email.
Pulls the full technology stack and vendor signals for that company from BuiltWith, including ecommerce platform, payments, analytics, marketing tools, and spend estimates.
Writes a clean, structured tech-stack note back into HubSpot, attached to both the contact and the associated company so any rep sees it in the record timeline.
Posts a short alert to your new-leads Slack channel with the company, the three or four most telling technologies, a fit rating, and a routing suggestion.

What you’ll need

A HubSpot account where you can turn on outgoing webhooks for new contacts and let the workflow write notes.
A BuiltWith API key (a paid plan unlocks the deep technology and spend data this workflow uses).
A Slack workspace with a channel ready to receive alerts, for example a #new-leads channel.
A short description of your ideal customer profile so the agent can judge fit (for example, 'growth-stage ecommerce brands on Shopify Plus').

How to customize it

Edit the ideal customer profile description so the fit rating reflects your current go-to-market focus, whether that is ecommerce, B2B SaaS, fintech, or something else.
Change which Slack channel receives alerts, swap the fit-rating emoji set, or tweak the Slack message format to fit how your team likes to scan leads.
Adjust the skip list for personal email domains, or have the workflow create a HubSpot task or kick off a sequence instead of (or in addition to) the Slack alert.

Use cases

Lead Enrichment
Notifications & Alerts

Auto-enrich new HubSpot leads with their tech stack

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts