LinkedIn Sales Navigator Clay Integration: Step-by-Step Guide (2026)

Setting up a LinkedIn Sales Navigator Clay integration with Evaboot lets you send enriched lead data directly from Sales Navigator into your Clay workflows via webhook.

It requires a little setting up, but once it's integrated, you can have constant flow between the 2 platforms, saving time and making your sales teams more efficient.

Evaboot notifies Clay the instant an export job completes. No CSV, no copy-pasting.

Once connected, every Sales Navigator export you run through Evaboot fires a webhook to Clay automatically. Your leads land as rows in a Clay table, ready for enrichment, filtering, or outreach.

Let's get into it.

How To Set Up the LinkedIn Sales Navigator Clay Integration

Setting up the LinkedIn Sales Navigator Clay integration takes 9 steps: generate a webhook URL in Clay, paste it into Evaboot, configure your job type and filters, then test and save.

Expect the full setup to take about 15 minutes. The full walkthrough is below.

1. Create a New Workbook in Clay

Log into Clay and create a new workbook by clicking New → Workbook. This is where your Evaboot lead data will land.

2. Add a Webhook Source

In your Clay workbook, click + Add at the bottom, search for Webhooks, and select Monitor webhook. Then copy the provided webhook URL.

A panel will appear on the right showing Pull in data from a Webhook.

3. Copy the Webhook URL

From the webhook panel, copy the Webhook URL. You'll paste this into Evaboot in the next step.

Optionally, you can add an auth token for extra security. This isn't required, but if you add one here, you'll need to enter the same token in Evaboot.

If you add or change an auth token, give Clay a moment to update before testing. You do not need to keep the Clay tab open.

The webhook endpoint automatically receives valid HTTP POST requests after it has been created..

4. Go to Integrations in Evaboot

In Evaboot, navigate to Integrations → Webhooks. This is where all webhook-based integrations are configured, including Clay.

5. Paste the Webhook URL

Paste the webhook URL you copied from Clay. If you added an auth token in Clay, enter the same token here.

6. Choose Job Type and Filters

Select which Evaboot job type this integration will handle:

Each job type sends a different data structure. You can click View sample webhook data to preview exactly what Clay will receive before committing.

If you select Sales Navigator Export, two additional filters appear:

Lead filter:

Email filter:

Clay uses Actions and Data Credits. Start with Only filtered leads and Safe only to keep your table clean and avoid wasting credits on duplicate or unverified leads.

7. Choose Execution Mode

Select how Evaboot triggers the webhook:

• Automatic — the webhook fires after the export and any selected email enrichment have finished processing. Best for ongoing workflows. Only one automatic integration per job type is allowed.
• Manual — you choose which completed jobs to send from the Evaboot dashboard. Useful if you want to review exports before they hit Clay.

8. Test the Webhook

Before saving, you must run a test. Make sure the Clay webhook source is still open and ready to receive data, then click Test Webhook in Evaboot.

Evaboot sends a sample payload to Clay and waits for a response.

If it succeeds, you'll see a green success log in Evaboot and the Create Integration button becomes active.

If it fails, check:

• Clay is open and the webhook source is active
• The webhook URL was copied correctly
• Auth tokens match on both sides
• If you recently changed the auth token, wait a moment and try again

9. Name and Save the Integration

Give the integration a name — something like 'Sales Nav → Clay Auto' works well — then click Create Integration.

The integration is now live. Evaboot will send data to Clay based on the job type, filters, and execution mode you configured.

How To Write Prospects to Rows in Clay

To write prospects to individual rows in Clay, use the 'Write each item to new row in other table' action on the Prospects array — this is a one-time setup that splits the single webhook payload into one row per prospect automatically for every future export.

When Evaboot sends data to Clay, it arrives as a single webhook payload containing an array of prospects. Clay stores this as one row by default.

Here's how to split it:

Clay will create a new table and populate it with one row per prospect from your Evaboot export.

How To Add Columns From the Evaboot Payload

Nested payload fields may need to be extracted or mapped into columns. Clay’s Send Table Data feature can also automatically extract and map new columns. — it only takes a minute.

