LinkedIn Outreach Tools: Build a Verified List First

Turn a list of LinkedIn profiles into a checked outreach list, in one prompt. Paste this into your agent:

Set up https://monid.ai/SKILL.md, and then use Monid to look up the current job title and company for each LinkedIn profile URL on my list, verify the email address next to it, and give me a table of the people who are still in role and have a deliverable address.

One prompt cleans a list before you send. 1 min setup · 3-6 hrs saved.

You are picking LinkedIn outreach tools, and every list of them ranks the senders: the apps that schedule connection requests and follow-ups. What they rarely cover is the step that decides whether a campaign works, which is who you send to. This guide separates the two, shows how to build a checked prospect list from your agent (we ran the calls live on 2026-10-16), and lists the traps in the output. The list step runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call. Monid does not send messages.

What is the easiest way to prepare LinkedIn outreach from an agent?

Monid. Install it once, add a key, and your agent looks up each prospect, reads the current role and verifies the email as typed JSON, so the list you hand to a sender is already checked.

• Pay per call. A profile lookup is $0.01 and an email check is $0.01225 (Verified 2026-10-16 on the LinkedIn tools page). Buy calls as you need them: no monthly plan and no minimum top-up. Discovery and inspection are free; only a run bills.
• One install, every tool. The same key and balance call the profile lookup, the verifier and every other tool on Monid, so a new step in your list prep is another call, not another account.
• Lives inside your agent. Install the CLI, add your key, run the prompt above, and the tool is there whenever you build a list, with nothing to keep running. Your agent reads SKILL.md and learns the rest, so setup is about a minute.

Sending stays with a sender of your choice. This route is the data half of the job.

What do LinkedIn outreach tools do, and which part do you still need to supply?

Outreach tools send and schedule; they do not decide who is worth contacting. A sender takes a list, spaces out connection requests and messages, keeps replies in one inbox and tracks who answered. Tools in that category include Swarmhit, HeyReach, Expandi, Dripify, Waalaxy and lemlist. What goes into them is your list, and the quality of that list decides what comes out.

Choosing a sender is a one-off decision and you can change it later. The checked list is the part you rebuild for every campaign, which is why it is worth doing from an agent rather than by hand.

How do you build a verified prospect list before you send?

Run two calls per prospect and keep the rows that pass. A profile lookup returns the person's current role, and an email verifier returns a deliverability verdict. The profile endpoint is /linkedin/profile from the provider ploid; it takes a url and returns one profile. The verifier is /email-verifier from hunterio; it takes an email.

For agents

Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:

set up https://monid.ai/SKILL.md

It learns the whole discover, inspect, run workflow itself. More in the agent quickstart.

For humans

npm install -g @monid-ai/cli
monid keys add -k <your-api-key> -l main

Inspect, then run one

Both endpoints are GET calls, so the input goes in --query:

monid inspect -p ploid -e /linkedin/profile
monid run -p ploid -e /linkedin/profile --query '{"url":"<profile-url>"}' -w
monid run -p hunterio -e /email-verifier --query '{"email":"<email-address>"}' -w

Loop it over your list

Put one profile URL per line in profiles.txt, and write one file per prospect:

mkdir -p out
i=0
while read -r u; do
  i=$((i+1))
  monid run -p ploid -e /linkedin/profile --query "{\"url\":\"$u\"}" -w > "out/profile-$i.json"
done < profiles.txt

Do the same with /email-verifier for each address. Each prospect bills the two calls, which is $0.02225 for both (Verified 2026-10-16). The email verification API guide compares the verifiers on Monid if you want a different one.

Or hand the whole job to an agent

Can you automate LinkedIn outreach yourself with n8n or Python?

Yes, for the list step, and it is the part worth scripting. A workflow tool such as n8n or a short Python script can read a sheet of profile URLs, call the lookup, call the verifier and write the result back. That is a loop of the kind above, and the n8n data layer guide shows how the calls fit into a node.

The sending half is different. Automating messages from your own logged-in account means working against how the platform treats automated activity, and the rules differ between platforms and plans, so read yours before you plan volume. That is a reason to keep data collection off your account: a profile lookup through an endpoint runs nowhere near your seat, and the guide to scraping without getting banned covers that side.

What Monid maintains for you is the fetch and the parsing. You send a URL and get a typed record, so you do not run a browser, rotate sessions or repair a parser when a page changes. What you write is the loop and the rule for who stays on the list.

What does a prospect record look like, and what can you build with it?

A prospect record is a short profile with a current position and a short history. We ran the profile call once on 2026-10-16 on the public profile of a well-known executive, so the fields below are what came back.

The response

