Guide

Send a Clay table to a campaign.

To send a Clay table to a LinkedIn campaign, add Clay’s HTTP API enrichment to the table and POST each row’s LinkedIn URL and fields to our add-leads endpoint with your API key. The leads join the campaign you name and go to the sender with the most weekly room. We have no native Clay integration. We make a competing LinkedIn outreach tool.

About 20 minutes7 steps
Table of contents

Before you start

  • A Clay table with a LinkedIn profile URL column, built from whatever sources you use in Clay. We don’t find or enrich leads
  • A launched campaign in our app, with the messages and the senders chosen. Clay can’t create one for you
  • An API key from Settings → API

The steps

Know what Clay does and what we do

Clay builds and enriches the table. We send the connection requests and messages from your connected senders. The link between them is one HTTP call per row.

We have no native Clay integration, so there is no Clay action to pick. Clay’s documentation (read 2026-11-15) describes an HTTP API enrichment that calls any API with a method, an endpoint, headers and a JSON body that can reference table columns. That is how a Clay table reaches our API.

For comparison, HeyReach’s help page Integrate HeyReach and Clay (read 2026-11-15) describes a native integration: an Add Lead to Campaign action in Clay, connected with a HeyReach API key, into an existing campaign. Clay’s own HeyReach page (read 2026-11-15) says Clay can’t create campaigns there either, so the campaign has to exist first. Ours takes a few more steps to set up, and the result is the same kind of thing: rows from a table become leads in a campaign.

Neither side creates your campaign. Write the sequence and pick the senders in the app first.

Get the campaign’s id

Call GET /public/v1/campaigns on our API host with your key in the X-API-Key header. It returns each campaign’s id, name and status. Copy the id of the campaign you want to feed.

The campaign has to be launched. Adding leads to one that is still a draft returns an error. Adding leads to a paused campaign is allowed: they wait until it resumes.

Keep the id with the table, for example in the column’s name, so the next person knows where the rows go.

Save the API key in Clay as a header account

Clay’s documentation (read 2026-11-15) says manually typed headers are visible in plain text to anyone with access to the column, and recommends saving keys in a header account under Settings → Connections and choosing it in the column.

Create a header account with the header name X-API-Key and your key as the value.

A key is one per workspace. If it leaks, revoke it in Settings → API and make a new one.

Add the HTTP API column

In the Clay table, click Add enrichment, search for HTTP API and choose Configure. Set:

  • Method: POST
  • Endpoint: https://{our API host}/public/v1/campaigns/{campaign_id}/leads
  • Headers: the header account from step 3
  • Body: a JSON object with one lead in it. In Clay’s body, typing a slash and a column name inserts that column’s value, and string values go in quotes.
{
  "leads": [
    {
      "profile_url": "/LinkedIn URL",
      "first_name": "/First name",
      "last_name": "/Last name",
      "company": "/Company",
      "title": "/Job title",
      "custom_fields": { "angle": "/Angle" }
    }
  ]
}

profile_url is the one field a lead needs. We accept first_name, last_name, company, title, location and any custom_fields you add. Turn on Clay’s option to remove empty fields, so a blank cell isn’t sent as an empty value.

Clay’s column sends one row per call, so each call carries one lead. Our endpoint takes up to 100 leads a call, and it is rate limited per key, so set a rate limit on the Clay column too.

Test on one row, then run the table

Click Test on a single row, as Clay’s documentation describes. A good response looks like this:

{ "status": "success", "data": { "added": 1, "skipped": 0, "invalid": 0 } }

Clay lets you return only part of a response using a field path, so data.added gives you a column of 1s and 0s.

skipped means we found the lead but didn’t enrol it, for example because the person is already live in another campaign. invalid means the value in profile_url isn’t a LinkedIn profile URL. Fix those rows in Clay, then run the rest.

Before you run the whole table, open the campaign in our app and use the lead preview on one of the new leads. Check that every variable in your messages fills, and that each one has a fallback, such as {first_name|there}.

A lead you sent twice isn’t duplicated. The same person imported again is updated, not added a second time.

Send replies back into a Clay table

Clay’s webhook source works the other way. Its documentation (read 2026-11-15) says you add a Webhooks source to a workbook, copy its URL, and that sending apps POST JSON to it so the table gets a new row. It also says you can add an authentication token to the request header and that a webhook source is limited to 50,000 submissions.

In our app, open Settings → Webhooks and add an endpoint with that URL. Choose the message.replied event, and the campaign if you want to limit it. If you set a token in Clay, add it as one of the endpoint’s custom headers: we allow up to 5, and credentials go in a header, never in the URL.

Each reply then arrives in Clay as a row with the lead, the campaign, the sender and the message. A reply also stops that lead in every campaign.

The other events are connection.sent, connection.accepted, message.sent, message.received, lead.tagged, lead.finished and campaign.finished.

Plan the volume for a team

Clay can fill a campaign in minutes. Sending takes longer, because each connected sender starts at 15 connection requests a day, can be raised to 25, and never sends more than 100 a week, inside Monday to Friday, 09:00 to 18:00 in its own time zone.

With 5 senders on one campaign that is 75 requests a day to start and 500 a week at most. We give each lead to the sender with the most weekly room left, and the lead stays with that sender. A 2,000-row table therefore takes weeks, whichever tool added the rows. See the weekly invitation limit and running one campaign from several accounts.

The price is $29 a month per connected sender with every feature and free members: $29 for 1 sender, $87 for 3, $145 for 5 and $290 for 10. The API and webhooks are on every plan. See pricing. HeyReach’s list price is on its own pricing page, and our HeyReach comparison shows the figures with their dates.

More rows don’t make a sender faster. More senders add capacity, each on its owner’s own account.

What you end up with

Rows from a Clay table become leads in a launched campaign through the HTTP API column, and replies come back to a Clay table as rows.

Good to know

Questions, answered plainly.

Something missing? Ask us and we’ll add it here.

Is there a Clay LinkedIn outreach integration?

We have no native Clay integration. Clay’s HTTP API enrichment can call our add-leads endpoint with your API key, one row per call, and our webhooks can post replies to a Clay webhook source. Both steps are in this guide.

How do I send a Clay table to a LinkedIn campaign?

Launch a campaign in our app, find its id with GET /public/v1/campaigns, then add an HTTP API column in Clay that POSTs each row’s LinkedIn URL and fields to /public/v1/campaigns/{campaign_id}/leads with your key in the X-API-Key header. Test one row, then run the table.

How does a Clay LinkedIn outreach setup differ from HeyReach’s?

HeyReach’s help page, read 2026-11-15, describes a native Clay action called Add Lead to Campaign, connected with a HeyReach API key. Ours uses Clay’s generic HTTP API column against our API, so you build the request yourself. Both need an existing campaign. Clay’s page for HeyReach says Clay can’t create one.

What does HeyReach’s Clay integration require?

Per Clay’s HeyReach page and HeyReach’s help page, both read 2026-11-15: a HeyReach API key, an existing campaign’s id, and a first name, last name and profile URL for each lead. Custom field names must match the variable names in the HeyReach sequence exactly. Neither page states a lead limit.

Can Clay add many leads to a campaign at once?

Our endpoint takes up to 100 leads in one call. Clay’s HTTP API column sends one row per call, so each call carries one lead. The campaign’s senders still send at their own limits, starting at 15 connection requests a day each.