Clay integrations: how the tools fit into a GTM engineering system

What are Clay integrations, and how many does Clay list?

Clay integrations are the connections that let a Clay table pull data from, or push data to, another tool. As of 17 October 2026, Clay's sitemap lists 246 pages under clay.com/integrations/data-provider, from Apollo and ZoomInfo to Smartlead, HubSpot and OpenAI. Clay's own counts vary by page: the homepage cites 150+ premium data sources and 200+ data and AI vendors, while the integrations page meta description says 50+ built-in data providers.

Clay groups the directory into categories such as CRMs, Contact Data, Contact Data Verification, Intent Data, Technographics Data, AI and Marketing and Outreach Tools. Each listing names its integration type, its plan compatibility and the actions it adds to a table, for example Find Work Email or Add Lead to Campaign.

For go-to-market (GTM) engineering, the count matters less than the order. A GTM engineer uses Clay as the workbench in the middle and chooses one or two tools per layer, rather than switching on every integration available.

How do native integrations differ from your own API key and the Clay HTTP API?

Clay's native integrations are listed as Clay-built Integrations, and each action on them is billed in one of three ways. Some are Clay Credits Only, some are Clay Credits or Bring Your Own Account, and some are Bring Your Own Account Required. The table below shows examples taken from Clay's integration pages in October 2026.

Clay's Actions and Data Credits doc says connecting your own key eliminates the Data Credit cost for that provider, but each enrichment still counts as one Action. The HTTP API column covers tools with no native listing: Clay's docs say it can send or retrieve data from any API endpoint, either enriching existing rows or acting as a source, with source pagination capped at 50,000 rows.

Which Clay integrations need the Growth plan, including Clay CRM integration?

Clay's CRM integrations need the Growth plan as of October 2026. The HubSpot and Salesforce integration pages are both marked Included in Growth+, and Clay's pricing page lists Auto-sync and enrich CRM, Integrate with any HTTP API, Automate any signal via webhook and Track web intent signals as Growth features.

Most data providers are open to every plan. Findymail, ZeroBounce, Bombora, PredictLeads, TheirStack, Champify, Warmly, Apify, OpenAI and Anthropic are all marked Included in All Plans. Smartlead, Exa, Zapier and Calendly are marked Included in Launch+, so a sequencer push needs at least Launch.

Clay's pricing page also says the Free plan includes bring your own API key but not phone number enrichment. Check plan compatibility on each listing before you design a workflow, because a CRM write-back step built on a Launch table will not run. Plan prices are covered in the Tentt Clay pricing guide.

How does a GTM engineering stack fit together around Clay?

A GTM engineering stack built on Clay runs in seven layers, in the order data flows. A signal creates a row, data providers fill in the company and person, a waterfall finds the email, a verifier checks it, AI writes the research, a sequencer sends, and the CRM records the outcome. Every tool named below has a listing on Clay's integrations directory.

You rarely need every layer on day one. A first system often uses one signal, one data source, a three-provider waterfall, one verifier, one sequencer and a CRM.

Which signal and trigger integrations start a Clay workflow?

Signal integrations decide which rows enter Clay and give you a reason to reach out now. RB2B sends identified website visitor profiles into Clay, according to its Clay listing, and Warmly is described as using person-level data and signal tracking. Champify identifies former customers and users who have changed jobs.

Account-level signals come from data feeds. PredictLeads' Clay actions return open jobs, financing events, recent news and tech stack for a domain. TheirStack finds job openings and companies by technology, and its listing says it tracks over 7,000 technologies across 50 million job postings, a vendor figure. Bombora returns company topic intent, billed as Clay Credits Only.

Start with the signal that best predicts a buying conversation for your offer, not the one with the most data. The Tentt guide to signal-based outbound covers how to pick and combine signals.

Which Clay data providers fill in company and contact data?

Clay data providers in the company and contact layer turn a domain or a name into a full record. ZoomInfo, Apollo and People Data Labs supply firmographics and people search, Crunchbase adds funding and investors, BuiltWith detects website technology, and Coresignal adds multi-source company and employee data, including headcount growth and job change signals.

This layer answers two questions per row: does the company fit your ideal customer profile, and who are the right people to contact. Clay formulas and filters are free under the 2026 pricing, so you can enrich firmographics, filter out poor fits, and only then pay to find people.

