Skip to content
Back to Systems Lab

Enrichment + orchestration

Clay ICP enrichment workflow

A job-search workflow connecting an ICP audience, person enrichment, an email waterfall, and job-change signals.

Tested draft

Tested on ten records. The enrichment workflow remains in draft while data exceptions and email writeback are reviewed.

My role
Audience selection, workflow configuration, and data review
Tools & methods
Clay Audiences · Person enrichment · Work Email Waterfall

Purpose

I built this workflow as part of a Clay cohort assignment. The audience focuses on Marketing and Revenue Operations leaders at target technology companies, with the goal of supporting more informed and timely professional outreach.

I also added a job-change signal with weekly monitoring. A new role can provide useful context for a conversation; it still needs to be evaluated before deciding to reach out.

How it works

Person enrichment uses a LinkedIn URL to retrieve professional context and employer information. Those fields then supply the Work Email Waterfall. The intended final step writes the reviewed email result back to the Audience.

Enrichment workflow

  1. Audience member added

    Start with a person in the job-search ICP segment.

  2. Enrich person

    Use the LinkedIn URL to retrieve role and employer context.

  3. Work Email Waterfall

    Pass the person and employer information to email providers.

  4. Write to Audiences

    Map the email output back to the Audience's Email field.

Configured workflow in draft. Email writeback and unresolved records need review before activation. Job-change monitoring is a separate audience signal.

What the test showed

The initial ten-record test completed on four records. Six failed because Company Name was missing. The field mapping pointed to the company associated with a certification rather than the current employer.

I corrected Company Name to use the Org field from person enrichment. After rerunning the test, nine records completed and returned email addresses. I also mapped the Work Email output to the Audience's Email field.

Review of the returned data found two exceptions: one record still lacked a company domain, and another returned an email domain that differed from the employer input. Completed enrichment runs still require a check that the result belongs to the intended person and employer.

Before activation

The next step is to resolve or exclude those exceptions, add a company-domain fallback, and verify email writeback on a reviewed record. The small test is useful evidence of a configuration fix; it does not establish the accuracy of a full outreach audience.

Discuss a GTM systems project