VIP lead alert

Notifies your team the moment a high-value lead makes contact, so a golden opportunity never sits unread in an inbox. It runs on every inbound email, which means the expensive judgement — is this actually worth interrupting someone for? — is made by the workflow, not by a person triaging their inbox.

How it works: 1. A new email arriving in the connected Gmail inbox wakes the run. 2. Claude reads the email and pulls out who wrote it and which company they work for, reading the signature block and the sending domain. Free mailbox domains (gmail.com, outlook.com) are ignored as employers. Newsletters, receipts, calendar invites and vendor pitches come back as UNKNOWN and the run stops there — no research is bought for them. 3. Perplexity searches the web for that company: what it does, headcount, revenue or funding, notable customers, and anything in the last year that changes its ability to buy. 4. Claude scores the lead from 1 to 10 against who you sell to, weighing what the email actually asks for as heavily as the company's size — a large company sending a vague hello is not a VIP lead, and a small company with a funded, named project can be. It returns the score and the one fact that decided it. 5. A router sends each score down one of three paths: 7 or above is a VIP, 4 to 6 is worth logging, below that is not a lead. 6. A VIP lead becomes a Slack DM naming the company, the score, the reason, an excerpt of the research and a link straight to the Gmail thread.

To make it your own: - Set `slackUserId` to whoever should get the alerts. The workflow stops with an instruction until you do — pick the person in the 'Send a direct message' step to find their Slack user ID. - Rewrite `whatWeSell` in your own words. This is the single biggest lever on scoring quality: the more concretely it names your customers' size, budget and the problem you solve, the better the scores. - Move `vipThreshold` (7) and `watchThreshold` (4) to tune how much noise you accept. Lower the VIP bar to catch more, raise it if the DMs get chatty. - The middle branch of the router only prints a note. Add a CRM step there — create a HubSpot contact, append a row to a sheet, open a task — to keep leads that are worth logging but not worth interrupting for. - To narrow what wakes the run, set a sender filter on the Gmail trigger so only mail from, say, your contact-form address is scored.

The two AI steps are deliberately asked for one strict line each and parsed rather than read: the company step returns `company | person | domain`, and the scoring step returns `score | reason` with the number first. An unreadable reply scores 0 and falls to the bottom branch, so a bad model response can never fire a false VIP alert.