Can I use NodeMaven proxies with Apify?

Yes. NodeMaven proxies can be used with Apify Actors that support custom proxies. In the Actor’s Input tab: Open Proxy and browser configuration. Select Own proxies. Add the NodeMaven proxy as a complete connection URL. Use this format: http://USERNAME:PASSWORD@gate.nodemaven.com:8080

Which NodeMaven proxy type is best for Apify?

The best proxy type depends on the target website and scraping workflow: Residential proxies: A versatile choice for general web scraping, location targeting, price monitoring, and market research. Mobile proxies: Suitable for mobile-first websites and targets with stricter IP reputation requirements. ISP proxies: Best for long-running workflows that need a fast, stable IP and a consistent online identity. Residential proxies are generally a practical starting point for most Apify scraping projects.

Should I use rotating or sticky sessions?

Choose the session type based on how the target website handles visitors: Rotating sessions: Use different IPs across requests. They are useful for large-scale data collection and workflows that benefit from IP diversity. Sticky sessions: Keep the same IP for a longer period. They are useful for logins, cookies, shopping carts, multi-step processes, and browser sessions that require a consistent identity. Configure the session type in NodeMaven Proxy Setup before copying the generated proxy credentials. Check our guide on proxy rotation.

How do I check that the NodeMaven proxy works?

Run Web Scraper with the example website used in this guide: https://books.toscrape.com/ After the run finishes: Open the run details. Check the status and logs. Open the Dataset or Output. Confirm that Apify successfully processed the website and returned data. A completed run without a proxy connection or authentication error indicates that Apify accepted the NodeMaven proxy configuration.

Why does the proxy return a 407 error?

An HTTP 407 error means that proxy authentication failed. Check the following: The complete NodeMaven username was entered. The proxy password is correct. The HTTP proxy uses the correct port. The URL starts with http://. Reserved characters in the credentials are URL-encoded. There are no extra spaces in the proxy URL. If the error continues, generate the proxy again in the NodeMaven dashboard and replace the existing URL in Apify.

Why use NodeMaven proxies with Apify?

NodeMaven gives Apify users access to: Residential, mobile, and ISP proxies Rotating and sticky sessions Country, region, city, and ISP targeting where available HTTP and SOCKS5 support IP Quality Filter settings A single gateway with configurable proxy usernames These options make it easier to adapt the proxy configuration to different Actors, target websites, locations, and session requirements.

Apify Proxy Integration: Easy Proxy Set Up Guide

What is Apify?

Apify is a cloud platform for web scraping, browser automation, and data extraction. Its Store includes ready-made Actors for common scraping tasks, while developers can also build and run custom Actors with JavaScript or Python.

Many Apify Actors support custom HTTP and SOCKS5 proxies. Connecting NodeMaven lets you route requests through residential, mobile, or ISP IPs, control the proxy location, and use rotating or sticky sessions based on the needs of your scraping workflow

Step 1

Generate a proxy in NodeMaven

Proxy type: Residential, Mobile, or ISP
Location: Select a country, region, city, or ISP when available
Session: Choose Rotating for IP rotation or Sticky when the same IP should persist
Filtering: Select the IP quality option that fits your workflow
Protocol: HTTP

For this guide, select HTTP. Apify Web Scraper also supports custom SOCKS5 proxy URLs.

Tip: You can start testing our proxies with quality guarantee with a $3.50 trial.

Step 2

Copy your NodeMaven proxy credentials

Copy the complete proxy details generated in the dashboard:

Host: gate.nodemaven.com
Port: 8080, or the HTTP port shown in your dashboard
Username: Your complete generated NodeMaven proxy username
Password: Your NodeMaven proxy password

Important: Do not shorten or edit the generated username. It can contain the selected location, session, and IP filter settings.

Step 3

Open the Actors section in Apify

The Actors section gives you two options:

Choose an existing Actor from Apify Store
Create your own Actor

For this guide, choose an existing Actor from the Store.

Step 4

Choose Web Scraper from Apify Store

Search the Store for Web Scraper and select the Actor maintained by Apify.

The Web Scraper page opens directly on the Input tab. You do not need to open this tab separately.

Step 5

Add the example website

Under Basic configuration, find the Start URLs field and enter:

https://books.toscrape.com/

We use Books to Scrape only as an example in this guide. It is a sandbox website created specifically for practicing and demonstrating web scraping.

When configuring a real scraping workflow, replace this URL with the website you want to process. Always make sure that you have permission to access and scrape the target website.

Step 6

Open the proxy configuration

Stay on the Input tab and scroll down to Proxy and browser configuration.

Open the section and change the proxy setting to Own proxies. A field for entering custom proxy URLs will appear.

Note: The exact label can vary between Actors. If another Actor does not show an Own proxies option, it may not support custom proxies through its form input.

Step 7

Enter the NodeMaven proxy URL

Add your NodeMaven proxy using the following format:

http://USERNAME:PASSWORD@gate.nodemaven.com:8080

Replace USERNAME and PASSWORD with the complete credentials copied from your NodeMaven dashboard. Keep http:// at the beginning of the URL.

