Ciela AI LogoCiela AI
Log in
Docs · Channels

Connect your LinkedIn to Mira.

Mira sends connection requests, opens conversations on accept, and follows up from your real account, not a shared session, that's the only way the messages look like you and the inbox stays yours when replies come back. This page walks you through the cookie-based connect so Mira can act in your voice in about three minutes.

Before you start

Have these three things ready

If any of these are missing the connect step won't make it past the cookie check.

  • A real LinkedIn account in good standing, ideally with a complete profile, a proper photo, and at least a few hundred connections so the platform doesn't flag the activity as a brand-new burner.
  • Chrome, Brave, Edge, or any Chromium browser logged into that account, you'll grab two cookies from devtools in step 2.
  • Roughly five free minutes to copy two strings, no app passwords, no third-party app to install, no LinkedIn admin work.

Walkthrough

01

Open the connect modal

Head to /dashboard/settings, click Connections, scroll to LinkedIn Account, and hit Connect LinkedIn. The modal that opens explains the cookies and waits for you to paste them.

If you're still in onboarding, the same modal opens from the LinkedIn card on Step 4 of the wizard, same fields, same validation.

02

Grab li_at and JSESSIONID

Mira authenticates with two browser cookies, the same ones your own LinkedIn tab uses to stay logged in. You're handing Mira the session, not the password, which is why this doesn't trip LinkedIn's "suspicious login from a new location" signal.

Chrome / Brave / Edge

  1. Open linkedin.com in a tab where you're already logged in.
  2. Right-click anywhere on the page and pick Inspect, then click the Application tab in devtools.
  3. In the left rail expand Cookies and click https://www.linkedin.com.
  4. Find the row named li_at, copy the long Value string. Then find JSESSIONID and copy its Value too, quotes around the value are fine, leave them in.
Safari doesn't expose cookies the same way, the cleanest path on Mac is Chrome for the connect step, then go back to whatever browser you live in. The cookies don't have to come from the browser you use day-to-day, they just have to be valid.
03

Paste and connect

Paste li_at in the first field and JSESSIONID in the second, then hit Connect. Mira opens a Voyager handshake against the cookies, pulls your member ID and email, and saves the session, the whole thing takes about two seconds.

On success the LinkedIn card flips green, your email appears next to the status pill, and the Disconnect button replaces the connect button.

04

Verify in settings

Back on /dashboard/settings, the LinkedIn card should read Connected with your email next to it. Mira will respect LinkedIn's weekly-invite ceiling automatically (around 100 a week, ramped up gradually for new accounts), you don't have to set a daily cap.

If the card still says Disconnected after the modal closes, the cookies were stale, head back to step 2 and grab them again from a freshly-loaded LinkedIn tab.

Common errors

When the connect fails, read this first

Four failure modes cover almost every rejection on this flow.

  • Cookies expired

    li_at rotates whenever you log out or LinkedIn flips a session, the most common cause is you logged out of the source browser between copy and paste. Grab a fresh pair from a tab you're actively logged into and try again.

  • Voyager 401

    The handshake reached LinkedIn but the cookies were rejected, usually because JSESSIONID and li_at came from different sessions. Copy them in one go from the same tab without refreshing in between.

  • Account challenged

    LinkedIn is asking you to verify the login (email code or phone OTP). Open LinkedIn in a normal browser, complete the verification, then re-grab cookies, the new pair will pass.

  • Account restricted

    LinkedIn flagged the account itself for review, no automation tool will get past this until you resolve it with LinkedIn directly. Wait for their reply before reconnecting Mira.

What happens next

Once Mira has a connected session she'll start working the moment you create a LinkedIn campaign or an Omnichannel flow that includes a LinkedIn step. Connection requests pace themselves under LinkedIn's weekly limit, accepts get a follow-up message in your voice, and the second a prospect replies Mira hands the conversation back to you so a real human picks up the thread. If LinkedIn invalidates the session (logout, password change, suspicious-activity flag), Mira pauses the campaigns and the settings card flips to Disconnected so you know to reconnect.

Keep reading

Agents

Meet Mira

What Mira sends, when she stops, and how she hands off the moment a real conversation starts.

Concepts

Templates and flows

How LinkedIn fits into omnichannel sequences when you want Mira working alongside Eli and Vance.

Need help?

Ciela can walk you through any step. Or write to support@ciela.ai and we'll jump on the connection with you.

Ask Ciela