Blog | GenFlows

Clay Workflow Automation: The GTM Engineer's Complete Playbook for B2B Outbound in 2026

Written by GenFlows Team | Jun 24, 2026 6:24:08 PM

Clay is the data orchestration tool that sits at the centre of most serious GTM engineering stacks in 2026. It connects to over 150 data providers, runs enrichment waterfalls that achieve 80 to 85% valid contact data coverage, supports trigger-based outreach workflows, and integrates natively with HubSpot, Salesforce, Outreach, and Salesloft. Companies that use it correctly generate three times the qualified pipeline at 40 to 60% lower cost per lead compared to traditional outbound approaches.

This guide covers the exact playbooks GTM engineers use in Clay, how waterfall enrichment works in practice, the HubSpot integration setup, and the signal-based workflow patterns that consistently generate the highest reply rates.

GenFlows is a Clay-certified GTM engineering agency. If you want these playbooks implemented for your company rather than built yourself, talk to our team here.

What Clay actually does and why GTM engineers use it

Clay is a spreadsheet-style interface that connects to external data sources and automation tools via APIs. Each row represents a prospect or account. Each column can be a data enrichment action, an AI research step, a CRM lookup, or a sequence trigger. GTM engineers use Clay for three primary purposes:

  • Enrichment: Pulling contact and company data from multiple providers to build complete prospect profiles
  • Research: Using AI to process prospect data into personalised insights and opening lines
  • Orchestration: Triggering sequences in Instantly, Smartlead, or HeyReach based on enriched data and signals

Waterfall enrichment: how Clay achieves 80%+ contact coverage

Contact data from a single provider typically covers 40 to 50% of any given list. A waterfall enrichment strategy solves this by querying providers in sequence and stopping when it finds a verified result. A standard setup for email finding might look like this:

  1. Step 1 — Apollo: Try Apollo first. Covers most North American B2B contacts well.
  2. Step 2 — Icypeas: For any contact Apollo does not find. Strong coverage for European and APAC contacts.
  3. Step 3 — LeadMagic: For remaining gaps. Good for SMB and founder-led companies.
  4. Step 4 — BetterContact: Final fallback. Aggregates multiple sources and catches what others miss.
  5. Step 5 — Email verification: Run every found email through MillionVerifier or ZeroBounce before entering a sequence.

This chain typically lifts email coverage from 20 to 30% (single provider) to 80 to 85% of any ICP list. Beyond email, the enrichment waterfall can pull 30+ data points per prospect: LinkedIn URL, job title, company headcount, funding stage, technology stack, recent LinkedIn posts, company news, and G2 review activity.

The Clay + HubSpot integration: what it covers and how to set it up

Clay's HubSpot integration covers five object types: contacts, companies, leads, deals, and custom objects. It supports four operation types: importing from HubSpot into Clay, creating new objects in HubSpot, looking up existing objects, and updating existing objects with enriched data. The practical workflows are:

  • Inbound enrichment: New leads enter HubSpot from a form. Clay imports those leads, runs the enrichment waterfall, adds firmographic data, scores them against ICP criteria, and pushes the enriched, scored lead back into HubSpot with a lead score and routing tag.
  • Outbound prospecting: Clay builds a prospect list from scratch using signal data and enrichment, then creates contact and company records in HubSpot automatically so every outbound prospect is tracked from first touch.
  • CRM hygiene: Clay periodically imports existing HubSpot contacts, checks whether their data is current, and updates stale records — preventing the common problem of working from a CRM with 30 to 40% data decay.

The HubSpot connector requires Clay's Pro plan. This is a non-negotiable cost for companies that want clean bi-directional data flow between their enrichment pipeline and their CRM.

Signal-based trigger workflows: the playbooks that generate the highest reply rates

Static lists produce static results. The highest-performing outbound campaigns in 2026 are triggered by specific events that indicate a target account is in a moment of change.

Playbook 1: New executive hire trigger

When a target account hires a new VP of Sales, CRO, VP Marketing, or Head of RevOps, that executive is in a 90-day window where they are evaluating tools and looking for quick wins. The Clay workflow monitors LinkedIn for new role announcements at target accounts, identifies the new hire and their key reports, runs enrichment to find verified contact data, and generates a personalised opening line referencing the hire and a specific challenge that executives in that role typically face. The email is triggered within 48 hours of the LinkedIn post.

Playbook 2: Funding round trigger

A company that just closed a Series A or Series B has capital to spend and is actively scaling their GTM motion. Clay monitors Crunchbase and LinkedIn for funding announcements, cross-references against ICP criteria, and triggers a sequence connecting the funding context to a specific capability your product or service offers.

Playbook 3: Technology change trigger

A company that adds a specific technology to their stack is signalling priorities. Clay monitors BuiltWith data and job posting language for technology signals, then triggers personalised outreach that directly references the technology context.

Playbook 4: Job posting intent trigger

Job postings are public signals of company priorities and pain points. Clay monitors job postings at target accounts and triggers outreach based on the specific role being hired for — a company posting five SDR roles is scaling outbound and likely experiencing the pain of manual prospecting.

The complete Clay GTM stack for outbound in 2026

Stack layer Primary tool Alternative What it does
Data orchestration Clay Enrichment, research, AI columns, workflow logic
Email sending Instantly Smartlead Sequence execution, inbox rotation, deliverability
LinkedIn outreach HeyReach Expandi Multi-account LinkedIn automation
CRM HubSpot Salesforce Contact records, pipeline, attribution
Workflow automation n8n Make Connecting signals to Clay to sequences
Email verification ZeroBounce MillionVerifier Verifying emails before sequencing
Signal detection PhantomBuster / Crunchbase BuiltWith, LinkedIn Monitoring target accounts for trigger events

AI columns in Clay: what actually works

Clay's AI columns let you run prompts against prospect data at the row level. The AI columns that produce the best results in outbound are specific and bounded, not open-ended:

  • Works well: "Based on [prospect's recent LinkedIn post] and [their job title], write a one-sentence observation about a challenge they likely face related to [your category]."
  • Works poorly: "Write a personalised cold email to [name] at [company]."

AI given a clear input and asked for a bounded output produces high-quality personalisation. AI asked to write an entire email from scratch produces generic output that feels personalised on the surface but reads as templated to anyone who receives a lot of cold email.

How to measure whether your Clay workflows are working

  • Contact coverage rate: What percentage of your enriched list has a verified email? Target: 75 to 85%.
  • Positive reply rate: Specifically positive replies as a percentage of emails sent. Target: 2 to 5% for cold outbound; 5 to 10% for signal-triggered outreach.
  • Meeting book rate: Positive replies that convert to booked meetings. Target: 40 to 60%.
  • Cost per qualified meeting: Total cost of tools plus labour divided by meetings booked. Target: $150 to $400 for well-run GTM engineering systems.

GenFlows builds and manages Clay-powered GTM systems for B2B companies. We handle the tool setup, enrichment waterfall configuration, sequence writing, HubSpot integration, and ongoing optimisation. See how we work and book a call.