Example:

http://your_generated_username:your_proxy_password@gate.nodemaven.com:8080

If the username or password contains a URL-reserved character—such as @, :, /, #, ?, or %—URL-encode that character before saving the proxy URL.

Step 8

Save and start Web Scraper

Review the configuration and click Save & start in the upper-right corner.

Apify will save the input, launch Web Scraper, and send its requests through the configured NodeMaven proxy.

Open the run details to monitor its status and logs. A successful run should finish without a proxy connection or authentication error.

Step 9

Check the scraping results

After the run finishes, open the Output tab.

A successful setup should show:

A green Succeeded status
One or more results in the dataset
Information extracted from Books to Scrape
No proxy connection or authentication errors

In this example, Apify returns the page title, H1 heading, and source URL from https://books.toscrape.com/.

Your NodeMaven proxy is now successfully connected to Apify.

Residential Proxies

Real residential IPs with rotating and sticky sessions. A strong default for large-scale scraping where broad location coverage and trusted consumer IPs matter

Recommended for:

Instagram TikTok LinkedIn

Buy now

Mobile Proxies

Real 4G, 5G, and LTE connections for mobile-first targets and websites with stricter IP reputation requirements

Recommended for:

TikTok Facebook X (Twitter)

Buy now

ISP proxies

Static residential ISP IPs with stable long sessions, fast speeds, and unlimited bandwidth. Best when an Actor needs to keep the same online identity across repeated runs

Recommended for:

LinkedIn Gmail Pinterest

Buy now

Not sure which proxy type to choose?

Chat with us

An Apify proxy routes an Actor’s web requests through a different IP address instead of sending them directly from the original connection.

Apify offers a built-in proxy service. Actors that support custom proxy configuration can also connect to third-party proxy providers such as NodeMaven through the Own proxies setting

Yes. NodeMaven proxies can be used with Apify Actors that support custom proxies.

In the Actor’s Input tab:

Open Proxy and browser configuration.
Select Own proxies.
Add the NodeMaven proxy as a complete connection URL.

Use this format:

http://USERNAME:PASSWORD@gate.nodemaven.com:8080

Apify Web Scraper supports custom HTTP and SOCKS5 proxy URLs.

Proxy support can vary between Actors. Check the Proxy and browser configuration section in the selected Actor’s Input tab to see which options are available.

For the setup described in this guide, we recommend using a NodeMaven HTTP proxy.

The best proxy type depends on the target website and scraping workflow:

Residential proxies: A versatile choice for general web scraping, location targeting, price monitoring, and market research.
Mobile proxies: Suitable for mobile-first websites and targets with stricter IP reputation requirements.
ISP proxies: Best for long-running workflows that need a fast, stable IP and a consistent online identity.

Residential proxies are generally a practical starting point for most Apify scraping projects.

Choose the session type based on how the target website handles visitors:

Rotating sessions: Use different IPs across requests. They are useful for large-scale data collection and workflows that benefit from IP diversity.
Sticky sessions: Keep the same IP for a longer period. They are useful for logins, cookies, shopping carts, multi-step processes, and browser sessions that require a consistent identity.

Configure the session type in NodeMaven Proxy Setup before copying the generated proxy credentials. Check our guide on proxy rotation.

Use the following format:

http://USERNAME:PASSWORD@gate.nodemaven.com:8080

Replace USERNAME and PASSWORD with the credentials generated in the NodeMaven dashboard.

Important: Copy the complete username. The generated username can contain your location, session, and IP filter settings. Removing part of it can change the proxy configuration or cause authentication to fail.

If your credentials contain reserved characters such as @, :, /, #, ?, or %, URL-encode those characters before adding the proxy URL to Apify.

Run Web Scraper with the example website used in this guide:

https://books.toscrape.com/

After the run finishes:

Open the run details.
Check the status and logs.
Open the Dataset or Output.
Confirm that Apify successfully processed the website and returned data.

A completed run without a proxy connection or authentication error indicates that Apify accepted the NodeMaven proxy configuration.

An HTTP 407 error means that proxy authentication failed.

Check the following:

The complete NodeMaven username was entered.
The proxy password is correct.
The HTTP proxy uses the correct port.
The URL starts with http://.
Reserved characters in the credentials are URL-encoded.
There are no extra spaces in the proxy URL.

If the error continues, generate the proxy again in the NodeMaven dashboard and replace the existing URL in Apify.

Yes, if the selected Actor accepts a list of custom proxy URLs.

Generate the required proxies in NodeMaven and enter each complete URL separately in the Actor’s Own proxies field. Apify can then select URLs from the supplied proxy list.

The exact behavior and input format can vary between Actors, so check the selected Actor’s proxy configuration before adding multiple URLs.

Yes. Developers can pass NodeMaven proxy URLs to the proxy configuration used by a custom JavaScript or Python Actor.

Store the proxy credentials in a secure input, secret, or environment variable. Do not hard-code passwords in public source code or expose them in logs.

NodeMaven gives Apify users access to: