---
title: "Signal to sequenced contact: Sales Navigator, Clay, Reverse Contact, HubSpot and Smartlead"
description: "A Sales Navigator search turned into an enriched, deduplicated, CRM-checked list in a live campaign. Five tools, the suppression rules, and what it costs."
url: https://www.reversecontact.com/integrations-hub/workflows/outbound-list-build
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)

# Signal to sequenced contact

A search becomes an enriched, deduplicated, CRM-checked list in a live campaign, without a spreadsheet in the middle.

Built by **Reverse Contact** · Verified 2026-09-18 · 5 tools, days to build

The outbound list build is the most-automated workflow in B2B and still, in most companies, the one with a CSV in the middle of it. Somebody exports a search, somebody else enriches it, a third person checks it against the CRM by eye, and a week later a version of that file becomes a campaign. Every step is automatable and the one that matters most is the one people skip.

That step is the CRM check. Sequencing a live customer, an open opportunity or someone another rep contacted last month is the failure this workflow exists to prevent, and it is the only failure here that costs you something you cannot get back. The enrichment is what makes the list worth sending to. The CRM check is what stops it embarrassing you.

Before you build any of this

Read what your Sales Navigator contract permits. LinkedIn's terms constrain what may be extracted from search results and how, and the constraint is contractual rather than technical, which means it does not announce itself when you cross it. This page describes the shape of the pipeline; what your agreement allows at each step is yours to answer first.

## The pipeline, step by step

5 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 saved search defines the segment

Sales Navigator filters are the most precise targeting most teams have access to. Save the search rather than exporting it, so the definition lives somewhere reviewable instead of in a filename.

the segmentdefined once

↓

02

### Rows land in a Clay table

The table is the workbench for everything that follows: enrichment, the CRM check, the conditional branches and the push to the sender. Nothing leaves it as a file.

1 tableno CSV

↓

03

### Reverse Contact resolves each row

Profile URL or email in, a structured record out: current role, company, headcount, location, confidence. This is what turns a list of names into a list you can write a first line for.

1 callper row

↓

04

### The CRM check, which is the whole point

A Lookup against every row. Already a customer, already an open deal, already contacted in 90 days, already owned by another rep: each one is a suppression rule, cheap to write and expensive to omit.

read-onlynothing written yet

↓

05

### Survivors go to the CRM and to the sender

Create the contact so the CRM knows this person is in a sequence, then push to the campaign. Smartlead's webhooks fire on every reply and bounce, so the timeline stays honest without a second sync.

2 writesCRM, then campaign

## The five suppression rules worth writing first

Each one is a single conditional in the table. Together they are the difference between a list and a liability.

- **Already a customer** — The most damaging and the easiest to catch. A lifecycle-stage check costs one lookup and prevents the email that gets forwarded to your account manager with a question mark.
- **Open opportunity** — Cold-sequencing someone mid-deal undercuts the rep working it and confuses the buyer about who they are dealing with. Suppress on any open deal at the company, not just on the contact.
- **Contacted in the last 90 days** — By anyone, through any channel. This is the rule that requires your activity data to be complete, which is why email and calendar sync is the integration everyone should set up first.
- **Owned by another rep** — Territory disputes are expensive in a way that does not appear on any dashboard. If the record has an owner, it routes to them rather than into a campaign.
- **Unsubscribed, bounced or complained** — Non-negotiable, and the one place where getting it wrong has consequences beyond the pipeline. Check it at the list level, not only inside the sending tool.

Each one of those is a single conditional, and the reason to write them before the first send rather than after it is that every one of them is cheaper to add now than to apologise for later.

## 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 5 sets of vendor docs first.

Drop it into Claude Code

mkdir -p .claude/skills/outbound-list-suppression curl -o .claude/skills/outbound-list-suppression/SKILL.md https://www.reversecontact.com/integrations-hub/skills/outbound-list-build.md

