Get a demo
EnrichWorkflow

Know Who's Behind Every Email

Turns personal and work emails into a professional profile with title, company and city.

Takes email addresses and finds who they belong to: full name, job title, company name, professional profile, and city. It even works on personal emails like Gmail with no company domain. When it can't confirm someone's current employer, it leaves the field blank instead of guessing, and it never overwrites data you already have.

About this Skill

When to use it

Use this Skill when you need to identify unknown people from a list of bare email addresses, such as subscribers or signups with mostly personal webmail. It finds each person's LinkedIn profile, current job title, employer, and location, then writes only confirmed details into your Audiences records. Avoid using it for finding work emails or phone numbers, scoring or tiering people, searching for net-new contacts, or cleaning up records that already have data.

What it delivers

Buyers get enriched Audiences records with a found LinkedIn URL, name, title, employer, and location, plus a linked company record keyed on website domain. Fields are left blank rather than filled with an unconfirmed guess, so downstream segmentation stays reliable.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

Enrich my new subscriber list using just their email addresses: find their LinkedIn profile, current title, employer, and location, and link them to a company record.

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • 01Trigger & source fields
    • Pick the Audiences segment that triggers enrichment when a new person joins it
    • tell it which fields hold email, name, and company (if any).
  • 02Output field mapping
    • Choose which person fields receive the found name, title, company, website, LinkedIn URL and source, and location
    • unmapped fields are never written.
  • 03Company record settingsDecide whether to create or update a linked company record for each resolved website.
  • 04Matching thresholds
    • Set how many days after a role ends before it's treated as outdated (default 365)
    • set the minimum confidence score for accepting a web-search LinkedIn match (default 70).
  • 05Domain exclusion lists
    • Review and edit the list of masked-relay email domains to skip before any paid step
    • review the list of placeholder domains never accepted as a company website.
  • 06LLM account & backfill budget
    • Connect the account the AI steps run on, if your workspace requires one
    • set a credit spend ceiling before running the optional backfill on existing people.

Outputs

  • 01Enriched person recordEach person record carries a confirmed LinkedIn URL, name, title, employer, website, and location, and leaves blanks where nothing was confirmed, ready for your Audiences segment.

Representative output

Enriched person record

EmailLinkedIn URLLinkedIn sourceNameTitleCompanyCompany websiteCityCountry
ana@gmail.comlinkedin.com/in/ana-exampleContactOutAna ExampleHead of GrowthNorthwindnorthwind.comAustinUnited States
j.doe@contoso.comlinkedin.com/in/jdoe-exampleClaygent (confidence 82/100)Jo Doe— withheld: role ended——LeedsUnited Kingdom
k.lee@gmail.com——Kim Lee—————

A dash means nothing was confirmed and nothing was written. That is the design, not a failure.

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

01
Check setup and connections

Checks sign-in to the Clay CLI, workflow tool availability, and Audiences access, then names the exact fix and stops if anything fails.

Step
02
Confirm tool pricing and inputs

Checks the current Clay action catalogue for each enrichment step's real inputs and credit cost before building anything.

Step
03
Build the enrichment workflow

Assembles the full node graph that normalizes names, finds LinkedIn profiles through a waterfall of sources, enriches the person, and resolves their current employer.

Agent
04
Validate the workflow graph

Checks every connection, condition, and data mapping in the draft workflow before testing it.

Step
05
Test on real sample records

Runs the draft workflow on 10 real people with empty fields plus one with an existing title, then stops and waits for you to review what each record found.

Step
06
Review cost and approve launch

Presents the test results, the measured cost per person, and exactly which fields it will write, then stops and waits for your approval to publish and turn on the trigger.

Step
07
Backfill existing people (optional)

Lets you re-run already-enrolled people through the published workflow in batches, stopping at your approved spend ceiling and asking before each further batch. The run stops and waits for spend approval before continuing.

Step

Connections required

No connections listed.

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 1From submitted SKILL.mdCurrent

Related Skills

Related searches