Overlap is normal. Apollo and ZoomInfo cover much of the same ground, so most teams pick one primary source and use the others only to fill specific gaps such as funding or tech stack. Coresignal's Clay listing is an HTTP API integration marked Included in Growth+, so check the plan before relying on it.

How do the email-finding waterfall and verification layers work together?

The email-finding waterfall runs several providers in sequence for the same contact, and verification checks every result before it reaches a sequencer. Clay's waterfall docs say you can reorder, add or delete providers, and the Work Email waterfall doc says you only pay credits for the provider that finds a match.

Clay's guide to finding work emails says the best single providers reach 52 to 90% coverage, while stacking three providers reaches 90 to 95%. Those are Clay's own test figures. Findymail, Prospeo, LeadMagic, Hunter, Dropcontact and BetterContact are common email steps, and ContactOut, Wiza, Lusha and FullEnrich add phones or LinkedIn-based lookups.

Verification is the next layer. ZeroBounce, NeverBounce and MillionVerifier are listed on Clay, and the Work Email waterfall can add a validation column after each provider step. Clay's guide advises you to always validate before shipping to a sequencer, and warns that catch-all addresses can pass and still bounce. The full build is in the Tentt waterfall enrichment guide.

Where do AI research integrations sit in the stack?

AI research integrations sit after the data layers, because a model writes better output when the row already holds firmographics, signals and a verified contact. Clay lists OpenAI and Anthropic as Clay-built integrations billed through Clay credits or your own account, with actions such as ChatGPT Generate text and Claude Generate text.

Search-led tools handle research the model cannot do from memory. Perplexity's Clay action runs an online AI search on Clay Credits Only, Exa's Clay action performs a search to surface relevant companies and needs your own Exa account, and Apify runs scraping actors from a Clay workflow, also with your own account.

Typical AI jobs at this layer are scoring fit, summarising a pricing page, classifying a business model and drafting one personalised opening line. Keep prompts narrow and test on a handful of rows before running a full table.

How do sequencing, CRM and routing integrations close the loop?

Sequencing and CRM integrations turn an enriched row into a conversation and a record. Smartlead's Clay listing includes Add Lead to Campaign, Lookup Lead Status in Campaign and Update Lead Category, all needing your own Smartlead account. Clay also lists Instantly, lemlist, Outreach, Salesloft, Reply.io and Woodpecker for email, and HeyReach, La Growth Machine and PhantomBuster for LinkedIn steps.

The CRM records what happened. Clay's Salesforce integration can create, update and upsert records and convert leads, and HubSpot can create objects, find owners, add records to lists and enroll contacts in sequences. Attio, Pipedrive and Close are also listed. Surfe, a tool that brings CRM actions into LinkedIn, appears on Clay as a provider for emails, phones and people search.

Routing also runs inbound back into Clay. Typeform imports form responses as a Clay source, Calendly is listed as a webhook integration, and Zapier can send any Zap data into a Clay table.

How should you choose from the Clay integrations list?

Choose from the Clay integrations list by working forward from the signal, not backward from the tools you already pay for. These four rules keep a system cheap and reliable:

1. Start from the signal: pick the event that best predicts a buying conversation, then only add data the message needs.
2. Order the waterfall by cost and match rate: cheaper providers with good coverage first, expensive ones last for the misses.
3. Verify before sending: put a validator after the waterfall and drop catch-all and role-based addresses you cannot confirm.
4. Write back to the CRM: push outcomes and new fields to HubSpot, Salesforce or Attio so the next run skips known contacts.

Use your own API key where you already hold a provider contract, since it removes the Data Credit cost while keeping one Action per run. Check each listing's plan compatibility before committing to a design.

Building your GTM engineering system from Clay integrations

Clay integrations work best as a sequence, not a shopping list: one signal, one data source, a short waterfall, a verifier, an AI step, a sequencer and a CRM write-back. Check each listing's billing mode and plan before you build, because CRM sync, webhooks and the HTTP API column sit on Growth as of October 2026.

When you review Clay integrations for your own stack, map each tool you already own to a layer and fill the gaps last. Tentt builds these GTM engineering systems for B2B teams, and the free GTM stack resources in the Tentt newsletter are a useful next step.