Repository navigation
ai agent lead list
A lead list is rows of public information about organizations worth contacting: company name, sector, a public contact page, and one fact worth citing in an outreach email. A browser agent reads company pages, directories and exhibitor lists the way a person would and writes those rows down, if you tell it exactly what counts as a lead and what to skip.
A "lead" here is an organization, not a person: a company, a nonprofit, an exhibitor, a vendor in a directory. The list is a small number of facts about each one, gathered from pages the organization itself published to be read: an about page, a directory listing, a press page. The point is arriving at a conversation with something specific to say, not harvesting an inbox at scale.
If the task is closer to open-ended research, comparing sources or summarizing a debate, that is covered on AI agents for web research; a lead list is narrower: the same handful of fields, repeated across many organizations.
Four fields carry the whole list, and each earns its place:
- Company name and sector. The two facts that let you sort the list, sector read from the directory or exhibitor category, not your own guess.
- A public contact page URL, not a person's inbox. The company's own about or contact page, the address it published for this purpose, not an individual's email pulled from a page never built as a directory.
- One fact worth citing. A specific detail on the page: a product line, a stated focus, a location. It turns a template into something that reads like it was written for that one company, and it is the one field a template cannot fake.
- The source URL and the date read. Company pages change; a row without its source cannot be re-checked when something looks wrong, and a stale row is worse than none.
Three lines, and each is a different kind of risk:
- Personal data harvested at scale is a different job, and a legal one. An individual's name, personal email or phone number, collected in bulk, is personal data under rules like the EU's GDPR, and unsolicited commercial email is regulated too, under rules like the US's CAN-SPAM Act. Neither is explained here, and this is not legal advice: check what applies to your case before building a list of people rather than organizations.
- Anything behind a login you were not given stays off limits, same as any automated access: an agent typing credentials it was not handed is not something this page instructs.
- Anything a site's terms forbid stays forbidden regardless of the tool. Directories often publish their own rules on bulk collection; read them before pointing an agent at the page.
Rows come from pages an organization already published to be read: a
company's own about or contact page, a business directory, a conference's
exhibitor list. Typed into uvx invisible-playwright-mcp ui, or handed to your assistant with
invisible_playwright_mcp's browser attached:
Go to
<the exhibitor list page>. For each exhibitor, open its entry and its own site if linked. Collect: company name, sector as the directory states it, a public contact or about page URL, and one specific fact worth mentioning in an email. Skip any exhibitor with no public site. Do not collect names or emails of individual people. Output one CSV row per company: name, sector, contact_url, fact, source_url, date_checked.
Bound a run the same way: a few dozen exhibitors in one session reads reliably; a directory of thousands is a slower, different task. The mechanics of clean CSV output belong to extracting data to a CSV with an AI agent.
A model can misread a directory's category, invent a "fact" that sounds plausible but is not on the page, or grab the wrong company's site when two names are similar. Spot-check a sample of rows against the live page before using the list for anything.
A paraphrased fact that turns out wrong in an actual email is worse than no fact at all. Re-open each contact URL once more before you send anything, since a page can change between the run and the message.
The structural version of that discipline is a source URL and a read-or-inferred flag beside every field, which turns spot-checking from a sample into a lookup: filling a CRM record from a company's website sets out the fields a company site reliably carries and the three it does not.
Once the list exists as CSV, landing it in a spreadsheet is a separate, smaller task: paste the rows in, or import the file directly. The mechanics, and where a spreadsheet's own import functions beat asking an agent to do the pasting, are covered in getting website data into Google Sheets with an AI agent.
Treat a directory or exhibitor page the same as any repeated traffic: a few dozen rows in one sitting reads like a person working through a list, and a script that revisits the same directory every few minutes reads like something else.
Bound the run by count, not by time, run it once rather than on a loop, and stop at the first sign the site is pushing back rather than retrying immediately. A one-off build for an upcoming event rarely needs repeating at all.
Can an AI agent build a lead list for me? Yes, for organizations rather than individuals: it can read company pages, directories and exhibitor lists and write out a name, sector, a contact page and one usable fact per row, if you tell it exactly which fields count.
Is it legal to scrape company data for lead generation? It depends what you collect and where you operate. Company-level facts carry lower risk than personal data about named individuals, and rules like the EU's GDPR and the US's CAN-SPAM Act exist around exactly that; this is not legal advice, so check what applies to your case.
Should the agent collect names and emails of individual people? Treat that as a separate, higher-risk task this page does not cover. A company-level list carries a different, lower risk profile than harvesting named individuals' personal emails at scale.
How do I check the list is accurate before using it? Spot-check a sample of rows against the live page, the way you would proof any generated dataset. The "one fact worth citing" field is most likely to be paraphrased wrong, and the one your reader notices first.
How many companies can I collect in one run? Bound it like any agent extraction: a few dozen rows in one session reads reliably, hundreds is a slower run with more chances of a dropped or duplicated row, covered generally on the CSV extraction page.
See also: AI agents for web research, extracting data to a CSV with an AI agent, and getting website data into Google Sheets with an AI agent.
Retrieved 2026-09-05.
-
invisible_playwright_mcp README, for the
uvx invisible-playwright-mcp uiinterface and the MCP path for assistants that can already run tools.
From the invisible_playwright_mcp wiki. The agent reads the public page; deciding who to email, and what to promise them, is still yours.
- OpenAI Operator alternatives
- Open-source Operator-style agents
- Is OpenAI Operator still available?
- OpenAI Operator vs Claude computer use
- browser-use alternatives
- Choosing an AI browser agent
- Open-source AI browser agents
- Open-source computer-use agents
- What is an AI web agent?
- AI browser agents vs traditional scraping
- Cloud browser infrastructure for AI agents, explained
- Browserbase alternatives
- Firecrawl vs an AI browser agent
- Skyvern alternatives
- Stagehand vs browser-use
- Project Mariner is gone: what replaced it
- Manus alternatives
- Gemini computer use vs Claude computer use
- A stealth browser MCP, reviewed honestly by its own wiki
- AI browser vs AI browser agent: which one do you want?
- AI browser agent vs RPA: which one fits the job
- AI browser agent vs n8n, Zapier and Make
- Vercel agent-browser alternatives, compared honestly
- What is an agentic browser? Definition and the two kinds
- Open-source agentic browsers: the three layers, compared
- Choosing an MCP server for browser automation: four axes
- Stealth MCP servers compared: Camoufox, nodriver, Patchright
- Playwright MCP alternatives, and the three you don't need
- Autonomous browser agents: the four rungs of autonomy
- What is actually free in the AI browser agent stack
- browser-use on GitHub: what the repo actually gives you
- Playwright MCP vs Chrome DevTools MCP: different jobs
- How to choose among MCP servers: a map by category
- Which MCP servers are worth adding to Claude Code
- MCP on GitHub: finding servers and judging them fast
- MCP vs an API: the decision, and what the wrapper costs
- MCP alternatives: when the protocol is the wrong shape
- Why does my AI agent get blocked?
- The timing signal AI agents give off
- Agent retry loops trip rate limits, not fingerprints
- Claude computer use detected as a bot
- browser-use getting blocked: what you can and cannot change
- Playwright MCP session blocked: four causes, four fixes
- Playwright MCP and captchas: what actually gets you past
- Cloudflare and a browser MCP server: what is being read
- Can an AI agent solve a captcha? The honest answer
- Getting an AI agent to fill out forms
- The best model for an MCP browser agent, and what it really costs
- Browser problem or model problem?
- How to use a Playwright MCP server with Claude Code
- Extracting data to a CSV with an AI agent
- Monitoring a page for changes with an AI agent
- How to let Claude Desktop control a browser
- How to add a browser to Cursor as an MCP server
- Using an AI agent to hunt for apartments
- Getting website data into Google Sheets with an AI agent
- Using an AI agent to download invoices from portals
- AI agents for web research
- Using an AI agent to test your own website
- How to add a browser to Cline as an MCP server
- Posting to social media with an AI agent
- Posting to Facebook with an AI agent
- Posting to Instagram with an AI agent
- Posting to X with an AI agent
- Automating LinkedIn posts: read this first
- Appointment bots: what they are and what an agent can legitimately do
- Track prices across sites with an AI agent
- Build a lead list with an AI browser agent
- Run an AI browser agent on a schedule
- AI browser agent with a local LLM: what changes
- Should you log your AI agent into your accounts?
- How to write a task an AI browser agent can follow
- Move data between two web apps with an AI agent
- The MCP server
- How the tools are shaped, and why
- Playwright MCP vs the Playwright CLI: which fits when
- Playwright MCP: browser is already in use, and the fix
- Playwright MCP best practices: four decisions that matter
- Playwright MCP with a proxy, and the three leaks it leaves
- A browser MCP server in GitHub Copilot: setup and limits
- Using a browser MCP server for web scraping: the pattern
- Which LLM for browser automation: the four properties
- How to build a browser agent, and what to take instead
- Getting an AI agent to log into a website: three routes
- MCP tools, resources and prompts: who controls each
- How many MCP tools is too many? The context arithmetic
- How to build an MCP server: the decisions, not the scaffold
- Local or remote MCP server: what changes, and what does not
- Writing an MCP client in Python: the thirty-line version
- Self-hosted AI agent: what one actually costs to run
- How long an AI browser agent takes per step, measured
- Text, HTML, snapshot or screenshot: what the agent should read
- Giving an AI browser agent a stopping condition
- Keeping an AI browser agent out of destructive actions
- Why did the AI agent click the wrong thing
- When the page changes under the AI agent
- Running one AI agent task across a list of sites
- Seeing a page as it appears in another country
- Getting data out of a dashboard with no export button
- Two browsers in one session: main and support
- Finding the dead links on a site with an AI agent
- Filling a CRM record from a company's website
- One form submission per spreadsheet row, with an AI agent
- Dated screenshots of a page as evidence
- Checking order and delivery status with an AI agent
- Reading a PDF that opens inside the browser
- Summarising a long page or thread with an AI agent
- Collecting every image on a page with its caption
- Collecting event and course listings with an AI agent
- Cancelling a subscription with an AI agent
- What an AI agent can and cannot do inside an iframe
- Shadow DOM and an AI agent: you can click it, you cannot read it
- How to add a browser to Codex as an MCP server
- What a page snapshot costs, per control
- How to let Gemini CLI use a browser
- Native selects and the ones that only look like selects
- Clicking by selector or by coordinates
- How long the agent waits before it gives up
- What a second browser costs
- Uploading a file with an AI agent, and why this one cannot
- Watching the agent work, and when it is worth it
- When not to use an AI browser agent
- Agent or script: deciding once instead of every time
- Using the keyboard instead of the mouse
- Secrets in an agent task: where they end up
- What an agent run should log
- Deduplicating what an AI agent collects
- Normalising values across sites
- Validating an AI agent's output
- Reading a table with an AI agent
- Driving a site's own search and filters
- The task works headed and fails headless
- How to let the AdaL CLI use a browser