Integrating Proxies with n8n and Make for No-Code Automation

Last updated: April 2026 | Author: Hex Proxies Team

No-code and low-code automation platforms have democratized web scraping and data collection. Teams that previously needed dedicated developers to build scraping infrastructure can now create sophisticated data workflows with visual tools. But these workflows hit the same IP blocking and geo-restriction challenges that code-based scrapers face.

Proxies solve these challenges for no-code workflows just as they do for traditional scraping. The integration approach differs by platform — n8n offers more flexibility through its self-hosted architecture, while Make provides cloud-based convenience with some proxy configuration limitations. This guide covers both.

n8n Proxy Integration

Why n8n Works Well with Proxies

n8n is an open-source, self-hosted automation platform. Because you control the server environment, you have full control over proxy configuration. This makes n8n the preferred choice for proxy-powered automation:

• Self-hosted: Configure environment-level proxy settings that apply to all HTTP requests
• HTTP Request node: Supports explicit proxy configuration per request
• Code node: Write custom JavaScript for advanced proxy rotation logic
• No IP restrictions: Your self-hosted instance can route through any proxy provider

Method 1: HTTP Request Node with Proxy

The simplest approach uses n8n's HTTP Request node with proxy settings:

{
  "nodes": [
    {
      "name": "Fetch Product Page",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "url": "https://www.example.com/product/12345",
        "options": {
          "proxy": "http://USER-country-us:PASS@gate.hexproxies.com:8080",
          "timeout": 30000
        },
        "method": "GET",
        "responseFormat": "text"
      }
    }
  ]
}

Method 2: Environment-Level Proxy Configuration

For n8n instances where all requests should route through proxies, set environment variables:

# n8n Docker environment configuration
HTTP_PROXY=http://USER-country-us:PASS@gate.hexproxies.com:8080
HTTPS_PROXY=http://USER-country-us:PASS@gate.hexproxies.com:8080
NO_PROXY=localhost,127.0.0.1,internal-api.company.com

With Docker Compose:

# docker-compose.yml for n8n with proxy
version: "3.8"
services:
  n8n:
    image: n8nio/n8n
    ports:
      - "5678:5678"
    environment:
      - HTTP_PROXY=http://USER-country-us:PASS@gate.hexproxies.com:8080
      - HTTPS_PROXY=http://USER-country-us:PASS@gate.hexproxies.com:8080
      - NO_PROXY=localhost,127.0.0.1
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=your-secure-password
    volumes:
      - n8n_data:/home/node/.n8n

volumes:
  n8n_data:

Method 3: Code Node for Dynamic Proxy Routing

For workflows that need different proxies for different requests (geo-targeted collection), use n8n's Code node:

// n8n Code Node — Dynamic proxy selection
const countries = ['us', 'gb', 'de', 'fr', 'jp'];
const results = [];

for (const country of countries) {
  const proxyUrl = `http://USER-country-${country}:PASS@gate.hexproxies.com:8080`;
  
  const response = await this.helpers.httpRequest({
    url: 'https://www.example.com/pricing',
    method: 'GET',
    proxy: proxyUrl,
    timeout: 30000,
    returnFullResponse: true
  });
  
  results.push({
    json: {
      country: country,
      statusCode: response.statusCode,
      body: response.body,
      collectedAt: new Date().toISOString()
    }
  });
  
  // Rate limiting between requests
  await new Promise(resolve => setTimeout(resolve, 3000));
}

return results;

Make (Integromat) Proxy Integration

Make's Proxy Limitations

Make is a cloud-hosted platform, which means you do not control the server environment. Direct proxy configuration is more limited than n8n, but there are effective workarounds:

• HTTP module: Supports proxy configuration in advanced settings
• Webhooks: Can trigger proxy-powered external services
• Custom functions: JavaScript functions for request manipulation

Method 1: HTTP Module with Proxy Settings

Make's HTTP module supports proxy configuration. In the module settings:

1. Add an HTTP "Make a request" module to your scenario
2. Configure the URL of your target page
3. Under "Advanced Settings" or "Show advanced settings," find the proxy field
4. Enter: http://USER-country-us:PASS@gate.hexproxies.com:8080
5. Set an appropriate timeout (15-30 seconds)

Method 2: Proxy Middleware Service

For more control, deploy a lightweight proxy middleware that Make calls via webhook:

// Express.js middleware for Make webhook integration
const express = require('express');
const { HttpsProxyAgent } = require('https-proxy-agent');
const fetch = require('node-fetch');

const app = express();
app.use(express.json());

app.post('/proxy-fetch', async (req, res) => {
  const { url, country = 'us', headers = {} } = req.body;
  
  const proxyUrl = (
    `http://USER-country-${country}:PASS@gate.hexproxies.com:8080`
  );
  const agent = new HttpsProxyAgent(proxyUrl);
  
  try {
    const response = await fetch(url, {
      agent,
      headers: {
        'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64)',
        ...headers
      },
      timeout: 30000
    });
    
    const body = await response.text();
    res.json({
      success: true,
      statusCode: response.status,
      body: body,
      country: country
    });
  } catch (error) {
    res.status(500).json({
      success: false,
      error: error.message
    });
  }
});

