Key Takeaways (TL;DR)
These Clay workflow templates come from live client builds, not theory. Five specific workflows, with the exact logic behind each one.
A job change workflow only becomes useful once you build the tier check into it. Without tiering, every job change looks equally urgent, and none of them are.
Self-serve Clay workflow templates, like phone lookups and decision maker searches, exist so reps stop building inside Clay. A checkbox on a CRM record should be enough.
Cost engineering matters as much as the workflow logic. One client processed 18,000 leads for about $38 by routing classification through OpenAI instead of Clay credits alone.
None of these templates are gated behind a form. Every Clay workflow template in this guide ships with the field mapping logic included, not held back for a sales call.
The GTM Engineering Company can build these workflows the same way for companies; documented with an SOP and a Loom walkthrough, so the system stays long after the engagement ends.
Table of Contents
Clay Workflow Templates at a Glance
What Are Clay Workflow Templates?
Template 1: The Job Change Workflow
Template 2: Self-Serve Phone Number Lookups
Template 3: Find Decision Makers on Demand
Template 4: Find Lookalikes After a Closed Deal
Template 5: Website Visitor Signal Routing
Field Mappings Behind Every Template
Common Clay AI Triggers and Rules
Clay Use Cases Across Enrichment, Routing, and Scoring
Everything You Need to Know About Clay Workflow Templates
Build Custom Clay Workflows with The GTM Engineering Company
FAQs About Clay Workflow Templates
Clay Workflow Templates: at a Glance
Template | What Does It Do? | Trigger |
Job change workflow | Flags contacts who left their company, checks account tier, routes or suppresses | Scheduled LinkedIn re-check |
Phone number lookup | Finds a contact or account-wide phone numbers on request | CRM checkbox field |
Find decision makers | Finds and enriches new contacts inside a target account | CRM signal or checkbox |
Find lookalikes | Finds similar companies after a deal closes, enriches decision makers | Deal marked closed won |
Website visitor signal | Deanonymizes site visitors, scores and tiers them, routes to the right rep | Website visit event |
What Are Clay Workflow Templates?
Clay workflow templates are reusable automations built inside Clay. Each one handles a specific, repeatable task: enriching a contact, checking a job change, finding a phone number, or routing a signal to the right rep.
The word "template" undersells what these actually are. A good Clay workflow template is not a static table you copy once.
It is a running system. Field mappings, trigger logic, and CRM writeback rules are already worked out, so you are not solving the same problem from scratch every time a new use case comes up.
The same logic applies to Clay workflows trial signup enrichment routing templates. A new signup needs the same enrichment and routing treatment as a job change or a website visit.
Most teams searching for these want 2 things at once: something they can adapt quickly, and something that will not quietly break in 3 months. Those 2 goals pull against each other more than people expect.
A template that is too generic breaks the first time your CRM schema does not match. A template that is too specific only works for the exact use case it was built for.
The five templates in this guide come from actual client builds. Each one includes the trigger, the enrichment steps, and the CRM writeback logic, since a template without writeback logic is really just half a workflow.
For the underlying principles behind why these workflows are structured this way, see our guide on Clay automation.
Template 1: The Job Change Workflow
Job change tracking sounds simple until you build it.
Most templates for lead enrichment stop at "find out if this person changed jobs." That is not the useful part. The useful part is what happens next.
This is one of the more detailed Clay workflow templates lead enrichment builds in this guide, since it branches into several outcomes rather than a single lookup.
Here is how the full workflow runs, step by step:
Step 1: Check if the contact exists in the CRM with a LinkedIn URL
If the contact is already in the CRM but has no LinkedIn URL on file, the workflow needs to find one first.
A LinkedIn URL is the main input for everything that follows, since it is what lets Clay pull current and past employment history for that person.
Step 2: Enrich the person and compare the current job to the CRM account
Once the LinkedIn URL is confirmed, Clay enriches the contact and pulls their employment history. That history gets compared against the account the contact is currently linked to inside the CRM.
If the enriched profile does not show the CRM's associated company anywhere in that person's job history, that is usually a sign the LinkedIn match was wrong, not that the data is bad.
The workflow re-runs the LinkedIn search once more before flagging the record for manual review, giving it 2 tries total before giving up.
Step 3: Handle the "still employed" case
If the comparison confirms the contact still works at the company on record, the workflow stamps that record inside the CRM.
This is a simple confirmation flag, and it matters because it tells anyone looking at the record later that the data was checked, not just assumed.
Step 4: Handle the "job change confirmed" case
This is where the workflow earns its place in your Clay automation templates lead routing stack.
Once a job change is confirmed, the workflow checks the tier of the new company the contact now works at:
Tier 2 or tier 3 account: No action needed. Update the record and move on.
Tier 1 account: Update the contact record, then flag it for an SDR or AE. Someone who already knew your product or did business with you is now sitting inside an account you actively want to win. That context is worth a rep's attention.
Contact left the company entirely, with no new employer found: Tag the old CRM record as do-not-contact. Emailing someone who no longer works there just bounces, and repeated bounces damage domain reputation over time.
This single Clay lead scoring dependency is why the job change workflow needs account tiers already built before it runs.
Without tiers, every job change looks equally important, and reps end up chasing noise instead of the accounts that actually matter.
Template 2: Self-Serve Phone Number Lookups
Not every Clay workflow needs to run automatically. Some of the most useful Clay workflow people list templates exist so a rep can request enrichment without ever opening Clay.
The logic here is straightforward:
Create a checkbox field on the CRM record, something like "find contact phone" or "find company phone."
When a rep checks that box, a webhook fires from the CRM to Clay.
Clay finds the phone number and writes it back to the same record.
The account-level version works the same way, just scoped wider. Instead of finding one contact's number, checking "find all phones" on an account record tells Clay to look up every contact tied to that account and enrich phone numbers for the whole group at once.
This is one of the more common templates for lead enrichment precisely because it is boring.
Reps don't need to understand Clay's interface end-to-end. They can simply check a box, and the data will show up where they already work.
Template 3: Find Decision Makers on Demand
A close cousin of the phone lookup workflow, this one solves a different problem: finding the right people inside an account, not just enriching people already in the CRM.
The trigger can be anything that signals renewed interest in an account: a CRM field flip, a re-engagement score crossing a threshold, or a manual checkbox similar to the phone lookup pattern.
Once triggered, the workflow will:
Send a webhook to Clay with the target account.
Search for people at that account matching a defined persona (title, department, seniority).
Find email addresses for the matches.
Create new contact records in the CRM and associates each one with the account.
This template removes a task that otherwise eats a meaningful chunk of a rep's week: manually searching LinkedIn for the right person at an account, one contact at a time.
Trigger it once, and the contacts show up already linked to the right account record.
Template 4: Find Lookalikes After a Closed Deal
This is one of the more requested Clay workflow examples for enrichment and lead routing, mostly because it turns a single win into a prospecting list without anyone lifting a finger.
The trigger is simple: a deal gets marked closed won. From there:
A webhook fires to Clay with the details of the company that just closed.
Clay finds a set of lookalike companies (typically ten), matched on firmographic and technographic similarity to the account that just converted.
Clay finds decision makers at each lookalike company.
Phone numbers and emails get enriched for those decision makers.
All of it gets written into the CRM as new account and contact records.
The rep who just closed the deal gets notified that a batch of similar accounts, complete with contacts, phone numbers, and emails, is sitting ready to prospect into.
The idea is simple: a fresh win carries momentum, and that momentum is worth more the same week than 3 months later.
This exact pattern shows up across our GTM case studies, since a closed deal is one of the most reliable triggers a workflow can use.
Template 5: Website Visitor Signal Routing
Website visits are one of the highest-intent signals a company generates, and most of that signal gets wasted because nobody is watching for it in real time.
This workflow starts with a deanonymization step that identifies the person or company visiting the site. From there, the path splits depending on whether that visitor already exists in the CRM.
If the visitor is new:
Enrich the person and their company.
Score and tier the account.
If it scores as tier 1, notify the sales rep immediately.
Clean and create the records inside the CRM automatically.
If the visitor already exists in the CRM:
Check whether they are an active customer. If so, notify the account manager or customer success rep.
Check whether there is an open opportunity tied to this contact. If so, notify the rep working that deal, especially if the visit included the pricing page.
If the contact is a new, unworked lead, notify the SDR responsible for that segment.
This is a genuinely useful entry point into signal-based outbound, since a website visit is closer to real intent than almost any other trigger available.
Signal-based outbound lead generation strategies like this one tend to outperform list-based sequencing.
Field Mappings Behind Every Template
Every template above depends on the same underlying discipline: clean field mappings between Clay and the CRM.
Before any of these workflows run reliably, you need to decide, field by field, how Clay should treat each one:
Overwrite: Clay's value replaces whatever is in the CRM, every sync.
Write only if empty: Clay fills the field only if it is currently blank.
Never write: Clay enriches the field for scoring purposes, but the value never syncs to the CRM.
Get this wrong on the job change workflow, and a manually confirmed employment note gets silently erased. Similarly, if you get it wrong on the decision maker workflow, it’s almost certain that duplicate contact records start piling up.
Clay field mappings are not a one-time setup step. They need revisiting every time a new template gets added, since a field that was safe to overwrite in one workflow might carry manually entered notes in another. Getting these Clay field mappings right the first time saves a rebuild later.
The provider layer matters here too. Every workflow above depends on accurate underlying data, and that comes down to which data enrichment tools sit behind the Clay table doing the actual lookups.
For workflows leaning on email specifically, like the decision maker and lookalike templates, the accuracy of your email enrichment tools inside that waterfall determines whether the contacts you create are actually reachable.
Once the data and mappings are solid, writing scores and enrichment back into the CRM is its own step. If you are running any of this through HubSpot, the setup to connect HubSpot to Clay follows the same overwrite logic described above.
When a sync that used to work suddenly stops updating records, that is almost always a mapping issue rather than a Clay problem.
It is worth checking whether your Clay HubSpot integration is working or not before assuming the whole workflow needs a rebuild.
Common Clay AI Triggers and Rules
Across all 5 templates, the best triggers are event-based; since event-based workflows produce systems people actually trust:
CRM field flips: A checkbox or dropdown change on a record, used for the phone lookup and decision maker templates.
Deal stage changes: Specifically, a deal moving to closed won, used for the lookalike template.
Scheduled re-checks: A recurring job that re-verifies data, used for the job change workflow.
External events: A website visit captured through deanonymization, used for the visitor signal template.
The rule worth remembering across all of them: a trigger should fire on something that already happened, not something you are guessing might happen.
Guessed triggers produce noisy workflows that fire constantly and get ignored. The best Clay AI triggers rules are event-based, since event-based workflows produce systems people actually trust.
Clay Use Cases Across Enrichment, Routing, and Scoring
Pulling the five templates together, the pattern across most working Clay platform use cases and examples looks like this:
Enrichment use cases:
Filling missing LinkedIn URLs, phone numbers, and emails
Backfilling firmographic and technographic data on accounts
Routing use cases:
Sending flagged job changes to the right rep based on account tier
Notifying account managers, CS, or sales reps based on who visited the website
Scoring use cases:
Tiering new website visitors before deciding whether to alert a rep
Comparing lookalike companies against the profile of a company that already converted
These 3 categories cover most of what people search for in Clay use cases across enrichment, routing, and scoring, and the templates in this guide touch all three at once.
Everything You Need to Know About Clay Workflow Templates
Category | Key Considerations |
What Are Clay Workflow Templates? | Reusable Clay automations with field mappings, triggers, and CRM writeback already built in |
Core Templates You Can Use | Job change tracking, phone lookups, decision maker finding, lookalike prospecting, website visitor routing |
Who Needs Them? | RevOps leads, GTM engineers, and sales teams tired of building the same enrichment logic repeatedly |
Biggest Risk | Field mapping mistakes: wrong overwrite rules erase manual data or create duplicate records |
Cost Control | Route classification through cheaper tools where possible, not every task needs a Clay credit |
Trigger Design | Use events that already happened (deal closed, field flipped) instead of guessed conditions |
Build Custom Clay Workflows with The GTM Engineering Company
The GTM Engineering Company builds workflows like these, the same way for our clients, combining field mapping logic, trigger rules and CRM write-back.
Every workflow ships with a written SOP and Loom walkthrough, so a client's team can see exactly how it works and extend it themselves.
On a single build, we processed nearly 18,000 leads for a mere $38, by routing classification through OpenAI instead of Clay credits alone. It is one of the several ways we save Clay credits on high-volume runs.
To know more about how we can help you build similar Clay workflows and manage your GTM efforts end-to-end, request a 30-day audit now.
FAQs About Clay Workflow Templates
What are Clay workflow templates?
Clay workflow templates are reusable automations inside Clay that handle a specific task, like tracking job changes or finding decision makers, with field mappings and CRM writeback rules already built in. They save teams from rebuilding the same enrichment logic every time. The best ones include clear rules for when Clay should overwrite CRM data. Templates without writeback logic are only half a workflow.
What should I consider when choosing which Clay workflow templates to build first?
You should consider which manual task costs your team the most hours right now, not which workflow sounds the most advanced. Job change tracking and website visitor routing tend to deliver the fastest value, since both catch real-time signals reps would otherwise miss. Field mapping discipline matters more than complexity, since a simple workflow with clean mappings beats a complex one with broken sync rules.
How does The GTM Engineering Company differ from a typical Clay template library?
The GTM Engineering Company builds these workflows as production infrastructure inside a client's own CRM, not as a downloadable file behind a signup form. Every workflow ships with a written SOP and a Loom walkthrough so the client's team can extend it. Cost engineering is built in, including routing classification through cheaper tools instead of Clay credits alone. Nothing is ever gated.
How do I get started building Clay workflow templates for my team?
Getting started begins with identifying which manual task is costing your team the most hours, then mapping the CRM fields that workflow depends on. A 30-day audit produces a documented punch list, a working enrichment table, and one operational signal already being live in your CRM. Most teams get their first template, usually job change tracking or phone lookups, running within 2 to 3 weeks.
How long does it take to build a working Clay workflow template?
A single, well-scoped Clay workflow template like a phone lookup or decision maker finder typically takes 1 to 2 weeks from field mapping to live CRM writeback. More complex templates, like the job change workflow with its tier-check logic, usually take 2 to 3 weeks. Full production stability, meaning the template survives edge cases like bad LinkedIn matches, takes another few weeks.
Why do Clay workflow templates break after working fine for weeks?
These workflows usually break because a field mapping rule was set wrong, not because the automation logic failed. A field set to overwrite when it should have been write-only-if-empty erases manually entered CRM data. API rate limits or a broken CRM sync can also silently stop a template from updating records. Reviewing the overwrite rules on every synced field is usually the fastest fix.
Can Clay workflow templates work without a CRM integration?
These templates can technically run and enrich data without writing anything back to a CRM, but the value drops sharply once that happens. Enrichment sitting inside a Clay table nobody outside the workflow sees does not change what a rep does that day. The templates in this guide all depend on CRM writeback, whether a stamped confirmation, a new contact record, or a rep notification.
Isn't building custom Clay workflows overkill when Clay already has pre-built templates in its library?
Clay's own pre-built templates work well for simple, single-step enrichment tasks, but most real GTM workflows need conditional logic a generic template does not cover. The job change workflow here checks account tier before deciding whether to route or suppress a contact, specific to your priorities. Custom templates cost more upfront but match how your team actually sells.
