LinkedIn + SalesCrew
A queue and a ledger, worked by a person. SalesCrew tells you who to touch and records what happened. It does not log into LinkedIn and it does not click for you.
- Queue and ledger, human-executed
- No LinkedIn automation
- Profile-level attribution
The short answer
- The honest mechanism: SalesCrew holds a queue of profiles to work and a ledger of what was done. A person opens LinkedIn and does the action. There is no browser agent, no cookie session and no unofficial API.
- The ledger records connection requests sent and accepted and conversations started, per profile and per sender, so LinkedIn stops being the channel nobody can report on.
- This is a deliberate limit. Tools that automate LinkedIn put the account at risk, and an account ban costs more than the tool saves. SalesCrew keeps the human in the click.
Mechanism
One row here matters more than the rest: there is no automation of LinkedIn itself.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Queue | Profiles queued from contacts, ICPs or by URL | Internal | LinkedIn queue rows, contacts | Available |
| Ledger | Statuses and timestamps recorded as a person works the queue | Internal | Ledger rows, timeline | Available |
| Attribution | Per sending profile, so results are readable by person | Internal | Ledger, KPIs | Available |
| Adding a prospect | URL-first: paste a profile URL and a row is created | Internal | Contacts, queue rows | Available |
| Sending a connection request | A person does this in LinkedIn | , | , | By design, never automated |
| Reading LinkedIn messages | Not built. Replies are recorded by the person who got them | , | , | Not available |
| Sales Navigator sync | Not built | , | , | Not available |
| LinkedIn agent that drafts messages | Agent drafts, a person approves and sends | , | , | On the roadmap |
Mechanisms read from the SalesCrew integration table, September 2026. LinkedIn's own user agreement is the authority on what automation is permitted on the platform.
Setup
Twenty minutes, and the discipline is in step five.
- 1
Define who belongs in the queue
An ICP or a segment, so the queue is a filtered list rather than everyone you ever exported.
- 2
Queue the profiles
linkedin_queue_add takes a profile URL and a status; linkedin_queue_add_contacts queues a set of existing contacts at once.
- 3
Assign a sender
Each row carries the profile that will do the work, which is what makes results readable per person later.
- 4
Work the list
Open the queue, open LinkedIn, send the request or the message yourself, then set the status. linkedin_queue_update does the same from a script.
- 5
Record the truth, not the plan
Sent, accepted, replied. A ledger only earns its place if it says what actually happened, including the rows where nothing did.
- 6
Pair it with email
Run the LinkedIn queue beside an email cadence on the same segment, and let the reply on either channel stop the other.
Questions
- Why not automate LinkedIn like other tools do?
- Because the platform's user agreement does not permit it and a restricted account takes the whole channel with it. A queue that a person works is slower and it keeps the account.
- Does SalesCrew read my LinkedIn inbox?
- No. There is no message sync. Replies are recorded by the person who received them, or by an agent through the MCP tools if you script it that way.
- What can an agent do here?
- It can queue, prioritise and, on the roadmap, draft the message. The action of sending on LinkedIn stays with a person, and any agent-written message would wait in the approval queue first.
- How do I report on LinkedIn results?
- The ledger gives requests sent, accepted and conversations started, per profile. That is enough to compare LinkedIn against email on the same segment.
- Can I import a Sales Navigator list?
- Through CSV into the data bank, then queue from there. There is no live Sales Navigator connection.
Give LinkedIn a ledger it never had
A queue your team works by hand, and numbers you can finally put beside the email channel.