Skip to main content
Connect Clay when you build lists in Clay and want those people in B2B Signals, with the reason you picked them. Each row you send from Clay becomes a person in People. Data moves one way: from Clay to B2B Signals. Nothing goes back to Clay.

​
Before you start

  • A Clay plan with the HTTP API column. Clay offers it on its Growth plan or higher.
  • An API key for your workspace. “API keys come with a paid plan (Software or Custom).” See API keys.
  • To turn Clay on, or to copy or make the key, you must be the workspace owner or an admin. Anyone can follow the other steps.

​
How Clay starts safely

Until you turn Clay on, every row Clay sends is a test. Nobody is added and nothing changes. You see what would have happened, so you can check your table before real rows arrive.

​
Connect Clay

1

Open the Clay drawer

Open Sources, then Integrations. On the Clay row, press Connect. You can also open it from Settings › Integrations, on the Clay or Zapier row.
2

Add our columns in Clay

Make a Clay table with our 8 columns, then add one HTTP API column with our settings. Press Download columns (CSV) to get the column names, and Copy column settings to get the settings to paste. See The columns and The HTTP API column.If the drawer shows Copy our template into Clay instead, open the template, choose Use template, and Clay makes your own copy with the columns ready.
3

Add your key in Clay

Press Copy your key and paste it into the header account in Clay. Clay asks for it once. Keep it private.
4

Send one row to test

Run the HTTP API column on one row in Clay. Within a few seconds the drawer shows Test received: and what a real send would do. Until then it says “Waiting for a test row. Send one from Clay and it shows up here.”
Connect Clay drawer with three steps and a Test received line

The Clay drawer after a test row arrived. Nobody was added; Turn on is now available.

5

Turn Clay on

Press Turn on. You see “Clay is on. New rows from Clay are added from now on.”
Turn on stays greyed out until a test row arrives. Members who aren’t the owner or an admin see “Only an owner or admin can turn Clay on. Ask them.”

​
The columns

Name the columns exactly like this. The HTTP API column reads them by name. Every row needs a person: a LinkedIn URL, or a full name with a company. Rows with only a company are skipped.

​
The HTTP API column

Copy column settings gives you these values to paste into Clay: Keep ?source=clay in the URL. It is what makes rows a test until you turn Clay on, and how we count them as Clay rows. With Auto-update off, Clay sends only the rows you run.

​
What the test tells you

A test never searches for a person by name. A row with no LinkedIn URL and a person we don’t know yet shows as skipped in a test, even if a real row would find them.

​
What happens to each real row

  • A new person is added to People, with your reason as the reason they came up. See Reason.
  • A person already in your workspace is updated, not duplicated. We match on the LinkedIn profile.
  • A person on Do not contact is saved, but never contacted.
  • Nothing is sent to anyone. A Clay row doesn’t start a campaign, and doesn’t go to HeyReach or other tools on its own.
When a row has no LinkedIn URL, we look the person up by name and company. These lookups have limits: 150 per workspace per day, counted in UTC, and 20 in one request. Rows past the limit are refused, and Clay shows an error for them. Run them again after midnight UTC, or add the LinkedIn URL, which avoids the limit.

​
Turn Clay off

Open the Clay drawer and press Turn off next to Clay is on. You see “Clay is off. Rows from Clay are tests again.” People already added stay in People.

​
Replace your key

We keep only a fingerprint of your key, so we can’t show it again. If you need it, the owner or an admin presses Copy your key, then Make a new key.
A new key replaces the old one at once. Anything still using the old key, such as Clay, Zapier, your own code or an AI assistant, stops working until you paste the new key there.
Yes. Add ?test=true to the URL, or send "test": true in the body. That row is a test even while Clay is on.
A row from Clay sends no message. It starts a campaign only if the row names one with workflow_id.
Yes, if the body includes a workflow_id, the id of a campaign. See Zapier, Make and your own code.

Zapier, Make and your own code

The same address, from any tool.

API keys

Make and replace your key.

Sources

Every way people come in.

Do not contact

People who are never contacted.