A form submission enriched, scored, routed and announced before the visitor has closed the tab.
This is the smallest workflow on the site and the one that changes a number fastest. A prospect fills in a form. Within a minute the record carries a title, a seniority, a company size and a score, an owner has been assigned from those fields rather than from a dropdown the visitor guessed at, and the right person has a Slack message naming them and telling them what to do.
Nothing here is clever. The reason it is worth building first is that the alternative is a lead sitting in a queue until somebody opens the CRM. What people argue about is which route to take, and that comes down to one question about your HubSpot subscription.
Calling an external API from inside a HubSpot workflow needs the webhook action or the custom code action, and both live in Data Hub Professional rather than Sales Hub. If you own Data Hub, build route A and skip the middle layer entirely. If you do not, route B through n8n is not a compromise, it is cheaper than the hub upgrade by a wide margin.
6 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.
HubSpot forms on any tier, including free. This is the trigger, and the only part that has to be HubSpot.
A single POST to the enrich endpoint. Use the cached endpoint here, not the live one: live resolution returns a task to poll, and neither a CRM workflow nor a speed-to-lead path should wait for it.
Title, current company, headcount, location, profile URL and a confidence score. A miss returns null rather than a guess, which is what lets the next step branch honestly instead of scoring a fabricated title.
Every value lands in its own property. A second workflow promotes a value to the field people trust only where that field is empty. This is the step teams skip and the reason pipelines get switched off in month three.
Owner assignment from headcount and title rather than from what the visitor typed into a company-size dropdown. This is the actual payoff: routing that does not depend on prospect honesty.
One channel, one trigger, the owner mentioned by name, the enriched context in the message and a link to the record. Not every submission: only the ones above the score threshold.
Identical output. Different owner, different bill, different failure modes.
Needs Data Hub Professional or Enterprise.
A contact-based workflow triggers on form submission. A custom code action calls Reverse Contact, reads the API key from a workflow secret and returns the fields as output fields. Subsequent actions write the properties, set the score, assign the owner and send the Slack message: one object in HubSpot, no third vendor, nothing to host. The constraints are HubSpot's: 20 seconds and 128 MB per custom code run, which a cached enrichment call fits inside comfortably.
The normal case. No hub upgrade.
n8n's HubSpot Trigger subscribes to HubSpot's webhooks API, calls Reverse Contact with an HTTP Request node, updates the contact with the native HubSpot node and posts to Slack. Self-hosted, so records never leave infrastructure you control. One thing to know first: the HubSpot Trigger authenticates with a developer API key from a HubSpot developer account rather than a private app token, because that is how HubSpot exposes the webhooks API, and it is free to create and nobody expects it. HubSpot also allows one webhook URL per app, so route several object types through one subscription and branch inside n8n.
Clay, for this particular workflow.
Clay is the right answer for the scheduled version of this and the wrong one for the real-time version. Tables run on a schedule or on demand, not on a form submission inside a minute. Use Clay for the backfill and the weekly refresh, which is the CRM data layer workflow, and keep it out of the speed-to-lead path.
This workflow ships as a skill file: the API surface of every tool in the chain, the build order, the limits that break it, and how to check it worked. Point an agent at it and it has what it needs without reading 3 sets of vendor docs first.
--- name: hubspot-speed-to-lead description: Build an inbound speed-to-lead pipeline: a HubSpot form submission enriche d by Reverse Contact, scored and routed on the enriched fields, and announce... --- # Inbound speed to lead ## What you are building ## Prerequisites ## The tools, and how to call them → Reverse Contact, HubSpot, Slack, n8n ## Build it → 6 steps ## Gotchas ## What breaks, from the vendors' own docs ## How to verify it works → 5 checks
mkdir -p .claude/skills/hubspot-speed-to-lead curl -o .claude/skills/hubspot-speed-to-lead/SKILL.md https://www.reversecontact.com/integrations-hub/skills/inbound-speed-to-lead.md
For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it https://www.reversecontact.com/integrations-hub/skills/inbound-speed-to-lead.md directly. It is plain markdown with YAML frontmatter and no tool-specific syntax, so nothing in it depends on which agent is reading it.
3 of the joins in this chain have a full guide behind them, HubSpot and Reverse Contact and HubSpot and Slack among them. The chain crosses 3 of the seven layers a stack splits into, from the CRM layer outward, which is why no single vendor owns it.
Documented by one of the vendors in the chain, and easier to design around than to discover.
All four are documented by a vendor rather than observed by us, which is the useful part: a limit you can read is a limit you can design around before it costs you a week.
What each component bills on, and which line actually scales with your volume.
| Component | Route A | Route B | Notes |
|---|---|---|---|
| HubSpot | Data Hub Pro | Any tier | Route A needs the webhook or custom code action, which is Data Hub. Route B only needs a developer app, which is free. |
| Orchestration | None needed | n8n, free self-hosted | Route A has no middle layer. Route B adds an instance you host and own. |
| Reverse Contact | Credits | Credits | 2 credits a reverse lookup from an email, published. Packs from $100, valid 3 months, or an Unlimited plan from $249 a month. |
| Slack | Free plan works | Free plan works | One channel and one message type does not need a paid workspace. |
The credit cost is published and the dollar cost is not, so this table stops where their pricing page does. A reverse lookup from an email is 2 credits and a freshness check is free. What a credit costs depends on the pack or the plan it came from, and a modelled figure here would be a guess wearing a decimal point. Worth sizing against monthly form volume rather than database size, because the first is a much smaller number: above roughly 15,000 lookups a month their own page points you at an Unlimited plan, where the cached endpoints stop being metered.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, with a confidence score your logic can branch on. The free trial takes no card and runs until the 500 credits a new account starts with are spent, which is enough to run this end to end before anyone signs anything.
Free trial, no card required, and 500 credits to start.
For speed, no. For routing, yes. You can alert on every form submission in ten minutes with nothing but a CRM and Slack, and at low volume that is a good answer. Enrichment is what lets you alert on the right ones. Without it the score is built from fields the visitor typed, and the classic failure is a director at a 2,000-person company selecting "1-10 employees" because the form asked and they were guessing.
Whatever you decide. The API returns null with a confidence score rather than inventing a title, so the branch is yours to write. The usual pattern is to route unresolved leads to a general queue with a lower-priority alert rather than letting them score zero and disappear. If your mix of personal email addresses is high, filter those out before the call instead of paying for a lookup that was never going to resolve.
Yes, with Zapier or Make instead of n8n, which trades self-hosting for a task meter and a faster start. At a few hundred submissions a month that is the right trade and it runs in an hour. It stops being right when volume climbs, because you are then paying per task for something n8n does for the cost of a small instance.
Because it is asynchronous. The live endpoints return a task id and you poll until it is ready, which is correct for freshness and wrong for a path that must finish inside a minute. Use the cached endpoint here, and run live resolution as a second pass in n8n where a polling loop is natural.
Count two things weekly: what share of submissions resolved, and how long the owner took to respond after the Slack message. The first tells you whether the data layer is earning its keep on your traffic. The second is the number you built this for, and it is the one that quietly regresses when the channel gets noisy.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.