{ "publicIdentifier": "<vanity-slug>",
  "fullName": "<name>",
  "headline": "<headline>",
  "summary": "<about text>",
  "location": "<city, region, country>",
  "countryCode": "US",
  "industry": null,
  "followerCount": <number>,
  "connectionCount": 8,
  "currentPosition": { "title": "<title>", "companyName": "<company>",
                       "companyUrl": "https://www.linkedin.com/company/<slug>/",
                       "startsAt": "<year>", "endsAt": "Present", "current": true },
  "positions": [ { "title": "...", "companyName": "...", "startsAt": "2015", "endsAt": "Present", "current": true } ],
  "education": [ { "school": "<school>", "degree": null, "field": null, "startsAt": "1973", "endsAt": "1975" } ],
  "isOpenToWork": false,
  "isPremium": true }

The email check returns a verdict and the reasoning behind it:

{ "status": "valid", "score": 92, "regexp": true, "gibberish": false, "disposable": false,
  "webmail": false, "mx_records": true, "smtp_server": true, "smtp_check": true,
  "accept_all": false, "block": false, "verification": { "date": "2026-10-17", "status": "valid" } }

The profile call returned no email or phone field, so the address comes from your own list or a finder, and the verifier checks it. The Hunter domain search versus email finder post covers how to find one.

What you can build with it

• A still-in-role filter. Compare currentPosition.companyName with the company in your CRM and drop the mismatches before a sender touches them.
• A personal opener. Pull the headline, the current company and how long the person has held the role, and have your agent draft one specific first line for each prospect.
• A priority order. Use the title and startsAt to put recent hires in a senior seat at the top, since new leaders often review their tools.
• A skip list. Mark anyone with isOpenToWork true or a mismatched company so a campaign for buyers does not reach people who are leaving.

What goes wrong when you prepare outreach lists at scale?

Four things show up when you read the output, and all four are from the 2026-10-16 runs.

Why is every position marked current?

Because the position list is a history, and the flag is not reliable on its own. On our profile, all three entries came back with current set to true and endsAt of "Present", including roles that started decades apart. Use currentPosition as the answer to "where do they work now", and treat the list as background.

Why is industry null and connectionCount 8?

Because some fields come back empty or implausible. industry was null and connectionCount was 8 on a profile with tens of millions of followers. Do not filter or score on either. Build rules on currentPosition, headline and location, which were filled in.

Why does a valid email still bounce sometimes?

A verdict of valid with a score of 92 means the checks passed, not a promise. The response separates accept_all, a server that accepts any address, from a confirmed mailbox. Keep accept_all addresses on a separate, smaller send, because a verifier cannot tell you whether a mailbox exists behind them. The bounce rate and spam trap guide explains what to do with the risky tier.

What does a list cost, and how long does it take?

The profile call billed $0.01 and the verification $0.01225, so one prospect is $0.02225 and a hundred is $2.225 (Verified 2026-10-16). The profile call took about 1.5 seconds on the wall clock and the verifier about 1.8 seconds, against a published median of about 6.8 seconds for the profile endpoint. Run several at once if you need the list faster.

Which endpoint should I use for which job?

The first two rows are the ones we ran. The third was inspected and not run, so test it on a few addresses before you give it a batch. For the full set of profile tools, see the LinkedIn tools page.

When is another route a better fit?

You need a sender. Nothing here sends a message. If your goal is a sequence with follow-ups and one inbox for replies, you need a sending tool, and the checked list is its input.

You want a ready-made list. A database seat gives you pre-built lists to search and export. If you need to size a market or pull thousands of contacts at once, that route is quicker than one call per person.

You are writing to a handful of people. For fewer than ten prospects, opening the profiles yourself is faster than setting up anything.

And the disclosure: we resell these endpoints. The most useful habit in this guide costs nothing whoever you buy from: check the list before you send, and send to the people who pass.

Conclusion

The best LinkedIn outreach setup is two choices, not one: a sender that fits how you work, and a checked list that goes into it. The list can be built from your agent through Monid for $0.02225 a prospect (Verified 2026-10-16), with one key for every tool, about a minute to set up, and nothing running when you are not using it.

Two things matter more than which sender you pick. First, a campaign that gets silence looks the same whether the message was weak or the list was stale, so check the list first. Second, do not trust a field because it is present: the position flags, industry and connectionCount were all unreliable in our run, while currentPosition and the email verdict were usable.

How we estimated the time saved: checking 100 prospects by hand (open the profile, read the current role, find an address, test it) takes about 2 to 4 minutes each, which is 3 to 6 hours. The 1 minute is the install, key and first call once you already have a Monid key.

Free next step: run monid inspect -p ploid -e /linkedin/profile, then make one call on a profile you know and compare the record with what you see in the browser. Start at monid.ai.

FAQ

Published July 2026.