In short
Source: Sales Surge, Pipedrive Platinum Partner, from Clay builds for B2B outbound teamsAs of: 16 November 2026
In this article
- What is Clay, and when is it too expensive?
- Which fields and integrations does Clay deliver?
- Why connect Clay to Pipedrive
- Clay vs Apollo vs ZoomInfo: when each one wins
- Connecting Clay to Pipedrive step by step
- Enriching trial signups with Clay and Pipedrive
- Is Clay GDPR-proof?
- What does Clay cost per month for an outbound team?
- Where Clay and Pipedrive pay off most
- Clay next to the alternatives
- FAQ
- Setup time
- 4 to 8 hours
- Sync direction
- From Clay to Pipedrive
What is Clay, and when is it too expensive?
Clay is a data platform for prospecting workflows. It gives you access to more than a hundred data providers, such as Apollo, Hunter, Prospeo, Findymail and Cognism. On top of that sit AI models from OpenAI and Anthropic.
Clay does not lock you into one data vendor. You build a waterfall instead: try provider A, fall back to B, then C, until you find the data at the lowest cost.
Outbound teams use Clay because prospecting moves from buying a static list to a process you program. A Clay workflow waits for a trigger, such as a job change, a funding round, a hiring signal or a new tool. It enriches the matching contacts through the waterfall and lets AI write the research and the opening line.
Only the validated records go to Pipedrive. Clay is too expensive when you run one ICP from one source: then you pay for a waterfall you never use. Below roughly 500 new contacts a month with one stable playbook, Apollo is usually enough.
Which fields and integrations does Clay deliver?
Clay delivers contact, company and signal fields from its data providers. It writes them to Pipedrive, HubSpot or Salesforce, to sending tools such as Instantly, or to any webhook. Which source is best depends on the field. This is the table we start from for B2B teams that sell in Europe, checked in November 2026.
| Field | Good first sources in the waterfall | EU coverage | Indicative cost |
|---|---|---|---|
| Work email | Hunter, Apollo, Prospeo, Findymail | Good when you chain 3 or more | about 1 to 3 data credits per email found |
| Mobile or direct dial | Cognism, Lusha, Kaspr | Mixed, best with Cognism | about 5 to 10 data credits per number found |
| Job title and seniority | Clay's own person data, Apollo | Good | about 1 data credit |
| Company size and industry | Clay's own company data, Apollo | Good | about 1 data credit |
| Tech stack | BuiltWith and similar sources | Good for websites, weaker for internal tools | about 1 to 3 data credits |
| Funding and growth | Crunchbase and similar sources | Mixed outside the bigger rounds | about 1 to 3 data credits |
| Hiring and job changes | Job posting and job change sources | Good | about 1 to 3 data credits |
| Research and opening line | An AI column on top of the fields above | Depends on the input | actions, plus model use that grows with length |
For Pipedrive, Clay has a native integration that creates and updates persons, organisations and deals. For anything with conditions, we send a webhook from Clay into Make. The Make guide shows that pattern.
Why connect Clay to Pipedrive
In this setup Clay is the staging layer and Pipedrive is the system of record. Data flows one way: from Clay to Pipedrive.
- Waterfall enrichment. Stack Hunter, Apollo, Prospeo and more into one enrichment chain, so a contact one source misses can still be found by the next.
- AI research at volume. Use an AI column inside Clay to draft a personal opening line from each prospect's profile data, blog or news mentions.
- Trigger-based prospecting. New funding, a job change, a hiring signal or a new tool automatically creates an enriched lead in Pipedrive. No list buying.
Clay vs Apollo vs ZoomInfo: when each one wins
We have built outbound stacks on all three, and each one has a clear job. Picking the wrong one is the mistake we see most in B2B prospecting.
Mistake #1: Using Clay when you only need Apollo.
Consequence: With one ICP, one playbook and one enrichment source, Clay is overkill. You pay for two tools instead of one and spend 4 to 8 hours on setup. Apollo delivers the same workflow in about half an hour.
How to fix it: Targeting one ICP with a stable playbook and fewer than about 500 new contacts a month? Then use Apollo directly into Pipedrive. Add Clay only when you need waterfall logic or AI research at volume.
Mistake #2: Using Apollo when you need Clay.
Consequence: Apollo's database has gaps, especially for European, technical and mid-market accounts. In those segments match rates can drop sharply. Enrichment from a single source quietly starves outbound campaigns.
How to fix it: Does your ICP sit outside Apollo's strong zone, such as the EU, deep tech or a niche? Then build a Clay waterfall with 3 to 5 sources. Measure the match rate per source in the first campaign, so you know which ones earn their place.
Mistake #3: Using ZoomInfo for SMB outbound.
Consequence: ZoomInfo is the standard for enterprise data. But it usually comes as a five-figure annual contract with complex terms. For teams of 5 to 25 SDRs it is overkill and locks you in.
How to fix it: ZoomInfo makes sense at enterprise scale, with a large SDR team and a real data budget. It also fits when you need their intent data. Otherwise Clay or Apollo is more flexible.
Mistake #4: Treating Clay as an enrichment tool only.
Consequence: Many teams use a fraction of what Clay can do. They run basic email finds and ignore the AI research, the trigger sources and the HTTP modules. Then they wonder why they pay for a Growth plan.
How to fix it: Use Clay as a prospecting workflow you program, instead of a database. Combine triggers with AI research and waterfall enrichment in one table per campaign.
Mistake #5: Sending raw Clay output straight to Pipedrive.
Consequence: Clay can return 5 emails for one person, job titles that conflict and company descriptions the model made up. Push that into Pipedrive and your CRM is unusable within two months.
How to fix it: Build a verification layer. Only push records where the email is validated and the job title comes from a trusted source. Tag AI-generated fields as 'AI suggestion, review before send'.
What Sander says about it
"The Clay teams that do well treat Pipedrive as the production database and Clay as the staging area. Nothing leaves Clay until it is verified, normalised and tagged. The teams that struggle use Clay as an expensive Apollo and pay more for the same outcome. Clay rewards workflow design and punishes shortcuts."
Connecting Clay to Pipedrive step by step
Plan 4 to 8 hours, longer than Apollo because of the waterfall logic. Before you start, you need these five things.
What you need
- A paid Clay workspace. Check which plan includes the integrations and the volume of credits you need
- Admin rights in Pipedrive and an API token
- Optional: your own API keys for providers you already pay for, like Apollo or Cognism
- Optional but useful: Make.com for sync logic and error handling
- One document that defines your ICP and fields, plus the rules for a verified record
Define the workflow scope
Pick one campaign, one ICP and one trigger. Do not build a generic enrichment setup on day one. Example: Series A SaaS companies in NL and DE that hired a Head of Sales in the last 60 days.
Create custom fields in Pipedrive
Add 'Clay source' as text, 'Enrichment confidence' as a dropdown with High, Medium and Low, and 'AI research notes' as long text. Add 'Verified email' as yes or no and 'Last enriched' as a date. These keep Clay output traceable inside Pipedrive.
Build the source table in Clay
Start from a trigger source, such as Clay's own people or company search, a job change tracker or a funding feed. Or import an account list. This becomes the input column of your Clay workflow.
Add the waterfall enrichment chain
Stack providers in order of priority. For emails, for example: Hunter, then Apollo, then Prospeo, then Findymail (order checked in November 2026). Clay only charges credits when the source before it returns nothing. Set a stop once the email is found and verified.
Add AI research columns
Add AI columns with a model from Anthropic or OpenAI. Feed them the profile fields that a data provider in your waterfall returned for the LinkedIn URL, plus the company website. We do not scrape LinkedIn itself. Then summarise the company in one line and draft an opener that names one specific signal. Each column produces one output you can check, never a wall of text.
Build the verification gate
Add filter columns: email verified, company size within your ICP, country on your target list. Only rows that pass go to Pipedrive. Failed rows stay in Clay for review or another route.
Push to Pipedrive
Use Clay's native Pipedrive integration or a webhook into Make.com. Map every Clay field to its Pipedrive field. Use 'create or update' with email as the unique key, and tag the deal source as Clay plus the campaign name.
Set up monitoring
Build a Pipedrive filter on 'Clay source is not empty', grouped by enrichment confidence. Track weekly volume and the share of High. If High drops below 60 percent in a campaign, find out why.
How to check it
- Run 10 test rows through the Clay table from start to finish
- Check that the waterfall stops at the first source that returns a result
- Read the AI columns: is the output about this prospect, or did the model make it up?
- Check that only verified rows reach Pipedrive and failed rows stay in Clay
- Open one of the new Pipedrive contacts and check that Clay source, confidence and AI notes are filled
Enriching trial signups with Clay and Pipedrive
For a SaaS company, a trial signup is the moment enrichment pays off most. Somebody gives you an email and nothing else. Clay can turn that into a company, a role and a fit score within minutes, and Pipedrive decides who follows up.
Trigger
Stripe or Paddle sends a webhook on a new trial, or your app does at signup.Clay table
A Clay table with a webhook source receives the email, the plan and the signup date.Enrichment
The waterfall adds company, size, industry, country and role. Free email domains such as gmail.com are flagged and skipped.ICP score
A formula or an AI column scores the fit from 1 to 10 on your own criteria.Routing in Pipedrive
A score of 8 or higher becomes a deal for an account executive with a task for today. A score of 5 to 7 becomes a lead in the Leads Inbox. Below 5 the person goes to nurture only.Feedback
When the trial converts or ends, the result goes back to Clay, so you can check whether the score predicts anything.
Keep the score simple for the first month. Three or four criteria you can explain beat twenty that nobody trusts.
Is Clay GDPR-proof?
Clay can be used within the GDPR, but compliance depends on how you use it and which providers you chain. Clay processes data on your instructions, so you need a data processing agreement with Clay. Each provider in your waterfall is a separate source, with its own way of collecting data and its own legal basis.
- B2B prospecting usually rests on legitimate interest. Write down your assessment per type of campaign.
- Store the source per field in Pipedrive, for example 'email: Prospeo, November 2026'.
- Put European providers first in your waterfall when you target EU contacts.
- Only enrich what you use, and delete what you no longer need.
- Record the enrichment chain in your DPIA, and process every opt-out in Clay, Pipedrive and your sending tool.
- Get LinkedIn profile data from a provider that takes the URL as input, never from a scraper. Scraping tools break LinkedIn's user agreement, can get a rep's account restricted and still need a GDPR basis.
The outbound guide covers where enrichment fits in a full outbound process, and the Instantly guide covers the rules for cold email in the EU, UK and US. Scenario 5 in the Make guide uses the same LinkedIn URL pattern.
What does Clay cost per month for an outbound team?
Since March 2026, Clay sells new plans with two kinds of credits: data credits for enrichment and actions for workflow steps. At the time of writing, the Launch plan starts around 185 dollars a month with 2,500 data credits and 15,000 actions. Growth starts around 495 dollars with 6,000 data credits and 40,000 actions. There is a free plan for testing. Older Starter and Explorer plans still run for existing customers. Check clay.com for the current figures.
A worked example for a team that enriches 2,000 new contacts a month:
| Item | Assumption | Per month |
|---|---|---|
| Work email through the waterfall | about 2 data credits per contact, because most stop at the first or second source | about 4,000 data credits |
| Direct dials | for 1 in 5 contacts, about 5 data credits each | about 2,000 data credits |
| AI research and opening line | 1 column per contact | about 2,000 actions, plus model use |
| Checks in the verification gate | about 2 filter actions per contact | about 4,000 actions |
| Write to Pipedrive | 1 action per contact that passes, say 1,500 | about 1,500 actions |
| Plan | about 6,000 data credits and 7,500 actions needed | Growth (6,000 data credits, 40,000 actions), or Launch (2,500 and 15,000) with extra data credits |
Compare that with Apollo for the same 2,000 contacts. If one source finds enough of your ICP, Apollo costs a fraction of this, see the Apollo guide. The waterfall only earns its money when a single source misses a large part of your market.
Where Clay and Pipedrive pay off most
These six are the Clay workflows we build most often on top of Pipedrive.
AI-personalised email research
- Source contacts from Clay's people search or an account list
- Enrich email and job title through the waterfall
- Get profile data through a data provider that takes the LinkedIn URL as input, plus news from the company site
- An AI column drafts a one or two sentence opener that names a real signal
- Push to Pipedrive with the line stored in 'AI research notes'
- The SDR approves or rewrites it before sending through Instantly
Account-based lead lists
- Import 50 to 200 target accounts into Clay
- Find 3 to 5 contacts per account by role, such as CEO, VP Sales and Head of RevOps
- Enrich emails and direct dials through the waterfall
- Let AI score each account on ICP fit
- Push the account and its contacts into Pipedrive as one organisation with linked people
- Tag the deal source as ABM plus the quarter
Trigger-based prospecting
- Pick the trigger: a funding round, a job change, a hiring signal or a new tool
- Filter on your ICP: industry and country, plus company size
- Enrich the decision-maker through the waterfall
- Let AI summarise the trigger in one sentence
- Push to Pipedrive with a task to reach out within 48 hours and mention the trigger
- Route it to the right SDR based on territory
Job change tracking
- Sync your Pipedrive contacts into a Clay table
- Run Clay's job change tracker on the list every week
- When someone moves, enrich the new company
- Create a Pipedrive deal at the new company with source 'Job change trigger'
- Add a task for the original deal owner to get back in touch
Intent data integration
- Pull intent signals from G2 or Bombora, or from your website analytics, into Clay
- Match the intent accounts to your open and lost deals in Pipedrive
- Find accounts with high intent and no recent activity
- Push them to a Pipedrive 'High intent' filter view
- Alert the assigned rep in Slack with the intent topic and the date of the last touch
Contact verification at volume
- Export Pipedrive contacts older than 12 months with no recent activity
- Run them through Clay's verification waterfall
- Update the 'Verified email' field and the 'Last enriched' date in Pipedrive
- Flag contacts that bounce or cannot be reached as stale, for review
- Archive contacts that fail verification across 3 or more sources
Clay next to the alternatives
Clay is the heaviest option of the four. This is when one of the others fits better.
Apollo.io
Pros
- One tool, fast setup
- Strong US database
- Built-in sequencer
- Easier to learn
Cons
- Single-source enrichment limits the match rate
- No native AI research
- Weaker EU coverage
Best for: Teams running one stable playbook against a US-focused ICP
ZoomInfo
Pros
- Largest enterprise B2B database
- Strong intent data
- Phone number coverage
Cons
- Usually a five-figure annual contract
- Long contracts
- Overkill for SMB outbound
Best for: Enterprise outbound teams with a large SDR team and their own data budget
Cognism
Pros
- Strong European contact data
- Phone numbers checked by people
- Built around GDPR and do-not-call lists
Cons
- No waterfall across other sources
- No AI research columns
- Annual contract, higher entry price than Apollo
Best for: Teams that call into Europe and want one trusted source instead of a chain
Clearbit is no longer on this list. HubSpot bought it and folded it into HubSpot as Breeze Intelligence, so for a Pipedrive stack it is no longer a standalone option.
FAQ
When should I sync from Clay to Pipedrive?
Sync once verification passes, never on raw Clay output. Build, enrich and verify inside Clay, then push only the validated rows to Pipedrive. Most teams sync once per campaign run, daily or weekly, rather than in real time. The exception is trial signups and inbound leads, which should reach Pipedrive within minutes so somebody can follow up the same day.
How much does Clay actually cost in practice?
At the time of writing, new Clay plans start around 185 dollars a month for Launch and around 495 for Growth. Data credits for enrichment and actions for workflow steps are counted separately. A team enriching 2,000 contacts a month with email, some direct dials and an AI opener needs roughly 6,000 data credits. That usually means Growth, or Launch with extra credits. Check clay.com before you budget.
What is the most common mistake teams make with Clay?
Sending unverified data to the CRM. Clay can return results that look complete but contain conflicting emails, company descriptions an AI model made up, or titles from a previous job. Always build a verification gate before the Pipedrive push. Tag fields filled by AI explicitly, so reps know to review them before anything is sent.
How does the Clay + Pipedrive + Instantly stack work?
Clay handles data and research, Pipedrive holds the source of truth and Instantly sends the email. Clay enriches the contact and writes it, with the AI opener, into Pipedrive. A Make.com scenario or Instantly's own Pipedrive integration adds the person to an Instantly campaign. Replies come back through Instantly webhooks and Make, and change the lead status or create a deal in Pipedrive.
When is Clay overkill and Apollo is enough?
If you run one ICP, one playbook and one enrichment source, stay on Apollo. As a rule of thumb, below about 500 new contacts a month with a stable playbook, Clay rarely earns its cost. Clay makes sense when you need a waterfall across three or more providers, AI research at volume or trigger-based prospecting. We say so even if you already have a Clay licence.
Does Clay have a native Pipedrive integration?
Yes. Clay has its own Pipedrive integration that creates and updates persons, organisations and deals. Once your sync needs conditions, normalised values or error handling, you run into its limits. Then send a webhook from Clay into Make.com, so all the logic of your integration sits in one place instead of two.
Is Clay GDPR compliant for European prospecting?
Clay can be used within the GDPR, but compliance depends on the providers you chain and how you use the data. Sign a data processing agreement with Clay and rely on a documented legitimate interest. Store the source per field in Pipedrive and process every opt-out in all tools. Put European providers first when you target EU contacts. This is not legal advice.
Which fields can Clay deliver to Pipedrive?
The usual set covers work email, direct dial, job title and seniority, company size and industry. Add tech stack, funding, hiring signals and an AI research note. Each field has its own best source: for example Hunter, Prospeo or Findymail for email, and Cognism or Lusha for phone numbers. Clearbit is no longer a standalone option, because it is now part of HubSpot.
