---
name: enrich-leads-apollo-clay
description: "Enrich Inbound Leads with Apollo and Clay Waterfalls. Use when marketing passes incomplete lead data to sales, forcing reps to research the basics by hand before every first touch."
---

# Enrich Inbound Leads with Apollo and Clay Waterfalls

Marketing passes incomplete lead data to sales, forcing reps to research the basics by hand before every first touch.

## When to use this skill

- The user wants to set up or run this workflow: "Enrich Inbound Leads with Apollo and Clay Waterfalls".
- The user describes this problem: Marketing passes incomplete lead data to sales, forcing reps to research the basics by hand before every first touch.

## At a glance

- Category: Inbound
- Difficulty: Intermediate
- Time saved: 12 hours per week. This figure is an estimate, not a measured result.

## Tools

Options separated by "or" are alternatives; use whichever the user already has.

- Clay
- Apollo
- HubSpot

## Steps

1. Set up HubSpot webhook in Clay to trigger on new form submissions
2. Configure Clay waterfall: Apollo enrichment > Clearbit fallback > Claygent LinkedIn scrape
3. Write enriched data (job title, company size, tech stack) back to HubSpot contact
4. Add lead scoring logic based on enriched firmographics
5. Route high-value leads to AE queue via HubSpot workflow

## Template outline

Field names, thresholds, and message text are starting points to adapt.

~~~text
Clay Table Structure:
- Trigger: HubSpot webhook (form submission)
- Column 1: Apollo enrichment (email -> company data)
- Column 2: Clearbit fallback (if Apollo returns null)
- Column 3: Claygent prompt to extract role level from LinkedIn
- Column 4: Lead score calculation (IF company size > 500 AND title contains "Director", score = 90)
- Write-back: HubSpot HTTP API update contact
~~~

## Guardrails

- Work only in the user's own accounts and workspaces, with their credentials.
- Confirm with the user before any step that writes to a CRM, sends email or messages, spends credits, or moves money.
- Treat every hours, cost, and threshold figure as a starting assumption and replace it with the user's numbers.
- Do not invent data, prices, or results. If a vendor price matters, check the vendor's current pricing page.

## Source

https://gtmplaybooks.io/playbooks/enrich-leads-apollo-clay/