How to send LinkedIn leads to Clay automatically: route qualified leads from traxy into a Clay table

TL;DR: To send LinkedIn leads to Clay automatically, create a webhook source in a Clay workbook, paste its URL into traxy under Integrations > Clay, send a test payload, then add a route that connects a saved lead view to Clay with Auto delivery. traxy then sends a signed event to your Clay table each time a qualified lead enters the view, plus a separate event when a lead you already have engages again.

Clay facts in this guide come from Clay's own docs, checked November 2026. traxy facts come from the traxy docs for the Clay integration and routes.

How do I send LinkedIn leads to Clay automatically?

Connect traxy to a Clay webhook and route a saved lead view to it with Auto delivery. traxy finds high intent leads from LinkedIn social intent (what people post, comment and like, profile viewers, and the people who engage with competitors' and creators' posts), keeps only people with a 50%+ ICP match, and sends each one to Clay as a signed lead event with its lead, company, contact and engagement fields.

The setup has three parts:

1. In Clay: create a webhook source and copy its URL, plus an authentication token if you want one.

2. In traxy: open Integrations > Clay, enter the HTTPS endpoint and optional authentication header, and use Send test payload.

3. In traxy: open the Clay connection's Routes tab, pick a saved view, choose Auto or Manual delivery and save.

You do not have to send leads anywhere to act on them. The same saved view can feed a LinkedIn and email campaign in traxy, which researches each lead and prepares personalized sequences that send from your own connected sender accounts after you approve the launch. More on that choice below. For a full side-by-side of the two tools, see traxy vs Clay.

What you need before you start

• A traxy workspace with your lead criteria and Signals set, so leads are already arriving.

• A saved view of the leads you want in Clay. Saved views update as leads change, and routes use shared views (saved views).

• A Clay workbook where you can add a webhook source.

• Permission in traxy to manage integrations and routes.

A good first view is narrow: for example, Warm leads in one region with a founder or head-of-sales title. A narrow view keeps the first test small and makes field mapping easier to check by eye.

What does Clay receive: lead, company, contact and engagement fields

Clay receives a JSON request for each delivery, with event metadata plus the lead, company, contact and engagement fields that are available for that lead. The exact field names are in the payload samples under Payload & help in the traxy app, so map from the sample rather than from memory (Clay integration).

Clay's docs describe its webhooks as receiving data "through HTTP POST requests in JSON format" from other applications (Clay webhooks, checked November 2026).

Two things to keep in mind. First, the payload can include contact fields that are saved on the lead; contact lookup is a separate step, so a lead without a looked-up email arrives without one. Second, the engagement context is the reason this person is on your list. Keep it as a column in Clay so whoever prepares the first message can see what the person posted, liked or commented on.

Step 1: create the Clay webhook receiver

Clay's webhook docs give these steps (Clay webhooks, checked November 2026):

1. In a workbook, click + Add at the bottom.

2. Search for Webhooks and click Monitor webhook.

3. Copy the URL. Clay describes it as the URL "where your data will be sent."

4. Optionally, add an authentication token so requests must carry it in a header. Clay says to copy the token immediately, because you can only access it once.

traxy's docs add one requirement on the receiving side: make sure it can accept requests outside a temporary test session (Clay integration). Use the webhook URL itself, not a one-off test link.

Plan the table for volume. Clay's docs say webhook sources are limited to 50,000 submissions, and that this limit persists even after deleting rows. On Enterprise plans, Clay's Auto-delete (passthrough tables) lets one webhook receive unlimited submissions; on other plans you create a new webhook once you reach 50,000 submissions (Clay webhooks, checked November 2026). Test payloads and repeat-engagement events also arrive as submissions, so they count toward that cap too.

Step 2: connect Clay in traxy and send a test payload

1. Open Integrations > Clay.

2. Enter a connection name and the HTTPS endpoint from Clay.

3. If you created an authentication token in Clay, add it as the authentication header, then save the connection.

4. Open Settings to review triggers and Payload & help.

5. Choose Send test payload and check that a new row appears in your Clay table.

A test sends one immediate request. Use that row to set up your columns before any real leads arrive. If nothing shows up in Clay, check the URL and the header first.

