superagnt_
// offer letter // teammate
ready to start immediately

LinkedIn Hiring Lead Enricher — emails verified + buying committee inferred

Takes the partial hiring contacts a scraper produces and turns them into a sequenceable pipeline: verified emails for every lead, plus inferred buying committees for the hiring companies where LinkedIn returned no hiring team. Hourly cron. Pair upstream with a hiring-signal scraper, downstream with a sequencer.

Lead APIsLinkedIn
Claim this hireno questions · deploys on claim
01// what they own

The outcomes on their scorecard

Verified emails, one credit per lead

people_email_finder waterfalls Hunter → Prospeo → LeadMagic on a single call. people_email_verifier gates on `deliverable`. You pay one credit per lead instead of stacking 3 vendor subscriptions.

Buying committee from a single company name

When a job post has no hiring team, people_search finds C-suite, VPs, directors, and founders in sales / marketing / BD at the company. Each is classified by title — only decision_maker and function_owner roles get inserted.

Hourly drain, bounded runs

Up to 50 leads in Job A + 10 job_posts in Job B per run. Atomic claim (UPDATE to in_progress) means concurrent runs never double-process. Predictable cost per hour.

No external pushes — clean handoff

This agent writes to the workspace DB only. The downstream sequencer (e.g. gtm-email-sequencer) picks up verified rows. Separation of concerns: enrichment and activation are different agents.

02// the motion

How the work gets done

Hiring scrapers produce contacts that are almost-but-not-quite ready for outreach: profile URLs without verified emails, and a non-trivial fraction of job posts where LinkedIn's Get_Hiring_Team returns empty. This agent closes both gaps in one hourly run. Job A drains pending_enrichment leads through a multi-provider email-finder waterfall (Hunter → Prospeo → LeadMagic via the agntdata orchestrator), then verifies each email and tags the row as verified / risky / invalid. Job B handles orphaned hiring companies: for every job_post stuck in 'no_hiring_team_found', it runs people_search with seniority + department filters, classifies each result by title (decision_maker / function_owner / recruiter / other), and inserts qualifying stakeholders as new pending_enrichment leads — which Job A picks up on the next run. The buying committee is reconstructed from the ground up. Output is two state changes: lead rows go from pending_enrichment to verified; orphaned job_posts move to hiring_team_inferred. Pair with `linkedin-hiring-signal-scraper` upstream and `gtm-email-sequencer` downstream for the full motion.

The bridge between a scraper and a sequencer. Scrapers produce profile URLs without emails, and a chunk of job posts where the hiring team is hidden. This agent finishes both: a multi-vendor email waterfall on the pending leads, plus a people_search-driven inference of buying committees for orphaned jobs. By the time the data lands in the sequencer, every lead has a verified email and every hiring company has at least one decision_maker or function_owner contact.

click a node to inspect
Hourly: Job A enriches pending leads, Job B infers buying committees for orphaned jobs.
03// the roster

Your new teammate

01agent

LinkedIn Hiring Lead Enricher

Hourly scheduled agent that drains pending_enrichment leads from hiring_leads with a verified email waterfall (Job A), and infers buying committees for job_posts where LinkedIn returned no hiring team (Job B). Pairs upstream with a hiring-signal scraper, downstream with an outbound sequencer. Does NOT push externally — handoff is via DB state.

1 schedule
04// built on

What it runs on

This hire is assembled from the public toolkit. Every piece below is a tool your own agents can call too.

05// onboarding

How setup works

  1. 01

    Claim the hire

    One click. No questionnaire. The brief is already written from your business, and you can edit it before you build if you want to.

  2. 02

    Your hire deploys itself

    Agents, tools, schedules, memory, hand-off queues and the database schema are provisioned into your workspace automatically, then the first real run fires while you watch.

  3. 03

    Hand it the keys it still needs

    You land in chat with your hire and its findings. Anything it still needs is asked for conversationally, whenever you want.

06// related

Other hires that pair well

» build it yourself

Every hire is assembled from the same toolkit.

Same data sources, same database, same memory, schedules and queues. Point your own agent at the MCP endpoint and wire it your way instead.

Wire your own agent