Typical fields to add: First Name, Last Name, Email, Job Title, Company Name, LinkedIn URL, Company Size, Location.

What Data Does Evaboot Send to Clay?

For a Sales Navigator Export, Evaboot sends four categories of data to Clay:

1. contact info (name, verified email, LinkedIn URL)
2. professional details (job title, seniority, department)
3. company data (name, size, industry, location)
4. export metadata (list name, export date).

The payload depends on the job type.

Before the webhook fires, Evaboot cleans the data — removing duplicates, correcting malformed job titles, and filtering based on the email and lead filters you configured. What arrives in Clay is already cleaned and ready to enrich.

Field Mapping: What Data Flows Into Clay

Every field in the Evaboot payload maps to a column you can create in Clay. The table below shows every payload field and how it typically maps:

Use this table to plan your Clay columns before running your first export. Once the columns are set up, every subsequent webhook populates them automatically.

Can You Automate Sales Navigator to Clay?

Yes. Setting the execution mode to Automatic means you never have to manually trigger the webhook.

The moment a Sales Navigator export finishes processing in Evaboot, the data fires to Clay automatically.

Combined with Clay's Auto-update setting on the table action, new prospects flow into your Clay table without any manual steps.

From there, Clay can run enrichment, scoring, or route leads into outreach sequences automatically.

If you run multiple types of exports — for example, Sales Navigator leads and URL enrichment — you can set up separate integrations for each job type, each pointing to a different Clay workbook or table.

Which Plans Support This Integration?

You need an active Clay account and an Evaboot account. Both platforms offer webhook support across their paid tiers.

Clay: Clay’s 14-day trial includes access to webhooks. Under current standard pricing, webhook automation is listed as a Growth-plan feature.

Evaboot: Webhooks are available on all paid plans, starting at $9/month. A paid plan is required for automatic execution and higher export limits.

If you're testing the integration, start with Clay's free tier and Evaboot's trial. Once you verify the workflow, upgrade both plans to match your export volume and enrichment needs.

Enrich Missing Fields with Waterfall Enrichment

Clay's waterfall enrichment runs multiple data providers in sequence until a field is filled — for example, checking Clearbit, then Hunter, then RocketReach for an email address.

Set up a waterfall column for any missing field (work email, phone, company tech stack) and Clay will backfill it automatically for every new row the Evaboot webhook sends.

Score Prospects by ICP Fit

Use Clay’s AI attribute columns to score each lead based on ICP fit, buying signals, and seniority. Prioritize high-fit prospects for outreach and route lower-fit leads to a separate nurture table.

Personalize Outreach Copy with AI

Clay's AI enrichment column writes per-row personalized copy grounded in enriched fields, closing the gap between scrape and send for Sales Navigator exports.

Use Claygent, Clay's AI web research agent, to auto-run per-row research prompts on Sales Navigator leads the moment they land in Clay via the Evaboot webhook, e.g., 'Find this company's latest funding round' or 'Summarize the prospect's recent LinkedIn posts'.

Newly possible because Claygent now runs as a native column-level AI agent inside Clay tables, so every webhook-triggered row can be enriched with LLM-generated research without leaving the workbook.

Set up these three workflows once, and every Sales Navigator export you run through Evaboot lands in Clay enriched, scored, and ready to send.

Claygent Research Trigger: Full Setup Workflow

There are 4 steps to fully set up the Claygent research trigger:

1. Setting Up the Claygent Column

• Open the table receiving your split-out Evaboot prospect rows, the same table where your firstName, companyName, and linkedinUrl columns already live.
• Click + to add a new column, then select the AI/Claygent research column type from the enrichment options.
• Name the column clearly based on what it's researching (e.g., "Funding Research" or "Recent LinkedIn Activity") this matters once you're stacking several Claygent columns side by side.
• Reference existing row fields in your prompt using Clay's variable syntax, so Claygent has the company name or LinkedIn URL to actually search against rather than working blind.

2. Writing the Research Prompt

1. Keep the prompt narrow and specific, vague prompts like

