---
title: "Inbound speed to lead: HubSpot, Reverse Contact and Slack"
description: "A form submission enriched, scored, routed and announced in Slack in under a minute. Three tools, two routes by HubSpot hub, and the limits on each."
url: https://www.reversecontact.com/integrations-hub/workflows/inbound-speed-to-lead
format: markdown twin of the page above, generated at build time
---

New Unlimited plans are here. Fetch, search and enrich without counting credits. [See plans →](https://www.reversecontact.com/integrations-hub//pricing#plans)

Reverse Contact

### Products

Data

People Data

Company Data

Our Data Quality Standard

Delivery methods

API

Webhooks

CSV Enrichment

MCP

CLI

Integrations

### Use cases

[Sales Product](https://www.reversecontact.com/integrations-hub//use-case/sales-products)[Recruiting Product](https://www.reversecontact.com/integrations-hub//use-case/recruiting-products)[Internal Data Teams](https://www.reversecontact.com/integrations-hub//use-case/internal-data-teams)[AI Products](https://www.reversecontact.com/integrations-hub//use-case/data-for-ai)[CRM Enrichment](https://www.reversecontact.com/integrations-hub//use-case/crm-enrichment)

### Features

[Email Finder API](https://www.reversecontact.com/integrations-hub//feature/email-finder-api)[Phone Number Enrichment](https://www.reversecontact.com/integrations-hub//feature/phone-number-enrichment)[People Search API](https://www.reversecontact.com/integrations-hub//feature/people-search-api)[Agentic Search API](https://www.reversecontact.com/integrations-hub//feature/agentic-search-api)[People Lookalike API](https://www.reversecontact.com/integrations-hub//feature/people-lookalike-api)[Company Search API](https://www.reversecontact.com/integrations-hub//feature/company-search-api)[Person Enrichment API](https://www.reversecontact.com/integrations-hub//feature/person-enrichment-api)[Company Enrichment API](https://www.reversecontact.com/integrations-hub//feature/company-enrichment-api)[Person Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-person-api)[Company Social Data API](https://www.reversecontact.com/integrations-hub//feature/social-company-api)

Security

Pricing

Docs

[Log in](https://app.reversecontact.com/auth/login) [Book a demo](https://www.reversecontact.com/contact?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header) [Start for free](https://app.reversecontact.com/auth/signup?utm_source=integrations-directory&utm_medium=referral&utm_campaign=tool-integrations&utm_content=site-header)

# Inbound speed to lead

Featured

A form submission enriched, scored, routed and announced before the visitor has closed the tab.

Built by **Reverse Contact** · Verified 2026-09-18 · 3 tools, hours to build

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.

Read this before you plan the build

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.

## The pipeline, step by step

6 steps. The ones in blue are the data layer; everything else is plumbing you already own or can stand up in an afternoon.

01

### A form submission creates or updates a contact

HubSpot forms on any tier, including free. This is the trigger, and the only part that has to be HubSpot.

0sthe trigger

↓

02

### The email goes to Reverse Contact

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.

~500msP95, published

↓

03

### The record comes back, or it does not

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.

1 callper submission

↓

04

### Write to rc\_ properties, never to the rep fields

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.

5 fieldsrc\_ prefixed

↓

05

### Score and route from the enriched fields

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.

instantCRM workflow

↓

06

### Slack tells the owner, by name

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.

under 60sform to a named human

## Two routes, and one to avoid

Identical output. Different owner, different bill, different failure modes.

### Everything inside HubSpot

**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.

Costs: Data Hub Pro, plus credits Hours

### HubSpot triggers, n8n does the work

**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.

Costs: Free self-hosted, plus credits Hours

### The one to avoid for this job

**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.

Costs: Not suited to per-event latency n/a

## Build it with an agent

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.

Drop it into Claude Code

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](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-reverse-contact-integration) and [HubSpot and Slack](https://www.reversecontact.com/integrations-hub/hubspot-integrations/hubspot-slack-integration) among them. The chain crosses 3 of the seven layers a stack splits into, from the [CRM layer](https://www.reversecontact.com/integrations-hub/stack/crm) outward, which is why no single vendor owns it.

## What will bite

Documented by one of the vendors in the chain, and easier to design around than to discover.

- **The Slack message cannot follow the record** — HubSpot's Slack workflow action sends to a channel chosen at design time. There is no built-in option to send to the channel associated with the record that triggered it. For this workflow that is fine, because one channel with one owner is the correct design anyway. It becomes a problem the moment somebody asks for per-segment routing, and at that point it is an hour of work in n8n rather than a setting.
- **Enrichment on creation writes to your CRM** — This is the whole point and it is also the risk. Anything pointed at a property a human maintains will eventually overwrite something correct with something plausible. The prefix convention and a promote-only-if-empty workflow cost an afternoon and remove the entire class of problem.
- **A miss is a real outcome, so handle it** — Reverse Contact returns null with a confidence score rather than a best guess, which is the behaviour you want and only useful if the next step branches on it. Decide in advance what an unresolved lead does: route to a general queue, flag for review, or fall through to a second provider. Doing nothing means those leads silently score zero.
- **The alert degrades faster than the pipeline** — Enrichment will keep working for years. The Slack channel will get noisy within a month if the threshold is set generously, and a muted channel looks exactly like a working one from the admin screen. Set the threshold high, review it once a quarter, and send everything below it to a digest.

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 it costs to run

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](https://www.reversecontact.com)

We sell B2B people and company data, and we publish this directory. Every tier requirement, limit and sync direction in this chain was read from a vendor's own documentation, through the integration records each step rests on. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. [What has changed since](https://www.reversecontact.com/integrations-hub/changes) · [How we checked](https://www.reversecontact.com/integrations-hub/methodology), and what we will not claim

[Eugene Suslov](https://www.linkedin.com/in/eysuslov/)

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

- **Verified** — 2026-09-18
- **Sources** — 17 vendor documents
- **Paid placement** — None

### Read from

- [Reverse Contact API documentation](https://docs.reversecontact.com/getting-started)
- [Reverse Contact: credits](https://docs.reversecontact.com/guides/credits)
- [Reverse Contact: rate limits](https://docs.reversecontact.com/guides/rate-limits)
- [Reverse Contact: MCP delivery method](https://www.reversecontact.com/delivery-method/mcp)
- [Reverse Contact pricing](https://www.reversecontact.com/pricing)
- [HubSpot developers: custom code workflow actions](https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions)
- [HubSpot knowledge base: manage your notifications in Slack](https://knowledge.hubspot.com/integrations/manage-your-notifications-in-slack)
- [HubSpot community: Slack notification to the channel associated with the deal](https://community.hubspot.com/t5/CRM/Slack-notification-in-Workflows-Send-to-the-channel-associated/m-p/1177859)
- [Slack: web API rate limits](https://docs.slack.dev/apis/web-api/rate-limits/)
- [Slack: rate limit changes for non-Marketplace apps](https://docs.slack.dev/changelog/2025/05/29/rate-limit-changes-for-non-marketplace-apps/)
- [Slack: workflows and custom steps](https://docs.slack.dev/workflows/)
- [Slack: workflow steps](https://docs.slack.dev/workflows/workflow-steps/)
- [Slack: guide to Slack Workflow Builder](https://slack.com/help/articles/360035692513-Guide-to-Slack-Workflow-Builder)
- [Slack: sending messages using incoming webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/)
- [ClickUp: create a task webhook Automation](https://help.clickup.com/hc/en-us/articles/31126817112343-Create-a-task-webhook-Automation)
- [Google Apps Script: quotas for Google Services](https://developers.google.com/apps-script/guides/services/quotas)
- [Gong: what the Gong API provides](https://help.gong.io/docs/what-the-gong-api-provides)

## Questions

### Do I really need enrichment for speed to lead?

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.

### What happens to leads that cannot be resolved?

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.

### Can I build this without n8n and without Data Hub?

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.

### Why not use the live endpoint for the freshest data?

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.

### How do I know it is working?

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.

Ask an assistant
