​
Clay

Beta — unverified against a live account. The Clay table HTTP-endpoint contract has not been confirmed against a live Clay workspace and may change.

​
What this integration does

Pull waterfall-enriched contacts from a Clay table via its HTTP API endpoint.

​
Prerequisites

  • A Clay workspace
  • A Clay table exposed as an HTTP API endpoint that accepts a POST and returns contact rows

​
Step-by-step connection

  1. In Clay, create/enable an HTTP API endpoint for your table.
  2. In Runline go to Settings → Prospecting & sending tools → Clay → Connect.
  3. Paste the endpoint URL (and an API key if your endpoint requires one) and save.

​
What data syncs

Pull (into Runline)
  • Rows returned by your Clay endpoint (email, name, company, title), normalised to prospects
Push (out of Runline)
  • Runline POSTs your ICP (titles, locations, limit) to the endpoint

​
Troubleshooting

  • Clay endpoint URL not configured → paste the endpoint URL.
  • Non-2xx from Clay → check the table endpoint is published and the payload shape matches.

​
Disconnect

Settings → Clay → Disconnect.