Learn and master Clay with Clay university

Enriching an audience segment now builds a Clay Workflow instead of a bulk enrichment table, with a guided four-step builder sitting on top of it.

This experience is in Beta. The legacy path is still available as Create enrichment table. If you have never built a bulk enrichment, the workflow path is the only one you'll see.

🧱 Why Enrichment Moved to Workflows

Bulk enrich had three specific problems:

1. You couldn't choose your test rows. You got the first ten records, so your edge cases stayed hidden until you had already run the whole segment through the enrichment.
2. You couldn't trace a record. When one came back empty, there was no way to see which step dropped it.
3. Adding a step meant paying again. Add a column and every single record re-ran, so you paid for all of them a second time.

🚪 Opening the Enrichment Builder

We're starting inside a people audience, a segment of records who live in New York City with "sales" somewhere in their title.

1. Open the segment and click Enrich, then hit the + in the Enrichments panel.
2. Choose Create enrichment workflow. The other option, Create enrichment table, is the bulk enrichment you already know, and it is still there.
3. Click View workflow to drop into the builder.

Two things are already true when the builder opens. There are four steps across the top: Source, Enrich segment, Map fields, and Review & run.

Clay starts the build for you with three nodes: a segment trigger, a Lookup company, and an Enrich segment.

🗂️ Step One: Source

Your segment is already selected here, because that is where you came from.

Open the list anyway. These are checkboxes, so one workflow can enrich several segments at once. Select two more and all three get enriched by the same workflow you are building.

Build the enrichment once, then point it at every segment that needs it, instead of rebuilding the same chain per audience.

➕ Step Two: Enrich Segment

This is where you pick what you're adding, using the same provider search you already use elsewhere in Clay. We'll start with one provider, Enrich person, so the pieces are easy to see.

The inputs arrive already filled in. Clay reads the segment and wires them up for you. If you rewire something and want Clay's suggestion back, click Suggest input mappings and it runs again. Those suggestions are right about 90% of the time, so usually the only thing left to do is save.

Save and test on 10 rows.

🧪 The Test Table

The test table opens at the bottom. This is unable with bulk enrich.

From here you control both what you test on and what you re-run:

• Add data lets you pick specific records out of the segment and add them to the test. Go find the difficult ones: the person with no LinkedIn URL, the one at a company nobody can resolve. Adding three of those takes this test from 10 rows to 13.
• Close the test table with the button in its corner, then bring it back any time by clicking Test data. The records you chose are still there.
• Re-run at three levels. Run a whole column again from its header, re-run specific rows, or click a single cell and re-run just that one. It behaves very much like the Clay Tables.

Now add the rest of the chain, Find work email and then Find mobile number. The input mappings fill themselves in each time. Save and test again, now across all 13 rows.

You are seeing what works and what breaks on 13 records you picked, rather than finding out after you have paid to run the entire segment.

🗺️ Step Three: Map Fields

Step three decides which workflow outputs get written back onto your segment fields. Clay does most of the work for you.

1. Accept the best-guess matches. Clay has already paired outputs to existing fields. Title, location, and URL match cleanly, so confirm them one at a time or use Confirm all.
2. Trash the ones that are wrong. A match you don't want goes away with the trash icon.
3. Create a field for anything with nowhere to land. Outputs that don't map cleanly get Add Field, where you name the new field yourself. A date of birth output becomes DOB or birthday, whichever you prefer.
4. Set Ignore blank values. This keeps whatever is already on the record when the workflow comes back empty, so a blank result never wipes out good data you already have.

A summary of the field mappings sits at the bottom of the step, with the write-back options below it. Next stays disabled until every mapping is resolved, and clearing it automatically adds the Upsert segment record node to the workflow, which writes your data back into Audiences.

🚦 Step Four: Review and Run

Review and run is the pre-flight. It shows you:

• The credit cost, per enrichment and as a total. This build comes to about five and a half credits per run.
• The enrichments you're running. Four here: Lookup company, Enrich person, Find work email, and Find mobile number.
• Your source and your destination. The segment being written back to is the one selected at the start, with the other two removed.
• The mapped fields, nine of them in this build.

Below that, Manage runs holds the two settings:

• Auto-enrich new records enriches records as they join the segment, in the background.
• Recurring enrichments re-runs the whole thing on a schedule.

Then open Run, which gives you three choices, each with its own estimate:

• Publish puts the workflow live without running it.
• Publish and run publishes and immediately runs the full segment, all 588 records.
• Test runs a smaller batch, the 13 rows we've been working with.

A draft never fires. The status flips from Draft to Live only when you publish, so a workflow you tested but never published is doing nothing.

📊 Reading the Runs Tab

The Runs tab shows the total number of runs completed, the number that failed, what they cost, and how long they took. Beyond those totals:

• Switch to table view for a Clay Table style view of the same data.
• Filter by status, by workflow version, and by trigger, and set the timeframe to one day, one week, or one month.
• Open a single record and you see exactly what the workflow did for it, including which step it failed on.

⚙️ Run Conditions

Every enrichment node has a Run if panel. Describe in plain English when that step should run and Clay adds the condition for you. You can also configure it by hand, setting specific rules, using AI to write them, or dropping into code.

For more detail on how Workflows themselves work, see the Workflows documentation.

🚀 What's Next

You can now build an enrichment across a segment as a Workflow, test it on records you picked yourself, watch it break where it was always going to break, map the results back onto your audience, and publish it so it runs across everything.