Two details from the traxy docs save time later. An existing authentication header stays saved when you leave its edit field empty, so editing the connection does not clear it; use the explicit removal action when you do want it gone. And disconnecting stops future delivery through the connection, but it does not delete rows already in Clay.

If you work from Claude, ChatGPT or another AI client, the traxy MCP can also create a Clay destination and queue a selected lead for delivery. Queued means the request was accepted for delivery, not that Clay received it, so check the table.

Step 3: route a saved view to Clay, automatic or manual

A route connects one audience to one destination (routes). Use separate routes when different lead views should go to different Clay tables.

1. Open the Clay connection's Routes tab and choose Add route.

2. Choose All leads or a saved view.

3. Select the Clay endpoint as the destination.

4. Choose Auto or Manual delivery. For Auto, review the ICP match threshold for this route.

5. Review the destination and save.

Auto delivery does not backfill

Automatic routes apply to leads entering the audience from that point onward. Saving or editing a route does not send every lead already in the view. To send leads you already have, select them in Leads, open Send to and choose the route.

The route threshold is not qualification

The route's ICP match threshold controls delivery to Clay only. It does not change who qualifies as a lead: only people with an ICP match of 50% or more become leads in the first place (how qualification works). Raise the route threshold when you want Clay to get only your closest fits.

Shared views and dependencies

If you pick a personal view, saving the route shares it with the workspace. A view used by a route cannot be deleted or made personal until you remove that dependency.

First delivery vs repeat engagement events

traxy sends two kinds of lead events, and the docs say they have different purposes. A first-delivery event means a person entered the routed audience as a qualified lead. A repeat-engagement event means a lead you already have engaged on LinkedIn again.

The simplest setup is one Clay table per route with a column for the event type, then conditional runs on your enrichment columns so they only fire for first-delivery rows. If you want repeat engagement in a separate place, send it to its own table and look the person up against the first one.

How do I keep the Clay table safe from repeats and bad requests?

Treat every incoming row as something that might arrive twice. traxy's docs say lead delivery can retry temporary failures, so make downstream processing safe for repeated events.

• Deduplicate on the lead. Keep the lead identifier from the payload as a column and check for an existing row before any enrichment runs, so a retried event does not trigger the same lookups twice.

• Use the authentication header. Clay's docs say you can secure the webhook with an optional authentication token sent in the request header. Store it as the authentication header on the traxy connection.

• Know what the signature is for. Every traxy request includes X-Traxy-Signature and X-Traxy-Timestamp headers, and Payload & help explains how to verify them with the signing secret. Clay's webhook docs describe the authentication token, not signature checks, so if your security team requires signature verification, send events to a receiver you control first (see the n8n LinkedIn lead workflow for a verify-and-dedupe pattern) and pass them on to Clay from there. If you rotate the signing secret, update that receiver before relying on later events.

• Watch failures on both sides. Check the delivery result in traxy and the rows in Clay. A route can pause after repeated failures. Fix an expired URL, an authentication failure or an unavailable workflow, then resume the route from its menu.

What to do in Clay next, and when you do not need Clay

Once rows arrive, Clay is a place to add your own columns. Common next steps:

• Enrich the company with the data providers you already use in Clay.

• Score accounts with your own rules, on top of traxy's ICP match.

• Send the row to your CRM, or to Clay Sequencer, which Clay describes as "the cold outbound email sequencer" and says is available on its Launch, Growth and Enterprise plans (Clay Sequencer announcement, checked November 2026). Clay's announcement describes an email sequencer; it does not list LinkedIn messages as a channel.

Before you build those columns, check which of them traxy already covers for the same leads. traxy runs your entire LinkedIn GTM end to end, from finding high intent leads from social intent to enriching and researching each one, to running relevant, personalized LinkedIn and email outreach to them on autopilot once you test on sample leads and approve the campaign, or you approve every message. In practice that means:

• Finding: Signals, Tracking of people, posts and company pages, and plain-English search over 71M+ scanned LinkedIn likes, posts and comments. Every lead shows the post or comment behind it.

• Enrichment: email lookup for a lead, and Auto-Enrich for newly qualified leads. Auto-Enrich does not backfill older leads.

