Autocloz + Unipile
Unipile is offered as a provider when you add a LinkedIn account in Autocloz, but it is not wired: there is no Unipile client in the code, so a LinkedIn sender set to Unipile falls through to the stub provider and every action is recorded as failed with a "real provider not registered" message. Nothing is sent through Unipile. For LinkedIn outreach today, use Autocloz's in-house automation, which runs from your own session cookie with built-in pacing.
Status: not available today. Not available. Unipile appears in the LinkedIn provider list, but no Unipile integration exists in the code. Choosing it produces failed touches, never sent ones.
What exists for Unipile in Autocloz
Fails visibly
Autocloz's rule is that a missing provider fails loudly. A Unipile sender shows failed touches in the Unibox and reports.
Working alternative
The in-house provider handles visits, invites, messages and InMails from your own account.
Same pacing either way
Whatever provider is eventually used, LinkedIn steps pass the same weekly caps, warm-up and quiet hours.
What to do instead of Unipile
- 1
Do not pick Unipile for a new account
In LinkedIn → Accounts, choose Direct (paste cookie) instead.
- 2
Move existing Unipile senders
If you created a Unipile sender, add the same LinkedIn account with Direct (paste cookie) and switch your sequences to it.
- 3
Paste li_at
Copy the li_at cookie from a logged-in browser and paste it.
- 4
Let the ramp run
New senders start at 5 actions on day one and grow over 21 days.
Checking which provider a sender uses
Open LinkedIn → Accounts and look at each account's provider. Anything showing Unipile or PhantomBuster will fail. Accounts showing Direct (paste cookie) or Direct (email and password) use the in-house provider and send for real.
Moving a Unipile sender to the in-house provider
Create a new LinkedIn account in Autocloz with Direct (paste cookie), using the same LinkedIn profile. Point your sequences' LinkedIn steps at the new sender. Leads who already received failed Unipile touches can be retried; nothing was sent to them through LinkedIn, so there is no duplicate. The new sender starts its 21-day ramp at 5 actions on day one, so plan volume accordingly.
Why Unipile is in the list at all
Autocloz originally planned to drive LinkedIn through third-party providers such as Unipile and PhantomBuster. It then built its own provider, which talks to LinkedIn from your session, and the code describes that provider as replacing Unipile and PhantomBuster. The provider picker still lists the old options. Because nothing is registered under the Unipile name, Autocloz's dispatcher uses its stub, which by design reports failure.
We are saying this plainly because a page describing Unipile's "durable session" would suggest a working path that does not exist.
What the in-house provider covers
Profile visits, invites with or without a note, messages to connections, InMails, automatic withdrawal of invites left pending for 14 days, and polling for accepts and replies. It adds a 21-day warm-up, a default weekly cap of 80 invites, a hard stop at 1,000 pending invites and cross-sender de-duplication over 90 days. Details are on the LinkedIn channel page. Messaging tips are in LinkedIn connection message templates.
What Unipile does not do in Autocloz
- No Unipile API connection of any kind.
- No PhantomBuster connection either, although it is also listed.
- No hosted LinkedIn sessions; the in-house provider uses your own cookie.
Troubleshooting Unipile
- A LinkedIn sender's touches all fail with "stub provider".
- The sender's provider is Unipile or PhantomBuster. Recreate it as Direct (paste cookie).
Part of the LinkedIn stack
Unipile is one of the ways to drive the LinkedIn channel. Both share the same visit/invite/DM steps, weekly caps and unified-timeline tracking.
Explore the LinkedIn featureRelated integrations
Playwright/Voyager session bridge — visit · invite · DM · InMail with weekly safety caps.
View integrationCall Control v2 + WebRTC softphone, signed-URL recordings, Ed25519 webhook verification.
View integrationIn-browser Voice SDK calling + low international SIP rates; CDR poll for retroactive ingest.
View integrationFrequently asked
Will Unipile be added?
There is no plan in the code for it. The in-house provider is the supported path.
Is PhantomBuster any different?
No. It is also listed in the picker and also has no integration behind it, so it fails the same way.
Do failed Unipile touches count against LinkedIn limits?
No. Nothing reached LinkedIn, so they do not count toward weekly invite caps.
Try Autocloz free
One sequence builder for email, LinkedIn, calls, SMS and WhatsApp — free forever for 3 users on email and calls.