For Codex, Cursor, or anything else that reads a file or fetches a URL, hand it `https://www.reversecontact.com/integrations-hub/skills/outbound-list-build.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.

9 of the joins in this chain have a full guide behind them, [Clay and LinkedIn](https://www.reversecontact.com/integrations-hub/clay-integrations/clay-linkedin-integration) and [LinkedIn and Reverse Contact](https://www.reversecontact.com/integrations-hub/linkedin-integrations/linkedin-reverse-contact-integration) among them. The chain crosses 5 of the seven layers a stack splits into, from the [prospecting layer](https://www.reversecontact.com/integrations-hub/stack/prospecting) 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.

- **Sales Navigator's terms are the real constraint** — Not the tooling. What your contract permits regarding extraction from search results is a question to answer before the build rather than after, and it is not one a directory can answer for you.
- **Every enrichment column multiplies the bill** — Clay bills per action on the attempt. Four enrichment columns across a 5,000-row list is 20,000 actions before anything resolves. Order them cheapest-first with conditional runs, so the expensive source only sees the residue.
- **The CRM check needs complete activity data** — "Contacted in the last 90 days" is only true if every channel logs to the CRM. If your reps' InMails live in Sales Navigator and never reach the CRM, this rule is quietly lying to you, which is an argument for CRM Sync or against the rule.
- **Creating CRM records from a prospecting list is a decision** — Push every sequenced contact into the CRM and the database fills with people who never replied. Push none and your suppression rules have nothing to read next quarter. Most teams create the record and mark it clearly, which is the right trade as long as the marking is consistent.
- **Smartlead's entry price comes off a slider** — The $39 figure is the bottom of it. Confirm the tier against your own mailbox count and send volume rather than budgeting from the headline.

All five 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 | Billing | What drives it |
| --- | --- | --- |
| Sales Navigator | `Per seat` | Core, Advanced or Advanced Plus. This workflow needs a seat, not the Advanced Plus CRM Sync edition. |
| Clay | `Per action` | Rows multiplied by columns, charged on the attempt. The lever is conditional runs. |
| Reverse Contact | `Per credit` | One call per row that reaches the enrichment step, 2 credits for a reverse lookup. Nothing for a freshness check first. |
| HubSpot | Any tier | Lookups and writes go through Clay, so no Data Hub requirement. |
| Smartlead | `From $39/mo` | Off a plan slider. Confirm the tier for your mailbox count. |

The cheapest change you can make to this bill is the order of the columns. Suppression before enrichment means you never pay to enrich a row you were going to drop, and on a list with an established CRM behind it that is routinely a third of the rows.

## [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** — 27 vendor documents
- **Paid placement** — None

### Read from

- [Clay: LinkedIn Ads in Clay](https://university.clay.com/docs/linkedin-ads-in-clay)
- [Clay: sources](https://university.clay.com/docs/sources)
- [Clay pricing](https://www.clay.com/pricing)
- [LinkedIn: User Agreement, section 8.2](https://www.linkedin.com/legal/user-agreement)
- [LinkedIn Help: prohibited software and extensions](https://www.linkedin.com/help/linkedin/answer/a1341387)
- [LinkedIn: API rate limits](https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits)
- [LinkedIn: getting API access](https://learn.microsoft.com/en-us/linkedin/shared/authentication/getting-access)
- [LinkedIn Help: Sales Navigator CRM Sync editions](https://www.linkedin.com/help/sales-navigator/answer/a8037044)
- [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 pricing](https://www.reversecontact.com/pricing)
- [HubSpot knowledge base: connect HubSpot and LinkedIn CRM Sync](https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync)
- [Clay integrations: ReverseContact](https://www.clay.com/integrations/data-provider/reversecontact)
- [Clay docs: Reverse Contact integration](https://university.clay.com/docs/reverse-contact-integration)
- [Clay docs: HubSpot integration overview](https://university.clay.com/docs/hubspot-integration-overview)
- [Clay: how to enrich HubSpot records](https://www.clay.com/guides/how-to-enrich-hubspot-records)
- [HubSpot knowledge base: create custom objects](https://knowledge.hubspot.com/object-settings/create-custom-objects)
- [Clay docs: Smartlead integration](https://university.clay.com/docs/smartlead-integration-overview)
- [Clay integrations: Smartlead.ai](https://www.clay.com/integrations/data-provider/smartlead-ai)
- [Smartlead API: webhook integration guide](https://api.smartlead.ai/guides/webhook-integration)
- [Reverse Contact: MCP delivery method](https://www.reversecontact.com/delivery-method/mcp)
- [HubSpot developers: custom code workflow actions](https://developers.hubspot.com/docs/api-reference/legacy/automation/workflow-actions/custom-code-actions)
- [Smartlead API: rate limits](https://api.smartlead.ai/guides/rate-limits)
- [Smartlead API: authentication and base URL](https://api.smartlead.ai/authentication)
- [Smartlead help centre: how to sync leads with HubSpot](https://helpcenter.smartlead.ai/en/articles/225-how-to-sync-leads-with-hubspot)
- [Smartlead help centre: Smartlead and HubSpot integration guide](https://helpcenter.smartlead.ai/en/articles/445-smartlead-x-hubspot-integration-guide-smartagents)

## Questions

### Why suppress before enriching rather than after?

Because every row you drop after enriching is a credit and an action spent on somebody you were never going to contact, and on a list built against an established CRM that is often a third of the file. The only reason to enrich first is if a suppression rule depends on an enriched field such as company domain, and in that case enrich only the field the rule needs.

### Can I skip Clay and do this in n8n?

Yes, and it will be cheaper per row. What you lose is the ability to look at 5,000 rows and see which ones resolved, which is how you find out a segment does not enrich well before you send to it. For a repeated, stable list build n8n is the better home. For an exploratory one, the table is doing real work.

### Do I need a CRM in this at all?

For the suppression rules, yes, and they are the part that justifies the build. Without a CRM to check against, this is a list build with enrichment on it, which is useful but is not what makes the difference. The same shape works on Salesforce, with the org's validation rules to think about.

### What match rate should I expect?

Nobody can tell you, including us. Reverse Contact publishes 70%+ identity match as a global figure and that is not a promise about your segment. Run 500 rows from the actual search you intend to use, count what resolved, and build the economics from that number. It takes an afternoon and it is the only reliable input.

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
