Skip to main content
Connect LinkedIn so your sequences can send connection requests, messages, and InMail from your own account, and so replies land back in Emanate next to the step that earned them. Find it under Integrations → LinkedIn in the sidebar.
Every rep connects their own LinkedIn account. You don’t need an admin to do it, and connecting yours never gives a teammate access to your inbox or your password.

​
What it unlocks

  • LinkedIn steps in sequences: connection requests, direct messages, and InMail, sent from your account on the schedule your cadence defines.
  • Reply detection: a reply to one of those messages is recorded against the enrollment, notifies you, and can branch or pause the cadence.
  • Late accepts: someone who accepts your invite weeks later still picks up the LinkedIn part of their sequence.
  • LinkedIn as a contact source: your own 1st-degree connections appear in Contacts so you can qualify them and enroll them.
  • Daily digest: accepted connections and LinkedIn replies are included in the Microsoft Teams digest, if your team uses it.

​
Before you start

Signed up with Google and never set a password? Open the LinkedIn sign-in page, enter your email, and choose Forgot password? to set one by email. You only have to do this once: Reset your LinkedIn password.

​
Connect your account

1

Open the LinkedIn tab

Go to Integrations, then open the LinkedIn tab, and choose Connect.
2

Read what you're authorizing

A dialog explains what Emanate will do on your behalf, who handles the sign-in, and LinkedIn’s own position on automation. Nothing happens until you continue.
3

Sign in on the secure page

Choose Continue to LinkedIn. You’re redirected to a page hosted by Unipile, our authentication partner, where you enter your LinkedIn email and password and complete any two-step verification LinkedIn asks for.Your credentials are typed on Unipile’s page. They are never sent to, seen by, or stored by Emanate.
4

Land back in Emanate

You return to Integrations → LinkedIn and your account appears in the table with a Connected badge, your name, and when you connected it. That’s it, sequences can now use LinkedIn steps.

​
Connection status

The table lists every LinkedIn account anyone in your org has connected, including unhealthy ones, so a stalled sequence always has something on screen explaining why. Whenever an account leaves Connected, LinkedIn sending stops for it and the enrollments waiting on it are paused rather than skipped, so nobody is silently dropped mid-cadence.

​
Managing the connection

​
Set your sending limits

Connecting is not the same as sending safely. Open Sequences → Settings → LinkedIn once and set:
  • Daily limits per account: separate caps for connection requests and messages. Premium accounts default to 20 connections and 25 messages a day, Basic to 5 and 25. Setting a cap to 0 pauses that action for the account. The cap belongs to the account, so every sequence using it shares one budget.
  • Connection acceptance wait: how long a sequence waits for an invite to be accepted before it skips that lead’s LinkedIn messages and lets them finish. Default 14 days. An acceptance that arrives later still revives the lane for up to 60 days.
  • Withdraw invitations: auto-withdraw invites left pending after 14, 30, or 60 days to keep your acceptance ratio healthy, or turn it off.

​
Privacy

This is your personal LinkedIn account, so it’s worth being precise about what Emanate can see, what it stores, and for how long.

​
Your password never reaches Emanate

Sign-in happens on Unipile’s hosted page, and Unipile holds the resulting session. Emanate stores no LinkedIn password and cannot read one. The link that starts the flow is signed, single-purpose, and expires 30 minutes after you open it, so it can only ever attach an account to the person and workspace that started the connect.

​
What Emanate does on your behalf

  • Sends connection requests, direct messages, and InMail according to your sequence steps.
  • Reads the replies to those messages so the sequence can advance, pause, or stop.
  • Marks threads as read when you open them inside Emanate.
Every one of those calls is made through Unipile. Emanate never drives your LinkedIn session directly.

​
What is stored, and for how long

​
What Emanate does not do

  • No feed scraping. We don’t read, collect, or store your LinkedIn feed, your profile views, or anyone’s connections but your own.
  • No unrelated conversations. An inbound message that doesn’t match one of your sequence steps is not attached to a contact, not surfaced anywhere in the app, and not stored as a conversation.
  • No posting. Emanate never posts, comments, likes, or endorses as you.
  • No sharing between workspaces. Everything above is scoped to your organization. Another Emanate customer can never see it, and we don’t sell or share it.

​
Who in your organization can see what

Teammates can see that you connected an account, its display name, its status, and a link to your public profile, because a shared cadence needs a visible sender. They cannot read your LinkedIn inbox through Emanate. Replies to a sequence appear on the sequence they belong to, so whoever can see that sequence can see those replies. An admin with the Integrations permission can disconnect your account, but cannot use it to send on their own.

​
Turning it off

Disconnect asks Unipile to end the LinkedIn session and removes the account from Emanate. Sequences stop sending LinkedIn steps from it immediately, and you can reconnect any time. Activity already recorded (replies on a sequence, connections already imported into Contacts) stays in your workspace so your history stays intact, delete those rows or write to support@emanate.ai if you want them removed too.
LinkedIn’s User Agreement prohibits scripts, robots, and automation. Using this integration may put your LinkedIn account at risk of restriction or suspension if your activity exceeds what LinkedIn considers normal use. The limits are applied at LinkedIn’s discretion and are not controlled by Emanate or Unipile. Keep your daily caps conservative, especially in the first weeks on a new account.

​
Troubleshooting

That happens on accounts created with “Sign in with Google”. Go to the LinkedIn sign-in page, enter your email, choose Forgot password?, and set one by email. Then run the connect again.
Complete any two-step verification prompt LinkedIn shows, including an approval in the LinkedIn mobile app. If it still loops, try an incognito window or another browser, and make sure you can sign into LinkedIn normally in that same browser first.
LinkedIn signs sessions out after a password change, a security checkpoint, or unusual activity. Reconnect from the row menu. If it recurs within days, lower your daily limits in Sequences → Settings → LinkedIn before reconnecting again.
Check three things in order: the account’s badge is Connected, its connection-request cap in Sequences → Settings → LinkedIn isn’t set to 0, and today’s cap isn’t already spent. Caps are per account and shared by every sequence using it.
Replies are matched to the message that prompted them. A reply on a thread Emanate never sent to, or from an account that was disconnected when it arrived, won’t match. Reconnect the account and reply manually, the enrollment isn’t lost.
An admin with the Integrations permission can disconnect it from the row menu. That ends the LinkedIn session and stops any sequence step still pointed at it.

​
Next steps

Sequences

Build the cadence your LinkedIn steps run in

Queue and limits

How sending is paced across accounts

Contacts

Work the connections LinkedIn brings in

Integrations overview

All connection types in one place