Recipe · Clay + webhook

Email the hiring manager same-day

The timing play: a watch fires → Clay enriches the company → your sequence sends while the req is hours old. The free tier (3 watches) covers it while you prove it.

What you need

  • A Reqbeat API key: free tier, on screen at signup, no card.
  • A Clay workspace with a webhook-source table and your sequencer connected.
  • A target list, or a role and geo search that defines one.

Step 1: create the webhook source in Clay

In Clay, create a table from a webhook source. Clay shows a URL. That URL is the endpoint your watch delivers to. Set a secret at registration and each delivery is signed (X-Plane-Signature).

Step 2: save the watch

One watch covers all postings that match it: a role and country across every company, or one account. A watch bills only when your endpoint accepts a delivery. Duplicates and failed deliveries cost nothing.

curl -s -X POST 'https://api.reqbeat.com/v1/watches' \
  -H "X-API-Key: $REQBEAT_API_KEY" \
  -d '{"q": "sdr", "geo": "United Kingdom",
       "webhook_url": "https://clay.example/wh/…"}'

Step 3: enrich and route

Each delivery lands as a Clay row with the company, the posting title and the ATS link. From there it is standard Clay: enrich the company domain, find the likely hiring manager, and verify the email.

Step 4: personalize with the receipt

The payload is a real posting, not a score, so the opener writes itself: "Saw you opened a req for {{raw_title}} this week." Link nothing. The point is you knew, same-day.

Why this converts

  • Timing: you reach the account before it solves the pain the req signals.
  • Specificity: the real posting beats "noticed you're growing". Your prospect can click the same link you saw.
  • Economics: the free tier's 3 watches and 50 delivered changes a month cover a focused play.

Your next watch could fire this afternoon.