Step 1: Webhooks by Zapier Catch Hook
1) Create the Zap trigger (Zapier)
In Zapier: Create Zap For Trigger: choose Webhooks by Zapier Catch Hook. Click Continue.
Copy the Webhook URL Zapier gives you (it looks like
https://hooks.zapier.com/hooks/catch/123456/abcdef)
Zapier gave you a Webhook URL (something like https://hooks.zapier.com/...)
In Clay, you must add an HTTP API enrichment that sends your row data (name, email, company, etc.) to this URL.
That’s how Zapier knows which lead you want to send.
Without this, your Zap will just sit there waiting.
Where to Paste the Zapier Webhook in Clay
Open your Clay table (the one with your leads).
At the top of the table, click “+ Add Enrichment”.
Enrichments are Clay’s way of calling APIs or tools.
From the list, choose “HTTP API”.
This lets you send your row’s data to any external URL.
In the HTTP API setup window:
Method → choose POST
URL → paste the Zapier Webhook URL (the one from your “Catch Hook” step in Zapier).
Headers → leave empty (not needed for Zapier).
Body (JSON) → paste the structure you want to send.
once you’ve pasted the Zapier Webhook into Clay and tested sending a row, here’s exactly what to do next step by step:
Test Your Trigger in Zapier
Go back to Zapier → open your Zap (the one with Catch Hook).
Click Test Trigger.
If Clay sent the data correctly, you’ll see something like:
{ "first_name": "Ashley",
"last_name": "Adams",
"email": "[email protected]",
"company": "TechStars",
"row_id": "row_123abc"
}
This confirms Clay → Zapier connection works.
Step 2: Set Up the Sendr Step
In your Zap, go to Step 2: Sendr (Generate Sendr Page).
Zapier will ask you to connect your Sendr account. Enter your Sendr API key (you’ll find it inside your Sendr dashboard → Settings).
Now map the fields:
First Name ← first_name from Zap trigger
Email ← email from Zap trigger
Company ← company from Zap trigger
Message/Template ← either pick a template in Sendr or paste a message body
When you run Test Action, Sendr should create a message and return something like:
{
"message_id": "msg_789xyz",
"status": "sent"
}
Step 3: Send Info Back to Clay (POST step)
Right now Sendr knows the message was sent but Clay doesn’t. So we add Step 3.
Go to Step 3: Webhooks by Zapier → POST.
In the URL, paste Clay’s “Update Row” API endpoint.
If you’re using Clay’s Zapier app instead, you can use Clay Update Record (easier).
In the Body (JSON), include:
Step 4: Sendr Generate Sendr Page
Here, you’re telling Sendr: “Take this person from Clay and send them a message.”
You’ll need to map the fields:
first_name → from Clay
email → from Clay
company → from Clay
Then choose or create a template in Sendr (the actual message content).
When you test this, Sendr should respond with something like: “Message created, ID: xyz123”.
Step 5 : Webhooks by Zapier — POST
This step is how you send info back to Clay (so Clay knows the message was sent).
You’ll POST to Clay’s API endpoint (or use the Clay app in Zapier if available).
In the Body, include:
The row_id from Clay (so Clay knows which row to update).
The sendr_message_id that Sendr gave you.
Maybe set a column status = sent.
After this, your Clay table will show that the message was sent, not just sitting there.
What’s Still Missing
Right now, your Zap only goes one way:
Clay → Sendr → Clay (mark sent).
To finish the circle, you also need a second Zap:
Trigger = Sendr Webhook (for events like open, reply, click).
z
Action = Clay Update Row (mark status = opened/replied/etc.).
That’s how you’ll see replies/opens show up in Clay automatically.