Clay logo, go to homepage

Search Marketplace

Browse all Skills

Check Employment With Jev

Builds a live Clay workflow that checks whether a contact still works at a company, and in what capacity, by judging their LinkedIn work history with Jev.

About this Skill

When to use it

Use this Skill when you need to know whether a contact still truly works at a company, telling a real job apart from a board seat, advisory tie, side gig, or a stale profile that was never updated. It sets up an always-on workflow that checks every person automatically and writes a clear verdict instead of trusting a single current-job flag. Avoid using it for finding new contacts at a company, finding someone's next job, finding emails or phones, scoring leads, or updating a CRM or sequencer.

What it delivers

Publishes a live Clay workflow that returns a five-value employment verdict, role details, and evidence for every person it checks, so you can trust which contacts have actually left. When run on an Audiences segment it also writes those verdicts onto each person's record, though accuracy still depends on how current their LinkedIn profile is.

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

Can you build something that checks whether our customer contacts still work at their company and flags the ones who've moved on?

Inputs & outputs

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

Inputs

  • 01People source and schedule
    • Choose a Clay table, an Audiences segment, or a webhook as the source
    • for an audience, choose to check people when they join or on a recurring schedule
  • 02Jev provider key
    • Supply a TypeSafe or OpenRouter API key so Jev can judge each role
    • the Skill saves it securely to a local config file, never in chat
  • 03Person and company to match
    • Company name, domain, or LinkedIn page to check against
    • a LinkedIn profile or LinkedIn URL for the person
    • an optional full name to catch a mismatched profile
  • 04Check behavior options
    • Choose whether to skip buying new profiles
    • set how old a saved profile can be before it's refreshed
    • pass a reference ID to match results back to your own records

Outputs

  • 01Per-person verdict tableShows each person's employment status, role type, confidence score, and the evidence sentence behind the call, so you can decide who to act on.
  • 02Person record fieldsWrites the verdict and supporting details onto each Audiences member's record so you can filter or build a saved segment of people who have left.
  • 03Setup summary cardSummarizes what the workflow built, what it cost, and how to trigger it going forward, so you can hand it off or call it from a table, audience, or webhook.

Representative output

What comes back on every person

FieldExample
Active at companypassive — one of yes · passive · no · unsure · not_checked
Relationshipadvisor_or_board — or primary job, side job, investor, honorary, former, no record
Confidence99
EvidenceBoard Member at Northwind Supply since May 2022. Also current: Adatum, CEO
Needs reviewany answer worth a second look; none otherwise
Check statuschecked · no_profile · blocked_missing_input · failed

Five verdicts, not two. "Still there" and "on the board" are different answers, and so is "we couldn't tell."

How the verdict is decided

A LinkedIn profile has no single "current job" — it has a list, and a role nobody closed stays current forever. So the work is split:

StepDone byWhat it does
Find the rolesCodematches on website, LinkedIn page, or company name once "Inc" and "LLC" are dropped
Work out the datesCodeevery start, end and overlap
Judge each roleJevsame company? a job, a contract, a board seat, an investment? still held? the main one?
Combine into a verdictCodeone answer from a fixed set, with a confidence and the evidence in a sentence

Jev is asked one small question per role, never "does this person work here?" — which is how a trustee seat stops making a CEO look like they left. About 4–10¢ per 1,000 people. A person sent with only a LinkedIn URL costs 0.5 Clay credits for the profile.

Six people, checked

PersonAgainstActiveRelationshipConf.Evidence
Dana RuizNorthwind Supplyyesprimary_job100VP Operations since April 2021. Also current: Contoso Robotics advisor, Tailspin Toys investor
Pat QuinnNorthwind Supplyyesside_job79Fractional CFO since March 2024 — there as a contractor, not their main job
Lee ParkNorthwind Supplypassiveadvisor_or_board99Board Member since May 2022. Main job: Adatum, CEO
Sam OkaforFabrikam Freightnoformer84Still listed as current, but replaced by a later full-time job at Litware
Ari MossNorthwind Supplynot_checkedunknown0No profile and no LinkedIn URL to enrich

Sam is the case a "current employer" field gets wrong — the profile still says Fabrikam because nobody closed the role. Dana is the other half: an advisor seat and an angel investment elsewhere don't stop her main job being here. And Ari came back not_checked, never no — nothing to read isn't the same as not there.

On a person record in Audiences

FieldValue
Active at companypassive
Active relationshipadvisor_or_board
Active company checkedNorthwind Supply
Active evidenceBoard Member at Northwind Supply since May 2022. Also current: Adatum, CEO
Active confidence99
Active needs reviewnone
Active last attemptchecked
Active checked at2026-09-29T06:35:20Z

If a later check can't run — the LinkedIn URL was removed, say — only the "last attempt" fields change. The verdict above and its date stay put. A failed check never overwrites a real one.

Once it's live

WorkflowPerson Active At Company (Jev) (published)
Profilesread from your Enrich person column; bought only when a row has just a LinkedIn URL (0.5 credits)
Preview10 of your people — yes 7, passive 1, no 1, unsure 1 · $0.0009
Smoke test11 people through the published workflow; 11 of 11 match the local check

Sending records in

The Skill builds one published workflow. Three things can call it:

A Clay tableadd an action that invokes it; the verdict comes back as that action's result
A Clay audiencepeople are checked as they join, or re-checked on a schedule
Anything that can POSTsend the fields to the workflow's webhook URL

Map your columns onto company_domain, profile, linkedin_url, full_name. Your column names don't need to match.

How the Skill runs

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

01
Explain build, cost, and check setup

The assistant describes what it will build, what it costs, what data leaves your systems, then checks your Clay CLI and Jev key are ready before continuing.

Step
02
Choose where people come from

Pick a Clay table, an Audiences segment, or a webhook as the source, and for an audience choose to check people on join or on a recurring schedule.

Step
03
Connect your Jev key

Provide a TypeSafe or OpenRouter API key; the assistant saves it securely and confirms it works before any checks run.

Step
04
Preview verdicts on sample people

The assistant runs a small preview using your own people, or sample data for a webhook or audience, and stops to ask if the verdicts look right before building anything.

Step
05
Approve the write and spend

The assistant states exactly what it will publish, which fields it will write, and what buying profiles and running Jev will cost, then waits for your go-ahead.

Action
06
Build and publish the workflow

The assistant creates and publishes the workflow, and a second one for an audience if chosen, checking every step before it goes live.

Step
07
Verify the published workflow

The assistant runs test checks through the live workflow and compares results against the local preview to confirm they match before moving on.

Step
08
Deliver and explain how to call it

The assistant hands over the summary card and shows how to trigger the workflow from a table, an audience, or any system that can send a web request.

Step

Connections required

Clay CLI / agent pluginRequired connection
Clay Public APIRequired connection
Jev API (TypeSafe)Required connection

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