Move phone-ready Clay rows into a queue.
Send phone-ready Clay rows through an HTTP recipe and store the intake result.
Rows without a phone stay in a repair view and are not sent.
- Phone-ready Clay row
- Clay sends a normalized HTTP request
- Queue result saved on the row
What you need.
HTTP intake recipe
- A Clay plan with HTTP integrations. Current documentation lists Growth and Enterprise.
- A Redialler workspace API key and queue ID.
- A durable table and row ID, a real phone, and columns for intake status and repair reasons.
Set up Clay.
Open Clay setup in Redialler Settings and download the HTTP request recipe.
Filter the Clay table to phone-ready rows. Keep missing-phone rows in a visible repair view.
Configure an HTTP request to your Redialler deployment with bearer authentication and an Idempotency-Key header.
Build
external_idfrom the table and durable row ID. Use a separate event or revision key for each changed request.Map accepted, duplicate, blocked, reason, and queue item ID into source status columns. Review the result before later enrichment or automation steps.
Confirm provider access and delivery in your account before rollout.
Data and permissions.
- Clay sends only the fields included in your request body. Redialler receives normalized lead and optional context fields.
- Keep the workspace bearer key in the private HTTP integration configuration.
- An enriched phone number does not establish permission to call. Send consent evidence only when you have its real source and capture time.
Current limits.
- This is an HTTP recipe. There is no native Clay source adapter or automatic table sync.
- Clay's native API is a separate Enterprise feature; it is not needed for this outbound HTTP recipe.
- A row position is not a stable lead ID. Sorting and insertion can change it.
- Confirm table setup, plan entitlement, and HTTP delivery in your Clay account before rollout.
Provider documentation
Questions about Clay.
Do I need Clay's native API?
The recipe uses Clay's HTTP integration to send a request. The native API is a separate feature. Confirm that your plan includes the HTTP integration.
Can I send every enriched row?
Filter for rows with real phone numbers. Keep missing or blocked rows visible for repair, and apply your calling and consent policies.
How do I resend a corrected row?
Keep its stable external_id and use a new event or revision Idempotency-Key. Reusing an idempotency key with changed request content returns HTTP 409.
Set up Clay for your workspace.
Sign in to open this tool in Settings. An organisation admin connects it for your workspace.