2. State the output format you want directly in the prompt (e.g., "Respond in one sentence" or "Return just the dollar amount and date") this keeps the column output clean enough to drop straight into an outreach template.
3. Avoid stacking multiple asks in one prompt, a column asking for funding and headcount and recent news tends to return incomplete answers on at least one. Split into separate Claygent columns instead.

3. Automating the Trigger on New Rows

• Set the column's run settings to trigger automatically on new row creation, so it fires the moment a webhook-triggered row lands from Evaboot, no manual click needed.
• Confirm this sits downstream of your "Write each item to new row" action, since Claygent needs the row to exist before it can run against it.
• Leave Auto-update enabled at the table level, matching the same setting used elsewhere in the Clay workflow for waterfall enrichment and row-splitting, consistency here means one setting change won't break the pipeline elsewhere.

4. Quality-Checking Before Full Automation

• Spot-check 5–10 rows before scaling, as Claygent may return outdated or misattributed information.
• Empty results often indicate incorrect upstream field mapping, especially for the LinkedIn URL.
• Verify accuracy before sending the final output to your outreach sequence.

Pre-Automation Checklist: Validating Your Pipeline Before Going Live

Before switching to full automation, it's worth confirming the pipeline actually holds up under real conditions, not just the sample test payload. The checklist below walks through a few manual runs to catch issues while there's still a human checkpoint in place.

1. Why One Test Payload Isn't Enough

• A test webhook only confirms that Clay and Evaboot are connected, not that your table structure, filters, and enrichment logic work at scale.
• Sample payloads are clean and may not reveal real export issues like missing emails, duplicate leads, or malformed job titles.
• Before enabling automatic mode, check the setup carefully because future exports will run without a human review step.

2. Running Manual Exports First

• Start with Manual mode to review each export before it reaches Clay.
• Run 2–3 real Sales Navigator exports using realistic lead volumes and list types.
• Send exports one at a time so any issue is easier to identify.
• Test different lead and email filters to find the cleanest setup before enabling Automatic mode.

3. Verifying Data Integrity Across Test Runs

• Check every mapped column across all manual exports, not just the first few rows, to identify missing, incorrect, or malformed data.
• Confirm the “Write each item to new row” action works correctly without creating duplicates, dropping prospects, or writing incomplete rows.
• Review job titles, company names, and other key fields for gaps that may still pass through Evaboot’s filtering process.
• Compare the total row count in Evaboot and Clay after each export. Any mismatch may indicate an issue with the filters, webhook, or row-splitting setup.

4. Monitoring Credit Usage and Making the Switch

• Track Clay credit usage during each manual run to confirm your lead and email filters are removing duplicates, unverified contacts, and low-quality records before enrichment.
• Compare credit consumption with lead quality. If credits are being spent on incomplete or unusable leads, tighten the filters before increasing export volume.
• Switch Execution Mode to Automatic only after all three manual tests show correct column mapping, complete rows, no duplicates, and expected credit usage.
• Keep Auto-update enabled at the table level so the verified workflow continues processing future exports without additional manual steps.

Troubleshooting Common Integration Errors

Most webhook failures come down to three issues: Clay not ready to receive data, auth token mismatch, or rate limits. Here's how to fix each.

1. Error: Webhook Test Fails in Evaboot

Cause: Clay's webhook source is closed or not listening when Evaboot sends the test payload.

Fix: Open the Clay workbook, navigate to the webhook source panel, and leave it open. Then run the test webhook again from Evaboot. If the issue persists, refresh the Clay tab and regenerate the webhook URL.

2. Error: Auth Token Mismatch

Cause: The auth token entered in Evaboot doesn't match the token set in Clay.

Fix: Copy the auth token from Clay's webhook source panel and paste it exactly into Evaboot's integration settings. If you recently updated the token in Clay, wait 30 seconds for the change to propagate before retesting.

3. Error: Webhook Fires But No Rows Appear in Clay

Cause: The 'Write each item to new row' action isn't configured, or the destination table is set to manual-run mode.

Fix: Open the Clay table that receives the webhook payload. Click the first row, hover over the Prospects array, and set up the 'Write each item to new row in other table' action.

Make sure Auto-update is enabled in the run settings. Then resend the webhook from Evaboot's integration dashboard.

Frequently asked questions