Using n8n as a lightweight Clay alternative for lead enrichment

Questions
1

I’m building a stripped-down Clay alternative for enriching leads using n8n.

The workflow starts with a list of business names or domains. I use HTTP Request or Brave Search to pull website or company data, then run extraction steps to find emails, phone numbers, LinkedIn URLs, etc. I also validate emails and store everything in a database or Google Sheet.

The problem: I want to avoid my VPS IP being blacklisted while scraping. I only want to route specific nodes (HTTP Request, MCP Brave Search) through a residential proxy—not the whole instance.

I tried applying a proxy at the Docker level, but it broke auth callbacks and affected unrelated workflows.

Has anyone done selective proxy routing per node in n8n? Or found a clean workaround?

Any ideas appreciated.

2

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.