---
name: outbound-list-suppression
description: Build an outbound list pipeline that enriches a prospect list, checks every row against the CRM for customers, open deals, recent contact and existing owners, and pushes only the survivors into a sequencing tool. Use when the user is building cold outbound lists and needs suppression rules, or wants to stop a CSV sitting in the middle of the process.
---

# Signal to sequenced contact

> Generated from https://www.reversecontact.com/integrations-hub/workflows/outbound-list-build
> Every tier requirement and limit below was read from the vendor's own documentation on 2026-09-18.
> Vendors change these without notice. Re-check anything load-bearing before you rely on it.

**Tools in this workflow:** LinkedIn Sales Navigator, Clay, Reverse Contact, HubSpot, Smartlead.
**Build effort:** Days.

## What you are building

A defined segment becomes an enriched, suppressed, CRM-checked list in a live campaign, with no spreadsheet in the middle. The enrichment makes the list worth sending to. The CRM check is what stops it embarrassing the company.

## Ask this before writing anything

Where is the source list coming from, and what does that contract permit? If the answer involves extracting from LinkedIn Sales Navigator search results, **stop and make the user confirm what their agreement allows**. The constraint is contractual rather than technical, so nothing will fail loudly when it is crossed. Do not build scraping into this pipeline on your own initiative.

## Prerequisites

| What | Where to get it | Notes |
|---|---|---|
| A defined source segment | A saved search, an export the user is permitted to make, or an existing list | Save the definition somewhere reviewable, not in a filename |
| Reverse Contact API key | Workspace > API Keys | One call per row that survives suppression |
| CRM read access | A private app with contacts, companies and deals read scope | This is what the suppression rules query |
| Sending tool API key | Smartlead, lemlist or equivalent | Campaign must exist before the push step |

## The tools, and how to call them

### Reverse Contact

- **Base:** `https://api.reversecontact.com/v2`
- **Auth:** `Authorization: Bearer rc_your_api_key`. Keys are created in Workspace > API Keys.

| Call | Request | What it does |
|---|---|---|
| `POST /v2/enrich/persons` | `{ "email": "j.okafor@northwind.io" }` | Resolve a person from an email, a name plus company, or a profile URL. Cached resolution, returns in the response. |
| `POST /v2/enrich/companies` | `{ "domain": "northwind.io" }` | Resolve a company from a domain or a name. |
| `POST /v2/fetch/persons` | `{ "linkedInUrl": "..." }` | Standard profile lookup from the database. |
| `POST /v2/fetch/persons/live` | `{ "linkedInUrl": "..." }` | Live on-demand resolution. ASYNCHRONOUS: returns a webhookId to poll, not a record. |
| `POST /v2/search/people` | `{ "filters": { "currentCompanyDomain": "northwind.io" } }` | Filtered people search. 1 credit a profile delivered, and /v2/search/people/count is free. It replaced /v2/search/persons, which returns 410 Gone since 13 October 2026. |
| `POST /v2/search/organizations` | `{ "filters": { "companyDomain": "northwind.io" } }` | Filtered company search. A domain can also go straight to a company through POST /v2/enrich/companies, or through the enrich_company MCP tool since November 2026. |
| `POST /v2/contact/email` | `{ "linkedInUrl": "..." }` | Find an email. ASYNCHRONOUS: returns a taskId to poll. 3 credits for a professional address, 5 for a personal one, 8 for both, refunded when neither is found. |
| `GET /v2/webhooks/:webhookId` | - | Poll an async job until status is "succeeded". Polling is free and does not count against the rate limit. |

Response shape:

```json
{
  "success": true,
  "data": {
    "person": {
      "fullName": "Jane Okafor",
      "headline": "VP Sales at Northwind",
      "location": "London, United Kingdom",
      "linkedInUrl": "https://linkedin.com/in/...",
      "currentPosition": { "title": "VP Sales", "companyName": "Northwind", "startDate": "2023-04" },
      "emails": [], "experience": [], "education": [], "skills": []
    },
    "company": { "name": "Northwind", "domain": "northwind.io",
                 "industry": "Software Development", "employeeCount": 220 }
  },
  "error": null,
  "metadata": { "requestId": "req_...", "executionTimeMs": 480, "updatedAt": "2026-09-01T..." },
  "quotas": { "creditsConsumed": 1, "workspace": { "credits": { "total": 10000, "used": 4521, "left": 5479 } } }
}
```

**Rules that will cost you time if you skip them:**