app.listen(3000, () => console.log('Proxy middleware on :3000'));

Then in Make, use an HTTP module to call your middleware endpoint, passing the target URL and country as JSON body parameters.

Practical Workflow Examples

Workflow 1: Automated Price Monitoring

Monitor competitor prices daily and alert your team when prices change:

Workflow 2: Multi-Market SEO Rank Tracking

Track search rankings from different countries using geo-targeted proxies:

Trigger: Weekly schedule
  ↓
Loop: For each country (us, gb, de, fr, jp)
  ↓
  HTTP Request: Search Google via country-specific proxy
    Proxy: http://USER-country-{country}:PASS@gate.hexproxies.com:8080
  ↓
  Extract: Parse SERP position for target keywords
  ↓
  Store: Write results to database/spreadsheet
  ↓
  Wait: 5 seconds (rate limiting)
  ↓
End Loop
  ↓
Report: Generate weekly ranking report
  ↓
Email: Send to marketing team

Workflow 3: Lead Enrichment Pipeline

Enrich a list of company leads with publicly available data:

1. Input: CSV/Google Sheet with company names and domains
2. Proxy fetch: Visit each company's website through residential proxy
3. Extract: Company description, team size, technology stack, social links
4. Enrich: Cross-reference with LinkedIn, Crunchbase (through proxy)
5. Output: Enriched lead data back to CRM or spreadsheet

Rate Limiting in No-Code Workflows

No-code platforms make it easy to create workflows that send requests too fast. Implement rate limiting to protect both your proxy reputation and your target sites:

n8n Rate Limiting

• Use the Wait node between HTTP requests (3-5 seconds for most sites)
• Set the workflow to process items one at a time (not parallel) in the workflow settings
• Use the SplitInBatches node to process URLs in small groups with waits between batches

Make Rate Limiting

• Use the Sleep module between HTTP requests
• Set scenario execution to "Sequential" in scenario settings
• Configure the HTTP module timeout to avoid piling up requests on slow targets

Cost Comparison: No-Code vs Custom Code

For teams collecting under 100 GB/month through proxies, the no-code approach is often more cost-effective when you factor in developer time. The proxy costs are identical — the difference is in development and maintenance overhead.

Choosing Between n8n and Make for Proxy Workflows

For proxy-intensive workflows, n8n's self-hosted model provides the best experience. You control the proxy configuration at every level and avoid cloud platform restrictions. Visit our residential proxy page for gateway details.

Security Considerations

• Credential storage: Store proxy credentials in n8n's credential manager or Make's connection settings — never hardcode in workflow JSON
• Environment variables: For self-hosted n8n, use environment variables for proxy credentials
• Access control: Restrict workflow editing permissions to prevent credential exposure
• Logging: Ensure workflow logs do not capture proxy credentials in plain text

Frequently Asked Questions

Can I use Hex Proxies with Zapier?

Zapier's HTTP module has limited proxy support compared to n8n and Make. For Zapier-based workflows, use the proxy middleware approach — deploy a lightweight API that Zapier calls via webhook, and the middleware routes requests through Hex Proxies. This adds a small amount of complexity but works reliably.

How much bandwidth do typical no-code scraping workflows consume?

Most no-code workflows scrape text-heavy pages (product listings, search results, articles). A typical page is 200-500 KB. Scraping 1,000 pages per day consumes approximately 200-500 MB, or about $0.34-$0.85/day at $1.70/GB residential proxy rates. Even aggressive daily monitoring of 10,000 pages stays under $10/day in proxy costs. Visit our pricing page for current rates.

Do I need a different proxy for each workflow?

No. You can use the same Hex Proxies credentials across all your workflows. Each request through the residential gateway at gate.hexproxies.com:8080 automatically gets a fresh IP unless you specify a sticky session. For workflows that need separate sessions, add different -sessid- parameters to the proxy username.

What happens when a proxy request fails in my workflow?

Both n8n and Make support error handling. In n8n, add an error trigger or use the "On Error" settings on the HTTP Request node to retry with a different proxy session. In Make, use the error handler module to catch failures and route to a retry path. Set retry count to 2-3 with a 5-second delay between attempts.

Can I use ISP proxies with no-code platforms?

Yes. ISP proxies at $0.83/IP work identically to residential proxies in terms of HTTP proxy protocol — configure the ISP proxy IP and port in the same proxy field. ISP proxies are ideal for no-code workflows that target the same sites repeatedly (daily price checks, weekly rank tracking) because the stable IP builds reputation with the target site. See our ISP proxy page for details.