Reply.io With Multiple LinkedIn Accounts: Setup Guide

    By the NextGen Profiles team4 min read
    On this page

    Reply.io doesn't run LinkedIn actions in your browser. Once an account is connected, its LinkedIn activity runs on the servers of Reply's LinkedIn provider. So the real choice is how the account gets there, and which IP it uses once it does.

    This guide covers the three connection methods and which to use for extra accounts, including rented ones that already have their own dedicated proxy. We confirmed the details with Reply.io's support team in October 2026.

    01

    The Short Answer

    If keeping each account on its own dedicated IP matters to you, connect it with its LinkedIn email and password plus its own proxy. Reply's support team recommends this option when the dedicated IP matters most.

    02

    The Three Ways to Connect

    Reply offers three ways to bring an account in (its step-by-step connection guide covers all three):

    Option 1: cookies through the Findy extension.
    Open the account in its own browser profile and connect it with Reply's Findy Chrome extension (see Reply's article on connecting with a session cookie). This reuses the existing LinkedIn session, but Reply told us the account's actions then go through its provider's shared US proxy, not your own. If you use this route, the browser profile's time zone needs to be a US one to get a US proxy.
    Option 2: email and password plus your own proxy.
    In Reply, connect the account with its LinkedIn login and enter its own proxy. This keeps the account on its dedicated IP. It's a fresh login, so LinkedIn may ask for a verification code.
    Option 3: invite link.
    Reply creates a link that the account's owner opens to log in and authorize the account, so no password changes hands. The owner can also enter the account's own proxy on the same screen. It's built for client or organization accounts you can't log into yourself.

    03

    Step by Step (Option 2)

    For each account:

    Have the account's proxy details ready
    host, port, username and password. Reply's team suggests proxies with username and password authentication.
    In Reply, connect the LinkedIn account
    with its email and password.
    Before clicking Login,
    click Other optional settings, select Use your own proxy under Localization, and enter its domain, port, username, and password.
    Complete the verification code
    if LinkedIn sends one, using the account's inbox or phone.

    04

    Settings That Keep the Account Stable

    A few settings make most of the difference:

    One sticky proxy per account.
    Reply accepts rotating proxies, but its support team told us the provider expects a fixed IP per account and suggested one sticky-session proxy for each.
    Use the account's usual proxy.
    Give Reply the same proxy the account uses in its browser profile, so it never appears from a new location.
    One browser profile per account.
    Reply's help center advises a separate Chrome profile for each account. An anti-detect browser does the same job with a separate fingerprint too (see our anti-detect browser setup guide).

    05

    Common Mistakes

    These are the setups that cause trouble most often:

    Assuming the cookie method keeps your own IP.
    With Findy, actions go through the provider's shared proxy.
    Using a proxy from a different country
    than the account. Keep a US account on a US IP.
    Ramping a new sender too fast.
    Build volume over a few weeks. Our warm-up playbook has the ramp.

    06

    Running More Than One Account

    One LinkedIn account can only send so many connection requests a week (our connection request limits guide has the numbers), so teams that outgrow one profile add senders. If you need more US accounts to run in Reply.io, NextGen Profiles rents real, aged LinkedIn accounts with a dedicated proxy for each one.

    Questions

    FAQ

    Does Reply.io run LinkedIn actions from my browser?

    +

    No. Once connected, the account's LinkedIn actions run on the servers of Reply's LinkedIn provider, whichever connection method you use.

    Which Reply.io connection method keeps a dedicated IP?

    +

    Email and password plus the account's own proxy. The cookie method through Findy reuses the session but routes actions through the provider's shared US proxy.

    Can I use rotating proxies with Reply.io?

    +

    Reply accepts them, but its support team told us the provider expects a fixed IP per account and suggested one sticky-session proxy per account.

    NextGen Profiles

    Need more senders? Rent real LinkedIn accounts.

    $59 a month per account. Try 2 accounts free for 10 days, no card needed.

    Start free trial

    Keep reading

    All articles