Optimizing Clay Workflows for B2B Lead Enrichment Success

Hey Clay Community! 🚀 I'm thrilled to share a workflow that I believe could be super valuable for anyone running B2B enrichment, lead targeting, or GTM campaigns using Clay. It's designed to automatically discover People, enrich them, and identify top contacts using AI – and it’s already speeding up our outreach dramatically. 📊 My Tables Setup:

Company Level Data – Enriched by domain.
All Engineers – Found via “Find People” from Company Level Data.
All Decision Makers – Same process as engineers.
Top Engineers – Filtered from All Engineers using Claygent AI.
Top Decision Makers – Filtered from All Decision Makers using Claygent.
Find Contact by Name and Company – Used to enrich contact → get domain → write domain back into Company Level Data to auto-trigger company enrichment.

🔁 Workflow Summary:

1.
Use "Find People" in All Engineers and All Decision Makers based on Company Level Data.
2.
Apply "Lookup Multiple Rows" in Company Level Data to fetch engineers and decision makers from their respective tables.
3.
Use these lookup outputs in an LLM step to identify Top Engineers and Top Decision Makers via Claygent.
4.
In a separate flow, enrich contacts by name & company → write the domain back to Company Level Data → which triggers enrichment again.

⚠️ Problem: The “Find People” columns in the All Engineers and All Decision Makers tables sometimes return data with a delay or not at all on first pass. As a result, the lookups in Company Level Data run too early, before those tables are populated, which causes my LLM inputs to be incomplete or empty. 🧠 What I'm Looking For: I want to trigger the lookup and AI steps only after the “Find People” functions have successfully run. Here are a few thoughts — and I’d love guidance or alternative ideas:

Is there a way to conditionally run lookups based on a flag or status column confirming data exists in Engineers/Decision Makers tables?
Can we introduce a “Ready” state or trigger field to sequence execution between data fetch and lookup?
Any creative hacks or native ways in Clay to ensure downstream steps don’t run prematurely?

This workflow could really benefit a lot of Clay users building scalable outbound engines — so I'd love your help in getting it over the finish line! 🧩✨

0 comments