For Clay users
Clay hammers LinkedIn for reads — profile lookups, company pages, Sales Navigator searches feeding your waterfall. That is a scraping signature, not a connection-request one. Get aged, high-trust accounts that absorb lookup volume without tripping rate-limit flags.
Trusted by lead-gen agencies · 0.01% ban rate · 24h replacement SLA
Most outbound tools get an account banned for sending too many connection requests. Clay is different: it drives the LinkedIn account through profile views, company-page pulls, and Sales Navigator searches to feed waterfall enrichment. That is high-frequency reading — and LinkedIn detects aggressive reading with its own rate-limit and scraping heuristics. The account that survives Clay is engineered for that signature.
Clay enrichment generates bursts of profile and company lookups in tight windows. We supply accounts whose age, network depth, and activity history make that read volume look like a busy recruiter or sales rep — not a bot scraping a list.
Clay power users run search-based enrichment off Sales Navigator URLs and saved searches. We attach a real Sales Navigator seat to the rental so Clay can pull richer, search-filtered data instead of being capped to basic profile fields.
Each account ships with one dedicated, static ISP-residential proxy. LinkedIn ties trust to IP consistency; a Clay job that surfaces from a new IP every run reads as account takeover. One account, one IP, every lookup.
We hand you concrete daily ceilings for profile views and Sales Navigator searches, so you can throttle Clay tables and Claygent runs below detection thresholds instead of guessing and getting throttled.
The difference between an account that survives a month of waterfall runs and one that gets rate-limited on day two.
Aged trust means LinkedIn tolerates the lookup spikes Clay produces during a big enrichment run.
A Sales Navigator seat unlocks the fields and search filters that make Clay waterfalls actually fill in.
Static proxy means a multi-hour enrichment job runs from one IP start to finish, the way LinkedIn expects.
A stable, unrestricted account means Clay returns data instead of blank cells from a throttled session.
Documented caps let you tune Clay run cadence so you stay productive without tripping a scraping flag.
If LinkedIn challenges the account mid-enrichment, NFC recovery and 24h replacement keep your pipeline moving.
The setup differs from a pure-sending tool because the bottleneck is reads, not connection requests.
We select accounts with the age, connection depth, and natural activity history that let LinkedIn read heavy lookup volume as legitimate professional usage.
For search-based waterfall enrichment, we attach a working Sales Navigator seat so Clay can pull from saved searches and filtered lists, not just public profile fields.
One matched, geographically consistent IP per account so Clay enrichment jobs and Claygent runs always egress from the same trusted location.
You receive concrete numbers for profile views and Sales Navigator searches per day, with guidance on spacing Clay runs to stay under LinkedIn rate-limit heuristics.
Credentials and session state are delivered in a format that plugs into Clay’s LinkedIn integration and downstream tools like HeyReach or HubSpot without re-authentication loops.
Every account is NFC-verified for fast checkpoint recovery, and if it is rate-limited or restricted during enrichment we replace it within 24 hours, matched on age and geography.
Aggregate behaviour of accounts running Clay enrichment workloads.
Composite patterns from GTM and RevOps teams running Clay enrichment.
“Our old account got rate-limited on the second big waterfall run — LinkedIn clearly clocked the lookup volume. The aged account from 500accs has run nightly enrichment for two months without a single challenge.”
“Attaching Sales Navigator was the unlock. Our Clay waterfalls went from half-empty rows to actually filling in titles, company size, and recent role changes because the searches had real data behind them.”
“The static IP mattered more than I expected. Our previous setup rotated proxies and LinkedIn kept throwing checkpoints mid-job. One fixed IP per account and the enrichment runs just finish.”
Composite use cases drawn from agency and in-house customers. Names and identifying details omitted to protect customer confidentiality.
Clay primarily reads LinkedIn — profile lookups, company pages, Sales Navigator searches — to feed waterfall enrichment. That triggers rate-limit and scraping heuristics, which are a separate detection layer from the connection-request bans that hit pure outreach tools. The account you need is tuned for read volume, not send volume.
Not for basic profile and company fields, but search-based enrichment is far richer with it. Clay can run off Sales Navigator search URLs and saved searches to pull filtered people and company data. We offer an optional Sales Navigator attachment for exactly this.
We give you concrete per-account ceilings for profile views and Sales Navigator searches on delivery, because the safe number depends on account age and warmup. The point is to throttle Clay tables and Claygent below the rate-limit threshold rather than discovering it the hard way.
Yes. Claygent drives the same LinkedIn session as any other Clay step, so a properly configured rented account with a stable session and matched proxy works with Claygent workflows that touch LinkedIn.
LinkedIn ties account trust to IP consistency. Clay enrichment jobs can run for hours; if your IP rotates mid-run, LinkedIn reads it as a session hijack and throws a checkpoint. One dedicated static ISP-residential IP per account keeps every lookup coming from the same trusted location.
Yes. Clay commonly enriches in one step and triggers sending or CRM sync in another. We deliver the account in a format that supports Clay’s LinkedIn integration and downstream handoff, though sending should respect its own separate volume limits.
Rate-limits are usually temporary; we advise pausing Clay and letting the account cool down. If LinkedIn applies a hard restriction, NFC-verified recovery handles checkpoints and we replace the account within 24 hours, matched on age and geography.
Automated data extraction sits outside LinkedIn’s terms, and we are direct about that. We reduce the operational risk — aged trust, static IP, documented caps — but the rental does not make unlimited scraping safe. Throttle your Clay runs accordingly.
It can, but parallel tables hitting the same account multiply the per-minute lookup rate and that is what trips rate-limits. We recommend serializing heavy enrichment or spreading it across multiple isolated accounts rather than parallelizing on one.
An outreach account is optimized to send connection requests and messages under daily send caps. A Clay account is optimized to read at volume: stronger aging to absorb lookup bursts, an optional Sales Navigator seat for search enrichment, and caps expressed as views and searches rather than sends.
Aged high-trust account, optional Sales Navigator, static matched proxy, documented caps, NFC recovery, 24h replacement.