HTTP step (default: entity / personalization)
URL:https://api.datavibe.cc/v1/gate/outbound
Clay columns: email, first_name, company, role (or title), subject,
generated_opener.
Authorization: Bearer dv_live_... and Content-Type: application/json.
Branch safely
BLOCKED,FAILED, orREJECTED: quarantine the row. Fix the Clay column named in the violation, regenerate, re-gate.QUEUEDorDISPATCHING: hold the row pending human review. Do not push to Smartlead yet.APPROVED: pass the row to Smartlead / Instantly when Clay owns dispatch.SENT: do not send again.
Entity rules
Optional: freshness records
When Clay also enriches M&A / funding / promotion dates, addmetadata.source_records and freshness_policy_days. With the
clay_revops_freshness_v1 policy template, production workflows must provide
structured source records so recent-event language is cross-checked against
dates.
Full guide: Clay RevOps integration on the docs site / landing.