Skip to main content

SimplyNode × Figranium Integration

SimplyNode is a residential and mobile proxy provider for high-volume, geo-sensitive, and detection-sensitive connections. Figranium can import SimplyNode proxy lists directly and use them as rotating pools in browser automation workflows.

50M+

Residential IPs across SimplyNode’s network.

1.4M+

Mobile IPs for stricter detection environments.

185+ countries

GEO targeting across countries, regions, cities, and ISPs.
Purchased SimplyNode traffic does not expire, which makes it useful for irregular or bursty Figranium workloads that may sit idle between scheduled runs.

How SimplyNode integrates with Figranium

Figranium workflows run through a browser engine that may need a clean, rotating, or sticky IP depending on the task. SimplyNode provides the proxy layer, while Figranium handles importing, storing, and selecting proxies for browser runs. Because Figranium supports native proxy import, HTTP/SOCKS5 connections, credentials, and round-robin or random rotation, you can generate a SimplyNode proxy pool, import it once, and manage it from Figranium instead of maintaining individual proxy entries by hand.

Common use cases

Data extraction

Use a fresh IP for high-volume scraping jobs where IP consistency is not required.

Price & change monitoring

Rotate IPs across scheduled runs to reduce repeated rate-limiting and fingerprint patterns.

Lead enrichment

Target traffic by country, region, city, or ISP for region-specific public data collection.

QA & regression testing

Keep a sticky IP throughout multi-step flows so a session does not change networks mid-run.
You can also split traffic into separate SimplyNode proxy profiles by project, GEO, platform, or Figranium workflow so usage and billing remain easy to track.

Choose a traffic type

Residential traffic — from $2.25/GB at scaleIPs from residential ISPs, suited to general-purpose scraping, automation, and platforms with moderate detection.
Start with residential traffic for general automation. If the target platform consistently flags residential IPs, mobile is the stronger fallback.

Set up SimplyNode

Before connecting SimplyNode to Figranium, create an account, purchase traffic, and configure a proxy profile.
1

Purchase traffic

Buy the amount of GB you need. Purchased traffic is added to your Remaining Traffic balance and is not tied to a single profile yet.
2

Create a Proxy Profile

From the SimplyNode dashboard, click Add Proxy Profile and allocate traffic from your main balance.Give the profile a descriptive name, such as Figranium — Scraping, Figranium — QA, or a GEO-specific label like US or DE.
3

Open the Proxy List Generator

Open the new profile to configure GEO, rotation, session behavior, and proxy format.

Configure SimplyNode for Figranium

1

Configure the proxy list

In SimplyNode’s Proxy List Generator, configure the GEO, rotation, session, and other settings for your workflow.Select HTTP, HTTPS, or SOCKS5 from the format dropdown instead of using a custom format.
  • For scraping or extraction where you want frequent IP changes, use new IP for each request.
  • For QA flows or multi-step sessions, use a sticky session with a fixed session ID. The same session ID returns the same IP; a new session ID returns a new one.
2

Download the proxy list

Download the generated proxy list from SimplyNode as a TXT file.
3

Import it into Figranium

In Figranium, go to Settings > Proxies and import the TXT file.The generated SimplyNode proxy will appear in your proxy list.
4

Mark it as a rotating pool

Find the imported proxy, click Edit, enable Rotating Pool, then click Save.This tells Figranium that the proxy represents a pool of changing IP addresses rather than one fixed endpoint.
Your SimplyNode proxy is now ready to use in Figranium workflows. Figranium can select from the pool according to your configured proxy behavior while SimplyNode handles the underlying IP rotation or sticky session.

Try SimplyNode

Create a SimplyNode account

Set up residential or mobile traffic and connect the generated proxy pool to Figranium.