- A miss returns **null**, not a best guess. Every response carries a confidence score, and you can raise the precision threshold on the request. Branch on it: do not treat a low-confidence answer as a match.
- Use the cached endpoints anywhere that must answer inside one HTTP request. The `/live` endpoints return a task and need polling.
- `quotas.workspace.credits.left` is on every response. Log it, or you will find out about the balance from a 402.
- Credit costs per call are published and a dollar rate per lookup is not: 2 credits for a reverse lookup from an email, 1 for a cached profile lookup, 2 for a live refresh, 3 for a business email and 20 for a direct phone number, with the last two charged only when one is found. Checks and the search count endpoint are free. Credit packs expire after 3 months. Do not hard-code a dollar cost assumption.

**MCP server:** `https://api.reversecontact.com/mcp`

- Auth: OAuth 2.1 where the client supports it, otherwise `Authorization: Bearer rc_your_api_key`.
- Tools: `enrich_person`, `enrich_person_live`, `enrich_company`, `enrich_company_live`, `search_persons`, `search_companies`, `check_usage`, `check_task`
- Streamable HTTP, JSON-RPC 2.0. The `_live` tools return a task id that `check_task` polls.

Docs: https://docs.reversecontact.com/getting-started

### Clay

- **Base:** `Configured in the table, not through an API`
- **Auth:** Per-integration, set in the workbook.

| Call | Request | What it does |
|---|---|---|
| `ACTION HubSpot / Salesforce Lookup` | - | Read-only. Pulls records into the table and changes nothing in the CRM. |
| `COLUMN HTTP API` | `POST https://api.reversecontact.com/v2/enrich/persons\nHeaders: { "Authorization": "Bearer rc_...", "Content-Type": "application/json" }\nBody: { "email": "/Work Email" }` | `/Work Email` is a column reference, so each row posts its own value. This is how a provider with no native listing becomes a column. |
| `ACTION HubSpot / Salesforce Update` | - | Writes back. Immediately live to every CRM user. Turn on "ignore blank values" and exclude rep-owned properties. |

**Rules that will cost you time if you skip them:**

- **Clay bills per action on the attempt, not the result.** Effective cost per filled field is the action rate divided by your match rate. Order a waterfall cheapest-first and use conditional runs so the expensive source only sees the residue.
- Import a filtered slice, never the whole portal. Filter on the gap you are filling.
- Run read-only until the columns look right, write to ten rows, open them in the CRM, and only then schedule.

Docs: https://university.clay.com/docs/hubspot-integration-overview

### HubSpot

- **Base:** `https://api.hubapi.com`
- **Auth:** `Authorization: Bearer <private-app-token>` for a private app, or OAuth for a marketplace app. Full CRM API access is on every tier including Free.

| Call | Request | What it does |
|---|---|---|
| `PATCH /crm/v3/objects/contacts/{contactId}` | `{ "properties": { "rc_title": "VP Sales" } }` | Update a contact. Send only the properties you own. |
| `POST /crm/v3/objects/contacts/search` | `{ "filterGroups": [...], "properties": [...] }` | Find records by property. Use this to pull the slice that is missing a field. |
| `POST /crm/v3/objects/contacts/batch/update` | `{ "inputs": [ { "id": "...", "properties": {...} } ] }` | Batch of up to 100. Prefer this over per-record PATCH at volume: it is one request against the rate limit. |

**Rules that will cost you time if you skip them:**

- **Rate limits.** A private app gets 190 requests per 10 seconds on Professional and Enterprise, 100 on Free and Starter. Daily caps are 250,000 / 625,000 / 1,000,000 calls **per account, shared across every app**. A public OAuth marketplace app is capped at 110 per 10 seconds per installing account.
- **Calling an external API from a workflow needs Data Hub Professional or Enterprise.** Both the webhook action and the custom code action live in that hub, not in Sales Hub. Check this before designing an in-HubSpot build.
- **Custom code actions get 20 seconds and 128 MB.** Combined length of all workflow secrets is capped at 1,000 characters. Secrets are read with `process.env.NAME`.
- **Workflows:** up to 50 simple on Starter, up to 300 fully customisable on Professional.
- **Never write to a property a human maintains.** Use prefixed properties (`rc_*`) and promote with a separate workflow only where the human field is empty.

**HubSpot custom code action (Node 20):**

```javascript
// Input field: email   Output fields: rc_status, rc_title, rc_company, rc_headcount
// Secret: RC_API_KEY
const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  const res = await axios.post(
    'https://api.reversecontact.com/v2/enrich/persons',
    { email },
    { headers: { Authorization: `Bearer ${process.env.RC_API_KEY}` } }
  );

  const person = res.data?.data?.person;
  const company = res.data?.data?.company;

  // null means "not found", not "try harder". Write nothing and flag it.
  if (!person) return callback({ outputFields: { rc_status: 'no_match' } });

  callback({ outputFields: {
    rc_status:    'matched',
    rc_title:     person.currentPosition?.title || '',
    rc_company:   company?.name || '',
    rc_headcount: company?.employeeCount || 0
  }});
};
```

