Coco + LinkedIn
Connect LinkedIn and Coco drafts your outreach in your voice, grounded in the prospect's actual public activity. Coco doesn't run spray-and-pray automation that gets accounts flagged — it drafts, you send (or you approve Coco to send through connected access for specific approved workflows). Coco also identifies mutual connections and surfaces warm paths to a target account. Sales Navigator is supported. About 4 credits per drafted LinkedIn message.
Try Coco for free → · 1,000 credits free · no card · ~2-min setup
What Coco does with LinkedIn
LinkedIn is a relationship channel, not a volume channel. Coco's posture on LinkedIn is built for that.
Drafts connection requests in your voice. When you ask Coco to reach a target contact, it pulls their public activity — recent posts, comments, role changes, company news — and drafts a connection request that references something real. Not "I'd love to add you to my network." The kind of opener a thoughtful human would write after looking at the profile. About 4 credits per drafted message. See LinkedIn outreach →.
Drafts InMails for non-connection outreach. When the target isn't a 1st-degree connection, Coco drafts InMails grounded in the same kind of public-activity research. The voice match is the same. Drafts queue for review.
Drafts follow-up DMs on existing conversations. For threads where you've already connected, Coco can read the conversation history (with your permission, per-thread) and draft the next message — value-add, not "just checking in." Drafts queue.
Identifies mutual connections and warm paths. When you're trying to reach an account, Coco surfaces which of your existing connections are connected to people there. The warm-intro path is one of LinkedIn's actual moats and Coco makes it operational instead of buried. See find design partners → for how this feeds the design-partner search.
Surfaces public-activity signals for research. Coco reads target contacts' recent LinkedIn activity as one of the inputs into account research — what they're posting, what they're commenting on, what role changes are happening on their team. Combined with research accounts →, this builds the kind of context that turns a cold email into a warm one.
Sales Navigator support. When you have Sales Navigator, Coco can use its richer search filters and saved-list functionality. The integration is otherwise the same posture: read for context, draft for review, send gated.
Behavior model — why Coco doesn't flag LinkedIn accounts
LinkedIn has gotten aggressive about flagging accounts that exhibit automation patterns. The reason most LinkedIn automation tools risk your account is that they run high-volume sequencing through your account at machine cadence — hundreds of connection requests a day, scripted DMs, scraped at speed.
Coco's posture is structurally different. Coco drafts; you send. The send action lives inside your normal LinkedIn behavior — your normal cadence, your normal click patterns, your normal sessions. There's no autonomous bot sitting on your account sending at 3am.
For workflows where you've explicitly authorized Coco to send through connected access (a narrow set of approved patterns), the send is still rate-limited to human-believable cadence inside human-believable session windows. The point isn't to maximize volume; it's to keep relationship-channel outreach high-quality.
This is the same anti-spray-and-pray posture that runs through the whole product. See why Coco isn't a spray tool → for the design rationale.
Approval gates by action type
| Action | Approval gate |
|---|---|
| Read public profile data for a target | Free — no gate |
| Read your own existing conversation history | Free — per-thread, with your permission |
| Draft a connection request, InMail, or DM | Free — drafts gate at send, not write |
| Identify mutual connections to a target | Free — no gate |
| Send connection request | Approval-gated |
| Send InMail | Approval-gated |
| Send DM | Approval-gated |
| Accept connection request on your behalf | Not in scope |
The structural default: Coco drafts; you click send. For specific approved workflows where you've authorized Coco to send through connected access (typically Sales Navigator API-backed flows), the send still operates inside the rate-limits and human-cadence guardrails described above.
Workflows that use LinkedIn
LinkedIn is one of the primary outreach and research surfaces in Coco's GTM stack. The workflows that lean hardest:
- LinkedIn outreach → — connection requests, InMails, and follow-up DMs drafted in your voice.
- Find design partners → — LinkedIn as a research surface for fit-evaluation and warm-path surfacing.
- Research accounts → — LinkedIn activity as one of several inputs into the account brief.
Each workflow uses LinkedIn as a context source and a destination for drafted (not auto-sent) outreach.
How this compares to Lavender
LinkedIn outreach is where Lavender lives — Lavender is a Chrome-extension coaching layer that helps you write better email and LinkedIn messages while you type. Honest framing: Lavender and Coco are different categories of tool.
Lavender coaches. You sit down to write a message; Lavender scores your draft against best practices and suggests improvements. The human stays in the chair doing the typing.
Coco does the work. You hand Coco a target; Coco assembles research, drafts the message, surfaces warm paths, queues the next-step. The work happens whether you're at the keyboard or not.
For teams that want a writing-coach layer on top of their existing motion, Lavender is the right tool. For teams whose bottleneck is the work itself — research, drafting, follow-through at volume — Coco's wedge is the actual execution. See Coco vs Lavender → for the full breakdown.
Try Coco for free → · 1,000 credits free · no card · ~2-min setup
Frequently asked questions
Will Coco get my LinkedIn account flagged?
No. Coco's posture is draft-then-you-send by default. There's no autonomous bot running on your account at machine cadence. For workflows where you've explicitly authorized connected send, the send rate-limits to human-believable cadence inside human-believable session windows. The structural anti-spray design is the safeguard.
Does Coco work with Sales Navigator?
Yes. When you have Sales Navigator, Coco can use its richer search filters and saved-list functionality. The behavior model and approval gates are the same — Coco drafts; you send.
Can Coco send InMails directly?
For specifically approved workflows, yes. The default is that Coco drafts and queues; the send action is your click. For workflows where you've authorized connected send (typically Sales Navigator API-backed flows), the InMail send operates inside the same rate-limits and approval guardrails as other send actions.
What scopes does Coco need?
Read for research (public profile, public activity, mutual connections). For specific workflows that include connected send, additional scope is required and granted only for those workflows. You can revoke at any time and the affected workflows pause until you grant again.
Can Coco accept connection requests on my behalf?
No — that's not in scope. Accepting incoming requests is a judgment action that stays with you. Coco can surface incoming requests as a queue for you to review, but the accept/decline action is yours.
Get started
If LinkedIn is where your relationships live but you're not finding the time to do thoughtful outreach there, the integration takes a couple minutes and the first drafted message lands within ten minutes after connection.
Try Coco for free → · 1,000 credits free · no card · ~2-min setup
Or book a walkthrough → if you'd rather see the LinkedIn workflow in action first.