• Research on each lead: a campaign researches every lead for the facts you choose before any message is prepared, filters out who does not fit and groups the rest by signal (create a campaign). When a required fact is not found, the lead stays in traxy, and in the campaign you can choose to skip it.

• Outreach: personalized LinkedIn and email sequences that send from your own connected sender accounts. You test on sample leads with nothing sent, review the launch (who joins and who is skipped), then approve it. After that the campaign runs on its own, or you approve every message in the review queue. Replies, unsubscribes and hard bounces stop the sequence (sequences).

You can run those campaigns by hand in the app, through trax (the traxy agent in the app), or from Claude or ChatGPT with the traxy MCP, which asks for your yes in chat before anything sends. You can also run many campaigns at once on different signals.

So the question is what Clay adds for this list. If the answer is a data provider or scoring logic your team owns, keep the route. If the answer is only "research the lead and send a LinkedIn and email sequence," you can skip the extra step and run it in traxy.

Where Clay fits better, and where traxy does

traxy is the vendor writing this, so here are the criteria we used: where the leads come from, who checks fit, where research and outreach happen, and how much you build yourself.

Clay fits better when your team already runs its GTM data in Clay tables, owns enrichment and scoring logic there, and wants every lead source in one workbook. Clay also has its own professional post enrichments: in a Clay table you can get reactions, comments and shares on a post by URL, or a person's recent posts, comments and reactions (Clay professional posts, checked November 2026). Those actions return a capped number of results per run, for example up to 50 reactions or 10 comments on a post, and you build the qualification step yourself.

traxy fits better when you want the LinkedIn engagers already checked against your ICP, with the post or comment behind each one, and when you want research and LinkedIn plus email outreach to run in the same place. For a broader comparison, see the best Clay alternatives.

You can also do both: traxy finds and qualifies, a route sends the leads to Clay for the steps they own there, and the same view feeds a traxy campaign for the people they want to reach on LinkedIn.

Limits to know

• No backfill. Auto routes send leads that enter the view after you save the route. Send existing leads with Leads > Send to.

• Retries can repeat events. Build the Clay table to handle the same event twice.

• Clay's submission cap. Clay limits webhook sources to 50,000 submissions, even after rows are deleted, unless you use Auto-delete on an Enterprise plan (checked November 2026).

• Contact fields depend on the lead. The payload carries contact fields saved on the lead. Run the lookup in traxy, or in Clay, if you need more.

• Engagement is interest, not a decision. A like or comment shows a reason to talk. It does not mean the person is ready to buy, and the ICP match score is not a probability of purchase.

• Disconnecting does not delete. Rows already in Clay stay there when you pause, delete a route or disconnect.

FAQ

Can I send LinkedIn leads to Clay without a scraper?

Yes. traxy finds and qualifies the leads from LinkedIn activity and sends them to a Clay webhook as signed lead events, so the Clay table starts with people who already have a 50%+ ICP match and the activity behind them.

Do leads already in my view go to Clay when I save the route?

No. Automatic routes apply to leads entering the view from then on. Select existing leads in Leads, open Send to and choose the Clay route.

What is the difference between the Clay, n8n, Zapier and Webhook connections in traxy?

All four send qualified lead events to another tool with the same pattern: endpoint, test payload, route. Pick the one where the rest of your workflow lives. See sending LinkedIn leads with Zapier and the n8n LinkedIn lead workflow for the other two.

Can Clay pull leads from traxy instead of waiting for events?

Clay's webhook receives what traxy sends. If you want your own code to read leads, signals and engagements on a schedule you choose, use the traxy REST API.

Do I need Clay to run outreach to these leads?

No. traxy campaigns research each lead and run personalized LinkedIn and email sequences from your own connected sender accounts. You approve the launch and the campaign runs on its own, or you approve every message.

How do I stop leads going to Clay?

Pause the route from its menu, or delete it to stop future routing. Disabling or disconnecting the Clay integration can stop all of its routes. Leads already sent stay in Clay.

Next step

Save one view of leads you would act on this week, create a Clay webhook, connect it under Integrations > Clay and send a test payload. Map your columns from that row, then add a route with Auto delivery. For the leads you want to reach directly, put the same view in a traxy campaign and test it on sample leads first.