SHAI

S9 Outreach

/lead-list-builder

Agent 57/58/59/66: Lead List Builder (S9 Outreach)

Builds a lead list from Instagram (#57), Facebook (#58), LinkedIn (#59), or a general email-marketing dataset (#66) through one of three named data vendors -- Bright Data, Apify, or PhantomBuster -- under that vendor's own terms and the target platform's terms. Captures the exact per-mode filter set (Instagram/Facebook engagement and profile metrics, LinkedIn's Sales Navigator-equivalent criteria run through a vendor dataset since no official search API exists, and any criteria a vendor's dataset exposes for email), then delivers a source-and-date-stamped table. No connector connected -> needs-connector recorded, zero rows, filter spec still delivered.

verified (fixture) 2026-09-08 · needs-connector: brightdatav0.1.0

Run itAll agents

Its status above is the registry's own, with the date of the run that produced it.

What it is for

Contract A

  • #57Instagram lead lists · mode `instagram`; every listed filter; §4.7
  • #58Facebook lead lists · mode `facebook`
  • #59LinkedIn lead lists · mode `linkedin` (Sales Navigator criteria)
  • #66Email lead lists · mode `email`

Example requests

  • find us leads on Instagram
  • build a list of law firm owners on LinkedIn
  • scrape Facebook for gym owners near me
  • build an email list for our outreach
  • lead list builder

What it needs, and what it hands back

Needs connected

Nothing. It runs on what SHAI already knows about you.

Better with: brightdata, apify, phantombuster.

Hands back

  • clients/<business-slug>/leads/<mode>-<date>.md (filter spec + table)
  • the table, returned inline when orchestrated

Stops and asks

Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.

Steps it cannot do through an API, and hands you instead: no data vendor connected -- the filter spec is captured and delivered, but the run stops at zero rows until Bright Data, Apify, or PhantomBuster is connected.

How it runs

These are the headings of its own written instructions — 301 lines you can read and change.

  1. Step 0 — Environment, connector, and profile
  2. Step 1 — Capture the exact filter criteria per mode
  3. Step 2 — Query the connected vendor
  4. Step 3 — Deliver the table
  5. Step 4 — Compliance note (every delivery)

Trades whose playbook recommends it

Life insurance agentsMortgage loan officersMusicians