Connect Your LinkedIn Account
SDRPilot works inside your real LinkedIn account. Connecting it means signing in once through SDRPilot so it can hold a live session for you.
One connected LinkedIn account is called a seat. A seat has its own daily limits, its own dedicated IP address, its own agents and its own inbox. You can run several LinkedIn accounts from one workspace; see Adding another LinkedIn account.
Keeping an account idle
When you add another account you can tick Keep this account idle for now. The account connects and stays signed in, but it sends nothing and joins no agent until you put it to work. We keep checking that it is still signed in, and it still connects to your other LinkedIn accounts. An idle account still counts as a sender, so it is billed like any other.
To start using it, open Settings, find the account and click Put to work: it joins your running agent’s senders, or gets an agent of its own. To pause an account that is working, click Set to idle: it stops all outreach and leaves every agent (an agent with no other account stops too), but it stays signed in. You can switch back at any time. Through the API, send dormant: true when connecting, or PATCH /auth/linkedin/accounts/{id} with { "dormant": false } or { "dormant": true }.
Personal profiles only
SDRPilot connects a personal LinkedIn profile, the one you sign in to with your own email and password. A LinkedIn company or business page cannot be connected: it has no login of its own and cannot send connection requests or messages.
Before you start
Have the email address and password you normally use on LinkedIn ready, and have your phone nearby if your account uses two step verification.
Connecting
- Open Settings, then the LinkedIn accounts tab, and start the connect flow. During onboarding this is step four and looks the same.
- Answer Where do you normally use LinkedIn? SDRPilot guesses it from your browser, so check it before you continue. It decides which country your dedicated IP is bought in.
- SDRPilot sets up the IP address for this seat. That takes a minute or two and you can watch it in the step list.
- On the Email and password tab, enter your LinkedIn email and password. (The other tab, Browser cookies, is the other way in; see Connecting with cookies instead.)
- Optional: add your authenticator app secret if you use an authenticator for LinkedIn. It lets SDRPilot answer a code prompt on its own.
- Optional: tick Remember my password so the seat can sign itself back in if LinkedIn ends the session.
- Continue. SDRPilot signs in, saves the session and shows the account as connected.
Connecting with cookies instead
If the account is already signed in to LinkedIn in a browser, for example an account you rent or manage for someone else, you can connect it with that browser’s LinkedIn cookies. No password and no verification code are needed.
- In the browser where the LinkedIn account is signed in, install the free Cookie-Editor extension (Chrome Web Store; its site links the Edge, Firefox, Safari and Opera versions).
- Open linkedin.com in that browser and check it shows the account you want to connect.
- Click the Cookie-Editor icon in the toolbar (under the puzzle piece if it is not pinned) and allow it to read linkedin.com when it asks.
- Click Export, then JSON. The cookies are copied.
- In the connect flow, open the Browser cookies tab and paste the whole export. A single
li_atvalue is not enough: LinkedIn ends a session that arrives without the rest of its cookies. - Open SDRPilot in that same browser or profile and paste there. In GoLogin or another multi-profile browser, that means opening SDRPilot inside the profile that holds the LinkedIn account, not in your everyday browser. SDRPilot copies the details of the browser you paste from (its browser version, time zone and language), so pasting from a different browser looks to LinkedIn like a new device and it signs the account out.
- Before you connect, close every LinkedIn tab in that browser or profile. Do not sign out of LinkedIn: signing out ends the session you just copied.
- Pick the country and continue as above. SDRPilot checks the session through the seat’s own IP address and shows the account as connected.
Once the account is connected, leave LinkedIn closed in the browser you exported from. The same session used from two places at once is what LinkedIn signs accounts out for. A cookie connect cannot sign itself back in when LinkedIn ends the session, so for an account you want to keep running unattended, signing in with the password and an authenticator secret is the more durable setup.
A connect link for a browser you do not want to sign in from
Step 6 means opening SDRPilot in the browser or profile that holds the LinkedIn session. When that browser is shared, for example a GoLogin or other anti-detect profile that several people use and that saves logins, signing in to SDRPilot there would expose your whole workspace. A connect link avoids that: it opens a page that takes the cookie paste without any sign-in.
- In Settings, on the row of the LinkedIn account that needs signing in, click Get a connect link and copy the link. The link is for that one account and works once, for 30 minutes. It only appears for an account that already exists in your workspace and is signed out; a working account has nothing to connect.
- Open the link inside the browser or profile where the LinkedIn account is signed in, or send it to the person who runs that browser. The page shows the account’s name and the country it runs from, and nothing else about your workspace.
- On that page, follow the Cookie-Editor steps, paste the whole export and close every LinkedIn tab in that browser (without signing out) before you connect. The page copies the details of the browser it is open in, so the account connects as that browser. If the page warns that the browser’s time zone does not match the account’s country, close it and open the link again in the right browser or profile.
- The page shows the sign-in progress and the result. Back in Settings, the account shows as connected.
A link is spent the moment a paste is accepted; a paste the page refuses (for example an export without the li_at cookie) leaves the link usable until it expires. Get a connect link again replaces the previous link for that account, and Cancel link stops it at once, for example when it went to the wrong person. Adding a new account through a link is not possible; the account is added in SDRPilot first, with the fee confirmation, and reconnected through the link when needed.
If the country does not match where you are
SDRPilot can see the time zone your browser reports and the country your connection comes from. When the country you picked disagrees with both, it asks once, before it buys anything. The question names both countries and gives you two answers: use the one it detected, or keep yours.
Keeping yours is a real answer. Agencies connect a client’s account from a different country every day, and that is what the seat should look like.
One thing to know if you keep it: the seat only acts during your working hours, read in your workspace time zone. If those hours fall in the middle of the night in the country you picked, SDRPilot says so on the same screen and offers to move your working hours to that country’s time. An account that only ever acts at 3am where it connects from is the pattern LinkedIn restricts accounts for.
What SDRPilot stores
After a successful sign-in, SDRPilot keeps the session that LinkedIn issued, encrypted. That session is what every later action uses, exactly as your own browser would.
Your password is not stored unless you tick Remember my password. When you do, it is encrypted, used only at sign-in time inside SDRPilot, never shown in the app and never returned by the API. Untick the box, or use Forget saved password on the account row, and it is erased. The same applies to a saved authenticator secret.
When LinkedIn asks you to verify
LinkedIn may challenge a new sign-in in one of these ways. The connect screen tells you which one it is.
- Approve on your phone. The screen says Check Your Phone and waits. Open the LinkedIn app and tap Accept within 2 minutes.
- A code by email or SMS. Enter the code when SDRPilot asks for it.
- A sign-in link by email. Open the email on this LinkedIn account’s inbox and click the link within 2 minutes.
- An authenticator code. If you saved your authenticator secret, SDRPilot handles this without you.
- A security check (a puzzle). SDRPilot cannot solve this for you. Sign in to LinkedIn once in your own browser, complete the check there, then come back and connect again.
This is normal for a first sign-in and does not mean anything is wrong. If a step times out, the screen says so; start the connection again and answer the prompt straight away.
If LinkedIn says “An unexpected error has occurred”
This message comes from LinkedIn’s own sign-in page. It means LinkedIn turned the attempt away before it looked at your password, which happens when it sees several attempts in a short time or a sign-in it did not finish verifying. Your password and your SDRPilot account are fine.
- Wait 15 minutes before trying again. Pressing Try Again immediately is refused the same way.
- If it happens twice, sign in to LinkedIn once on your phone or laptop and answer any verification it shows there.
- Come back to SDRPilot and connect again.
Staying connected
Use check sign-in on the account row whenever you want to confirm the session is still alive. If LinkedIn ends the session, the row says so and offers sign in again.
If you ticked Remember my password, the seat tries once to sign itself back in, after a short delay, with a strict cap on how often it may try in a day. A challenge that needs a person, such as a phone approval with no authenticator secret saved, is never attempted automatically.
More on sessions and IP addresses is in Proxy and Session, and the reasoning behind the pacing is in Keeping Your LinkedIn Account Safe.
Adding another LinkedIn account
- On a SDRPilot plan, first add an extra sender: Settings → Billing → Manage billing, then add a sender to your plan. Your plan includes one sender, so the second account needs one extra sender, the third two, and so on.
- Open Settings, then the LinkedIn accounts tab, and choose Add LinkedIn account.
- The form opens empty, with your connected accounts left exactly as they are. Sign in with the other LinkedIn account, the same way as the first one, with email and password or browser cookies (see Connecting).
If your plan has no free sender left, the card shows Add a sender in Billing instead of the button. Signing an account you already connected back in never needs an extra sender.
If an account you added and paid for has not finished signing in yet, finish it with sign in again on that account (or delete it) before adding another one, so you are not charged twice. Until then the card points you to that account instead of adding a new one.
Each account has its own inbox, its own leads, its own daily limits and its own dedicated IP address. When you already have an agent running, the new account joins that agent’s senders and does everything the first account does: its own searches, profile views and connection requests, within its own limits. Without a running agent, it gets its own agent, created the same way as the first one.
Your LinkedIn accounts also connect to each other on their own. With two or more accounts connected, one sends the other a connection request without a note and the other accepts it, within your active hours. Nothing is sent when the two are already connected or a request between them is already waiting. These requests count toward the daily connection limit and the warm-up, and your own accounts never show up as leads or conversations.
Champions Circle members who sign in with DM Champ skip step 1: there is no sender limit, and each extra account pays its own seat fee in AI credits, as described below.
What a sender costs and how to stop paying
Every plan includes one sender, which is one connected LinkedIn account. You can add more senders to your plan in Settings → Billing → Manage billing; prices are on Plans and Billing. Each sender gets its own dedicated IP address.
To stop using a sender, disconnect the account from its row in Settings. The IP address is released. To stop paying for an extra sender as well, remove it from your plan in the billing portal. Removing an account never deletes your agent; it keeps its other senders, or waits for a new one.
Pausing an agent does not disconnect the account. A paused agent keeps the account connected, so it still counts as a sender.
AI replies and tool calls on LinkedIn conversations are included in your plan.
Champions Circle members who sign in with DM Champ pay per seat instead of a plan. A seat costs 250 AI credits per 30 days, taken from your linked DM Champ balance at the start of each period. The charge covers the dedicated IP address, which is bought 30 days ahead, so it is not refunded when you stop early. Disconnecting the account stops the renewal. If you connect the same account again inside the period you already paid for, nothing is charged; after the period has ended, a new 30 days is charged on reconnect. A paused agent keeps the account connected, so the renewal continues. AI replies and tool calls on LinkedIn conversations do not cost credits: the seat is the only LinkedIn charge. Each account card shows the date it was connected, the date it is paid until (the next 250 credits are due then) and, if it dropped, the date it was disconnected. If a renewal could not be charged because your balance was too low, top up and press Try again or refresh on the account: the renewal is charged right away and the account resumes. To keep renewals from ever running short, turn on auto-recharge in DM Champ under Settings, Billing; a short renewal then recharges once and is charged right away. For a client account that holds seats, its agency keeps it funded: Sub Accounts, Edit, Credit management, Monthly allowance (at least 250 credits per seat), or, when the client buys its own credits, the client turns on auto-recharge in its own Settings, Billing. Low credit alerts are always on.