Urgent.News

What's breaking now, across thousands of outlets.

Tech

How I Built a Zero-Browser B2B Company Enrichment Pipeline in n8n (Replacing 5 Chained APIs)sda

If you build outbound pipelines in n8n , Clay , or Make , you probably know the pain of enriching a list of company domains: Call one tool for emails & socials Call another for tech stack detection Call another for DNS / SPF / DMARC & SSL health Call another to check careers/ATS pages and /pricing Stitch 4–5 mismatched JSON payloads together and pay 4–5x the cost I wanted one lightweight HTTP…

Outbound sales pipelines often struggle with enriching company domain data, requiring multiple separate API calls for email, social media, tech stack, DNS, and other information. This process is time-consuming, expensive, and often requires headless browsers or proxies. The goal was to create a lightweight HTTP-based enrichment pipeline in n8n that required no additional software or heavy resources.

The solution uses pure streaming HTTP requests combined with Cheerio for DOM parsing and Node.js built-in modules like dns/promises and node:tls. By fetching the homepage HTML, live DNS records (MX, SPF, DMARC), and live TLS certificates simultaneously, the system can process domain information in parallel, minimizing overall processing time.

The enrichment tool also automatically discovers and inspects up to five high-signal internal pages (pricing, careers, contact, blog, security) to uncover a company's technology stack. This approach provides a deterministic buying signal score (0-100) along with human-readable outreach hooks. Parsing the company's live DNS TXT record reveals crucial information like CRM, email, and support platforms, even when HTML-based tools are evasive.

Special attention is given to Cloudflare email decoding, which removes obfuscated email addresses and related junk data. The system also checks for the presence of an llms.txt file to determine AI search readiness, audits robots.txt for various AI bots, and validates the freshness of sitemap.xml files.

Sample output from the enrichment pipeline for the domain linear.app includes the company name, buying signal score, tier, specific signals (such as hiring activity and freemium pricing), primary email, email provider, a summary of the tech stack, ATS platform, pricing model, and SSL/DNS/Dmarc status. A free n8n workflow template is available for importing into n8n, allowing users to import a list of domains and receive a structured JSON response ready for outbound outreach.

Additionally, an Apify actor (https://apify.com/kiranvia/b2b-company-intelligence) is available for free use, providing test domain credits and running efficiently at 256 MB of RAM. For AI-powered research assistants like Claude or Cursor, the actor can be integrated via MCP to automate the prospecting research process.

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

Part 30: Identity and governance for agents across five vendors

Part 30 · One Agent, Five Platforms Five platforms means five policy models, unless you design one. Each vendor has its own idea of who an agent is, where its permissions live, what gets logged and…

  • Each vendor has distinct agent identity and permission management methods.
  • Least privilege enforced at gateway level and process API across platforms.

Stop Exporting One Square Image for Every Platform in 2026

The fastest workflow in social media design is one master file. Export a single 1080×1080 square, upload it everywhere, let each platform do the rest.

  • Exporting one 1080x1080 square image for all platforms in 2026 simplifies workflow.
  • Single image maintains control over cropping, avoiding distortion.
  • Tailored exact sizes for each platform prevent cropping or padding issues.

Serialization and Deserialization in Database Engines: How Data Becomes Bytes

When building a database engine from scratch, one of the most important concepts you need to understand is serialization and deserialization .

  • Serialization converts data structures into byte sequences for storage or transmission
  • Deserialization reconstructs original data structures from serialized bytes
  • Database engines rely on serialization/deserialization for persistent data storage

More from Thursday 19 November →