The Guide to Clay Sources
Treating data sources as the front door to every workflow — a mental model for building in Clay with intent, instead of stitching columns together and hoping.
What it is & why it exists
Clay Sources are the front door for your data. They exist because data shouldn't sit in a messy pile — it has to flow cleanly into your system so it can trigger the workflows that actually move revenue.
The mistake is treating a source as an import step. It isn't. Before pulling anything in, the real question isn't "what list do I have" — it's "how should information move, and what form does it need to be in at each step?" Get that wrong and every column downstream inherits the mess.
◧The Lego Blueprint
Data isn't a flat spreadsheet. It's building blocks — each a different size and color — and the shape of a block changes as it moves from one system to the next. So before touching a single button, you visualize how your systems connect and how the data transforms step to step. You're not importing a list; you're drawing the blueprint for how information moves.
→In service of the end goal
Every source decision serves something downstream. Three questions keep the build honest — and they're a sequence, not a menu.
Know your goal
Name the outcome first: route a demo lead, update the CRM, or build messaging. The goal decides everything after it.
Have it or find it?
Do you already hold this data — a form submission — or must you go get it, like scraping a LinkedIn profile? This split is the whole decision.
Pick your block
Choose the exact Clay Source that matches your answer, plug it in, and let it feed the workflow.
Choosing the right source
That one question — have it vs. find it — cleanly splits every Clay Source into two families. Naming the family before you build is what turns "clicking buttons" into a deliberate choice.
- Webhook / API push
- Form submission
- CSV / list import
- CRM sync (HubSpot, Salesforce)
- Existing integrations
- Company search
- People / contact search
- Web & profile scrape
- Enrichment waterfalls
- Research / open-source pulls
The misconception I corrected
Going in, I thought Clay was purely an outbound sales tool — a way to sell more stuff. Building this changed that. Sources power far more than lead gen: CRM hygiene, deep research, connecting open-source projects, even a job search. No more manually opening tabs, clicking links, and copying descriptions.
The reframe: Clay is a data-movement engine, not a prospecting list. Once you see sources as the front door rather than an import, the whole tool opens up.
What shipping this taught me
I could have compared tools I already knew. I chose the unfamiliar one on purpose. I'd been building tables in Clay by stitching columns together without a real mental model — clicking buttons, not architecting. Forcing myself to articulate the blueprint above is the shift I wanted: from operating a tool to engineering with it.
My weakest instinct is reaching for old solutions to new problems. In a landscape moving this fast, staying open — and leaning into the discomfort of unfamiliar tools — is the habit worth protecting. That's really what this prompt taught me: as much about how I think as about GTM engineering.