LinkedIn Newsletter Scraper: Keyword to Newsletters

🏆 Part of The Mine Works' 149-actor portfolio · 40,000+ runs · 200,000+ results delivered across our full distribution stack · 99.9%+ success rate

💰 $3.00 / 1,000 results.

⚡ Keyword in, every public LinkedIn newsletter matching it out: title, link and search snippet. No login, no API key.

💸 A search that returns nothing is never charged.

Give it a keyword or topic and get back matching public LinkedIn newsletters: title, URL and a snippet from how it's indexed. No login, no API key.

Why this doesn't promise subscriber counts or full issue text

A subscriber-count tier was built and tested against a real newsletter page before this actor shipped, and removed after that test: the fetched page, 94KB of real HTML, contained the word "subscriber" zero times in any form. LinkedIn renders that number with client-side JavaScript rather than serving it in the page a plain HTTP request receives, so a tier promising it could only ever return null while implying it sometimes worked. The same is true of full issue text. Rather than ship a field that quietly never populates, this actor is scoped to what it can actually deliver every time: the title, URL and snippet a public search surfaces for a newsletter, which comes from the search result itself and doesn't depend on LinkedIn's own page rendering at all.

Input

• query (required): a keyword, topic or brand name, e.g. "artificial intelligence".
• maxResults: caps how many newsletters come back. Default 10, maximum 50.
• monitorMode: turns this into a standing watch (see below).

Example output

{
  "url": "https://www.linkedin.com/newsletters/artificial-intelligence-6598352935271358464/",
  "title": "Artificial Intelligence",
  "snippet": "The most important artificial intelligence and machine learning news and articles.",
  "checked_at": "2026-08-30T00:00:00.000Z"
}

Turning a keyword into a standing watch

A brand or research team tracking a topic on LinkedIn doesn't want the same newsletter list re-delivered and re-billed every time it checks in. Set Monitor mode to true, save the run as an Apify Task, then add it to an Apify Schedule with the same query each time. Every run after the first returns only newsletters not delivered in a previous run.

Weekly or monthly is the right cadence here. New LinkedIn newsletters on a given topic don't appear fast enough to justify anything more frequent, and because monitor mode only returns what it hasn't seen before, a scheduled rerun that finds nothing new costs nothing.

Who this is for

Content and partnerships teams looking for newsletters to sponsor or guest-write for within a topic. Competitive research into who is publishing on LinkedIn around a subject. Anyone building a directory or monitoring feed of LinkedIn newsletter activity in a niche.

Frequently asked questions

Does this return subscriber counts or engagement numbers? No. That data is rendered client-side on LinkedIn's own newsletter pages and is not present in a plain fetch of them, so this actor does not claim to deliver it rather than return a field that would always be empty.

Does this need a LinkedIn login? No. It performs a public search and reads what is publicly indexed; it never logs into LinkedIn.

Why did a search return fewer newsletters than maxResults? A narrow or unusual topic may simply not have that many active newsletters indexed. The run log states how many were found.

Can I get the full text of each newsletter issue? No, for the same reason subscriber counts aren't included: that content is not present in a plain fetch of LinkedIn's own pages, and this actor only ships fields it can reliably deliver.

Does a search with zero matches cost anything? No. A search that returns nothing never fires the newsletter-found event.

Can I use this to build a directory of newsletters in my niche? Yes. Repeated keyword queries build up a structured list you own and control.

Use from Claude, ChatGPT & any MCP agent

Hosted MCP endpoint, no install, OAuth on first connect:

https://mcp.apify.com/?tools=themineworks/linkedin-newsletter-scraper

Claude Desktop / Cursor config (token auth):

{
  "mcpServers": {
    "linkedin-newsletter-scraper": {
      "url": "https://mcp.apify.com/?tools=themineworks/linkedin-newsletter-scraper",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Ask your agent: "Find LinkedIn newsletters about [topic] with an active following, so I can pitch a guest post."

Pricing

Event	Price	You pay when
Newsletter found	$0.003	A newsletter is delivered to your dataset

Flat pricing, not tiered by Apify plan, and no separate Actor Start charge. Pay per newsletter delivered. A search that returns nothing is never charged.

Related actors

Two that pair naturally with this one when the newsletter is a pitch target rather than the end goal: themineworks/domain-to-linkedin-resolver takes a company domain and finds its LinkedIn presence, and themineworks/linkedin-email-finder finds a contact email from a LinkedIn profile.

Keywords: LinkedIn newsletter scraper, LinkedIn newsletter discovery, LinkedIn content sourcing tool, LinkedIn newsletter directory, LinkedIn topic monitoring, LinkedIn newsletter API alternative