Docs: https://developers.hubspot.com/docs/api/overview

### Smartlead

- **Base:** `https://server.smartlead.ai/api/v1`
- **Auth:** API key as a query parameter.

| Call | Request | What it does |
|---|---|---|
| `POST /campaigns/{id}/leads` | `{ "lead_list": [ { "email": "...", "custom_fields": {...} } ] }` | Push the survivors of your suppression rules into a campaign. |

**Rules that will cost you time if you skip them:**

- Webhooks fire on every send, reply, bounce and unsubscribe. Route replies to a human within minutes; send the rest to a report.
- Entry pricing comes off a plan slider. Confirm the tier against your own mailbox count rather than budgeting from the headline.

Docs: https://api.smartlead.ai/reference

### LinkedIn Sales Navigator

- **Base:** `No public API for this workflow`
- **Auth:** CRM Sync is installed as an app, not called as an API.

**Rules that will cost you time if you skip them:**

- **CRM Sync requires Sales Navigator Advanced Plus**, not Advanced. The embedded profile card runs on Advanced and syncs nothing.
- **It does not backfill.** Only new and updated data syncs after switch-on; history needs an uninstall and reinstall.
- **Field mappings cannot be customised.** Every supported field syncs or none do.
- **Read your contract before extracting anything from search results.** The constraint is contractual rather than technical, so it does not announce itself when you cross it. An agent must not automate scraping here.

Docs: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync

## Build it

### 1. Suppress before you enrich

This ordering is the single biggest cost lever in the whole pipeline. 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 routinely a third of the file. Enrich first only if a suppression rule needs an enriched field, and then enrich only that field.

### 2. Write the five suppression rules

Already a customer (lifecycle stage). Open opportunity at the company, not just on the contact. Contacted by anyone through any channel in 90 days. Owned by another rep. Unsubscribed, bounced or complained. Each is one conditional; together they are the difference between a list and a liability.

### 3. Enrich the survivors

Resolve each remaining row to current role, company, headcount and location, with a confidence score. This is what lets a first line reference something true rather than something inferred.

### 4. Drop low-confidence rows rather than personalising around them

A guessed job title in a first line is worse than a generic one. Branch on the confidence score and send anything under your threshold to a review queue.

### 5. Create the CRM record, marked

So next quarter's suppression rules have something to read. Mark it clearly and consistently as prospecting-sourced, or your database fills with people who never replied and your reporting stops meaning anything.

### 6. Push to the campaign, and wire the webhooks back

Replies and bounces should reach the CRM timeline within seconds, not at the next sync. That is what keeps the "contacted in 90 days" rule honest for the next run.

## Gotchas

- "Contacted in the last 90 days" is only true if every channel logs to the CRM. If rep InMails live in Sales Navigator and never reach the CRM, this rule is quietly lying to you.
- Four enrichment columns across a 5,000-row list is 20,000 Clay actions before anything resolves. Order cheapest-first with conditional runs.
- Suppress on any open deal at the **company**, not just on the contact. Cold-sequencing someone at an account mid-deal undercuts the rep working it.
- Smartlead entry pricing comes off a slider; confirm the tier against mailbox count rather than the headline figure.

## What breaks, from the vendors' own docs

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

## How to verify it works

- Run the suppression rules against a list you already sent to, and confirm they catch the people you know should have been excluded.
- Check the drop rate. On a list built against an established CRM, a third is normal. If almost nothing is suppressed, a rule is not reading the field you think it is.
- Pull ten enriched rows and check the titles by hand against a source you trust.
- Send to a five-row test campaign first and confirm replies reach the CRM timeline.
- Count what share resolved. Build the economics from that number, not from any published match rate.

## What this costs to run

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

## Sources

- Reverse Contact: https://docs.reversecontact.com/getting-started
- Clay: https://university.clay.com/docs/hubspot-integration-overview
- HubSpot: https://developers.hubspot.com/docs/api/overview
- Smartlead: https://api.smartlead.ai/reference
- LinkedIn Sales Navigator: https://knowledge.hubspot.com/integrations/connect-hubspot-and-linkedin-crm-sync
- This workflow, with the reasoning behind each step: https://www.reversecontact.com/integrations-hub/workflows/outbound-list-build

---

*Published by Reverse Contact, which appears in this directory as a data provider.
No other vendor pays for placement. Where a vendor publishes no public figure, this file says so
rather than estimating. Reverse Contact costs are stated in credits, which it publishes; no dollar
rate per lookup appears here, because none is published and dividing a pack price is not their number.*
