$ man clay-http-api

Clay HTTP API Pattern

Using Clay's built-in HTTP API integration to make external API calls — like MX record lookups — directly inside a Clay table. No code, no Zapier, no middleware. Just configure the endpoint, map the response, and the data lands in a column.

Clay has native integrations for common enrichment providers, but MX record lookups aren't one of them. The HTTP API integration fills that gap. It lets you call any API from inside Clay and parse the response. This is how you extend Clay's capabilities beyond its built-in integrations without leaving the platform.

I set up an HTTP API column in Clay that calls an MX lookup service (like dns.google/resolve or a dedicated MX API). The input is the contact's email domain. The output is the raw MX record. I then use a formula column to classify the result — Google, Microsoft, or Other. This two-column pattern (HTTP API → formula classifier) is reusable. I use the same approach for tech stack lookups, SSL certificate checks, and other DNS-based enrichment.