How to connect a LinkedIn account through unipile

How to link a LinkedIn account to outreach software through Unipile, what the token does, and how to keep the account healthy after you connect.

Get started

Short answer

Unipile is a third-party provider that holds the LinkedIn session, so the outreach tool never sees your password. You authorize once, the tool gets a token, and you can revoke that token from settings whenever you want.

What unipile does in a LinkedIn connection

Unipile is a third-party provider that sits between your LinkedIn account and whatever tool you're using. When a tool supports it, you sign in to LinkedIn once on Unipile's side, and the tool receives a token instead of your password.

Kinlead connects this way, and so do a number of other outreach tools. The provider holds the session. Your job is to authorize it once and decide what the tool is allowed to do with it.

That last part matters. A token is not a blank check for the tool to do whatever it likes. It's a way for the tool to act as you without holding the thing that would let anyone log in as you from a browser.

If a tool can't tell you how it authenticates to LinkedIn, don't connect your account to it.

Why handing over your LinkedIn password is a bad trade

If a tool asks for your LinkedIn email and password directly, it has to keep them. It needs to log in again tomorrow, and the day after. That copy lives in a database somewhere, protected by whatever security that company happens to have.

A breach of that database hands over your LinkedIn account. If you reused the password, it hands over more than that.

There's a second problem that has nothing to do with breaches. A login from a server address shared by many accounts looks different from a person logging in from a laptop in one city. LinkedIn watches for that pattern, and an account that trips it gets a security check or a restriction.

Password stored by the tool

  • You type your LinkedIn email and password into the tool
  • The tool keeps a copy so it can log in again tomorrow
  • Every action runs from a shared server address
  • A breach or a policy change locks you out of everything at once

Token from a provider

  • You sign in to LinkedIn on the provider's page
  • The provider hands the tool a token, not your password
  • You can revoke the token from settings
  • Changing your LinkedIn password is not the only way out

How the handshake works, step by step

The flow is short. It looks a lot like the 'Log in with Google' button you've clicked on other sites, except the account behind it is LinkedIn.

The token is the part people miss. It's revocable. If you stop using the tool, or you stop trusting it, you disconnect in settings and the token stops working. Your LinkedIn password never changed, and nothing else that uses that password is affected.

  1. 1

    Redirect

    The tool sends you to the provider's authentication page.

  2. 2

    Sign in

    You log in to LinkedIn on that page and complete any verification LinkedIn asks for.

  3. 3

    Token created

    The provider creates a session token tied to your account.

  4. 4

    Token handed over

    The provider shares the token with the tool you're connecting.

  5. 5

    Actions run

    The tool sends messages and reads profiles through the token, never through your password.

Connecting your account without creating a mess

Set aside five minutes and do it on the machine and network you normally use. Signing in from a new country on a VPN, then going back to your usual network an hour later, is the kind of thing that triggers a verification prompt you didn't want.

Have your phone nearby. LinkedIn may ask for a code, and the flow stalls if you have to go hunting for it.

Once you're back in the tool, check the connection before you queue anything. A token that half-worked will fail on your first campaign and you'll spend an afternoon guessing why.

  1. 1

    Open integration settings

    Find the account or connection area in your tool.

  2. 2

    Choose the provider option

    Select Unipile rather than a direct LinkedIn login.

  3. 3

    Authorize

    Sign in to LinkedIn on the provider page and finish any verification.

  4. 4

    Confirm

    Return to the tool and check the account shows as connected.

Paste this job

After you connect, check these before you queue anything:

- The account shows as connected in the tool
- Your LinkedIn profile loads inside the tool
- A test read returns data (inbox or a profile lookup)
- Daily invite and message limits are set
- A send window is set to your working hours
- You know where the disconnect button is

Keeping the account healthy after you connect

The token solves the password problem. It does nothing about behaviour. An account that sends a hundred invites in an hour will get attention whether it authenticated with a password or a token.

LinkedIn doesn't publish exact limits for invites, messages or profile views. Anyone who quotes a number is guessing or repeating someone else's guess. What you can do is watch your own account: how many pending invites sit unanswered, whether your acceptance rate is drifting down, whether LinkedIn has started asking you to verify things it didn't ask before.

Set limits you can live with and leave them alone for a month. Changing them every week gives you no signal about what's actually working.

Session audit

Safety measure
Check active sessions in LinkedIn settings
What to do
Confirms where you're logged in and spots anything you don't recognise

Action limits

Safety measure
Set daily invite and message caps
What to do
Keeps volume inside what your account has handled before

Send windows

Safety measure
Limit activity to your working hours
What to do
Matches the pattern of a person at a desk

Token revocation

Safety measure
Disconnect the provider in settings
What to do
Stops tool access immediately, without touching your password

A connection is permission to act, not permission to act fast.

When the connection drops or LinkedIn pushes back

Tokens expire, passwords change, and sometimes LinkedIn throws a security check in the middle of a session. The tool will show the account as disconnected or throwing errors on actions that worked yesterday.

Stop sending before you reconnect. Reauthorize once, then run a small amount of activity for a few days before going back to your normal volume. If LinkedIn asked you to verify something, finish that in the browser first, because the provider can't do it for you.

  • Pending invites piling up with no acceptances
  • A verification prompt you didn't trigger
  • Failed actions on an account that worked yesterday
  • Messages in your inbox you don't remember sending (change your password now)

What people do

  • Reconnect five times in an hour
  • Raise the daily limit to catch up
  • Switch tools and keep sending at the same volume

What works

  • Reauthorize once, then stop sending for a day
  • Lower limits for a week
  • Clear stale pending invites before adding more

Doing this with Kinlead

Kinlead connects to your LinkedIn account through Unipile, so the password is never stored on Kinlead's side. Outreach runs from your own account, and you can disconnect from settings at any time.

Kinlead sends at most one action every 5 minutes per LinkedIn account, inside daily invite and message limits you set, and inside a send window in the lead's time zone. When LinkedIn pushes back on an account, Kinlead pauses invites on that account and emails you. The details are on the LinkedIn account safety page.

Frequently asked questions

Related

Get started with Kinlead

Prefer markdown? How to connect a LinkedIn account through unipile.md