Urgent.News

What's breaking now, across thousands of outlets.

Tech

Extracting B2B Churn & Regulatory Leads Without Headless Browsers (~100MB RAM + MCP)

Spinning up Playwright or Puppeteer for every scraping pipeline gets expensive fast, especially when running usage-based jobs for Clay, n8n, or Model Context Protocol (MCP) agents. A single Chromium container easily eats 1–2 GB of RAM before parsing a single record. Over the past few days, I built two pure-HTTP extractors targeting high-intent B2B verticals where headless browsers turned out to…

Extracting B2B churn and regulatory leads without headless browsers can be done using pure HTTP methods. This approach is more efficient in terms of RAM usage and eliminates the need for Chromium containers.

Two specific extractors have been developed targeting high-intent B2B verticals: Xero App Store churn data and detained overseas shipments in U.S. FDA OASIS Import Refusal Reports.

For the Xero App Store, the server embeds the entire Redux state in the HTML response. By making a single fetch() call, you can retrieve data such as developer support information, trial duration, review counts, and more. Appending query parameters to the app's reviews URL allows for filtering reviews server-side. This method enabled the extraction of low-star reviews for 1,100+ reviews on seven popular Xero integrations.

For FDA port detentions, instead of automating browser interactions, POST requests can be made directly to specific URLs. This retrieves structured data such as Manufacturer FEI, address, entry/DOC/line, lab flags, and FD&C Act violation sections. This approach allows for querying the data via MCP schemas, enabling AI agents and GTM workflows to access the information without browser overhead.

Both extractors are available in the Apify Store with native MCP schemas, making them easily integrable into various workflows. To ensure smooth publication validation, it is recommended to include an explicit output schema in the actor's configuration.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Faceless Video Automation in n8n: Outline, Costs, Limits

Faceless video automation in n8n means chaining nodes so an idea goes in one end and a narrated video comes out the other: a trigger, an LLM for the script, a text to speech call, an image step and a…

  • Faceless video automation in n8n involves chained nodes for idea-to-narrated-video workflow
  • Services include LLM, voice, image source, and renderer nodes for video creation
  • Costs are time and upkeep due to service accounts, API changes, and rate limits

One Rust Patch, Two Workloads: Catching Regressions with CodSpeed

You’re reviewing a Rust pull request that changes how a batch job counts unique event IDs. The tests pass, and on the first benchmark the patch uses about 24% fewer instructions than the original…

  • Rust patch replaces BTreeSet with small Vec, reducing instructions by 24%
  • Patch incurs 3.28x more instruction references with unique IDs benchmark
  • Lab tests patch on two batches: 2,048 IDs each, one with repeats, one unique

More from Friday 20 November →