Skip to main content
Clay has no general-purpose read API — data flows into Indexbrain the opposite way from every other integration: you configure Clay to push rows out, rather than Indexbrain pulling them in.

​
Setup

1

Go to Integrations

Navigate to Settings > Integrations > Clay.
2

Create the webhook URL

Click Create webhook URL — no API key needed.
3

Add an HTTP API step in Clay

In your Clay table’s workflow, add an HTTP API step and set its URL to the one Indexbrain just gave you.
4

Run the workflow

Every row that runs through that step is sent to Indexbrain automatically.
The webhook URL is the only credential this connection has — anyone with the URL can send data as this connection. Treat it like an API key: don’t paste it anywhere public.

​
Why this works differently than other integrations

Clay doesn’t offer a REST API you can call to read table contents — this is confirmed directly from Clay’s own documentation, not a guess. Clay’s real integration surface is built around webhooks and workflow steps inside Clay itself, not an external API to query. So instead of Indexbrain periodically asking Clay “what’s changed,” you tell Clay to tell Indexbrain — once, per table, as part of a workflow you already control.

​
What Indexbrain can do with Clay data

Once rows are flowing in, they’re searchable the same way as any other connected source:

​
What Indexbrain does NOT do with Clay

This is a meaningfully smaller capability set than some other tools claim for Clay integrations — stated plainly rather than implied:
  • No enrichment. Indexbrain cannot ask Clay to enrich a list of companies — enrichment happens inside Clay itself, triggered by you, not by Indexbrain.
  • No prospecting. Indexbrain cannot build a new list of companies or contacts in Clay — it can only receive rows you’ve already chosen to send.
  • No table listing. Indexbrain has no way to see what tables exist in your Clay workspace — it only ever sees whatever rows get pushed to its webhook.
  • No write access of any kind.
If you’re looking for Indexbrain to run Clay searches or enrichment on your behalf, that’s not what this integration does — it’s a receiving end for data you’re already producing in Clay.

​
Troubleshooting

  • Confirm the HTTP API step in your Clay table actually points at the exact webhook URL from Settings > Integrations > Clay.
  • Confirm the workflow step has actually run — nothing is pulled automatically, only what’s explicitly pushed.
  • It’s shown persistently on the Clay integration page once connected — no need to reconnect to see it again.