LinkedIn Writing Workflows: Messages, Invitations, Comments, and Posts
Map AGNURA’s LinkedIn writing surfaces: classic messaging, Sales Navigator inbox, invite notes, feed comments, Generate Post wizard, Voice to Text, and human insert/send.
LinkedIn writing workflows are the distinct drafting jobs you do on LinkedIn: reply in a chat, reply in Sales Navigator inbox, add an invite note, comment on a post, or publish a post. Each job uses different context. Mixing them causes bad drafts.
This hub maps those jobs for people who use AGNURA AI Assistant in Chrome. Task-level how-tos live as separate spokes. This page owns the map: which surface, which actions, which context, and what AGNURA never does (auto-send, bulk invites, engagement pods).
Direct answer
On LinkedIn in the browser, AGNURA can help you draft when Activate LinkedIn is on:
| Surface | Main generate action | Main rewrite action | Extra |
|---|---|---|---|
| Classic Messaging compose | Write Reply | Rewrite Message | Voice to Text mic |
| Sales Navigator inbox | Write Reply | Rewrite Message | Voice to Text + Select Template |
| Connection invite note | Write Invite Note | Rewrite Invite Note | 200-character cap |
| Feed comment box | Write a Reply | Rewrite Reply | Voice to Text |
| Create-post popup | Generate Post (wizard) | Rewrite Post | News / KB / story / article lanes |
Sales Navigator uses a separate content script from classic Messaging. Classic Messaging skips /sales/ paths so the two do not share injection logic.
Every AI draft still needs your review. Insert is manual. You click Send, Invite, Comment, or Post in LinkedIn.
Why the map matters
People often expect one “LinkedIn AI button” to mean the same thing everywhere. It does not.
- A message may need profile + thread.
- An invite note is short and profile-led.
- A comment needs the post (and visible comments).
- A post may need ideas from news, a knowledge base, a personal story, or one article.
Using rewrite when you need generate (or the reverse) wastes a call and can drop the context you care about. The Gmail pair works the same way: Generate vs Rewrite in Gmail: Which Context Is Used?.
Key concepts
Generate vs rewrite (LinkedIn)
| Pattern | Typical inputs | Job |
|---|---|---|
| Generate / Write | Surface-specific prompt + context (profile, thread, post, comments, wizard sources) + optional knowledge base / What I want to say | Create a first draft from context |
| Rewrite | Shared rewrite prompt + current draft | Polish wording without reloading full conversation/post context |
Human-in-the-loop
Drafting is not sending. AGNURA does not auto-send messages, auto-connect, auto-comment, or auto-publish posts.
Local settings vs managed AI
Prompts, Activate LinkedIn, news catalog, and wizard answers live in Chrome local storage. Generate/Rewrite calls use your AGNURA sign-in. Voice to Text uses the browser speech API (no managed AI). See Local Settings vs Local AI: The Privacy Difference.
Options by surface
1. Messaging (Write Reply / Rewrite Message)
Where: Classic LinkedIn messaging compose footer (not Sales Navigator).
Write Reply can send:
- LinkedIn reply prompt
- Optional What I want to say
- Shared knowledge base
- Recipient profile (best-effort from profile page and/or messaging; may use session-backed profile fetch paths when only a profile URL is visible)
- Conversation thread when available
Birthday hints from the profile Highlights area can steer openings when present. Top Activity posts may be included when visible on the profile.
Rewrite Message sends rewrite prompt + compose draft only (no profile, thread, or knowledge base).
Requirements (Write Reply): AGNURA credits, non-empty LinkedIn reply prompt, and at least profile or thread context.
How-to: How to Write a LinkedIn Reply From Profile and Thread Context.
1b. Sales Navigator inbox (separate feature)
Where: LinkedIn Sales Navigator conversation compose under /sales/inbox/....
Write Reply uses the same LinkedIn reply prompt and optional knowledge base, plus:
- Recipient name and headline from the thread header (and
/sales/lead/...link when present) - InMail / message thread text from the open conversation
It does not run classic /in/ Voyager profile redirects from this script. Profile context is thinner than classic Messaging.
Rewrite Message, Select Template, and Voice to Text are also available on the Sales Nav actions bar.
How-to: How to Write a Reply in LinkedIn Sales Navigator Inbox. Compare surfaces: LinkedIn Messaging vs Sales Navigator: Which Context AGNURA Uses.
2. Connection invite notes
Where: LinkedIn “Add a note to your invitation” modal.
Write Invite Note uses invite prompt, profile context (including recent Activity posts when available), and knowledge base. Output is capped at 200 characters.
Rewrite Invite Note rewrites the note draft under the same cap.
Insert into the note field is manual. AGNURA does not click Send invitation for you.
3. Feed comments
Where: Comment box on a feed/post (“Add a comment…”).
Write a Reply uses comment prompt, post text, visible comments, optional What I want to say, and knowledge base. Last generated reply per post can be stored locally (up to 50 posts) and reloaded.
Rewrite Reply is draft-only (no post/comments/KB).
Voice to Text appends dictation into the comment editor.
4. Create post (Generate Post / Rewrite Post)
Where: LinkedIn create-post popup footer (not the closed feed composer row).
Generate Post opens a 5-step wizard (answers saved locally):
- Idea source: Industry news, Knowledge base only, Personal story, or React to one article
- Topic inputs (industries, story notes, article URL, or KB confirm)
- Feel: audience / format / tone / time window (plus advanced must-include/avoid/prompts)
- Pick an idea (news/article lanes can show real RSS headlines)
- Generate post text, then Insert / Copy
Rewrite Post polishes the post draft with the shared rewrite prompt (optional What I want to say). No ideas/RSS/KB on rewrite.
News industries and feeds live under Settings → News Sources.
Decision framework
| If… | Then… | Because… |
|---|---|---|
| You are answering a classic chat | Messaging Write Reply | Profile + thread matter |
| You are answering Sales Navigator InMail | Sales Nav Write Reply | Separate surface; header + thread |
| You already typed the message | Rewrite Message | Draft-only polish |
| You are connecting with a note | Write Invite Note | Short, profile-led, 200-cap |
| You are commenting on a post | Feed Write a Reply | Post + visible comments |
| You need a new LinkedIn post from news or KB | Generate Post wizard | Idea lanes are built for that |
| You only want to rephrase a finished post | Rewrite Post | Smaller context |
| You want dictation without AI cost | Voice to Text | No managed AI call |
Checklist: responsible LinkedIn drafting
- Confirm Activate LinkedIn is on; refresh LinkedIn after toggles.
- Open the correct surface (message, invite, comment, or create-post).
- Prefer facts visible in profile, thread, post, or your knowledge base.
- Generate or rewrite once.
- Edit claims, tone, and length (especially invite notes).
- Insert manually.
- You click Send / Invite / Comment / Post in LinkedIn.
Where AGNURA fits
AGNURA AI Assistant is a Chrome extension. LinkedIn helpers run on LinkedIn pages you already have open. They do not replace LinkedIn’s product rules or your judgment.
Prerequisites
- Desktop Chrome + AGNURA installed
- Signed into LinkedIn in that profile
- Activate LinkedIn on (default on for new installs)
- AGNURA sign-in for generate/rewrite actions
- Matching prompts under Settings → LinkedIn Prompts / Rewrite Prompt / News Sources as needed
Setup: Install AGNURA From the Chrome Web Store and Sign In and Use AGNURA AI Credits.
Compared with common alternatives
| Approach | Fit |
|---|---|
| Copy into a chatbot tab | Works; more context loss |
| LinkedIn-only auto-outreach bots | Volume; higher platform and trust risk; not AGNURA’s job |
| AGNURA on-page LinkedIn drafting | Same-tab context, manual insert/send |
Risks and limits
- Profile, thread, and comment scrapes are best-effort. Lazy-loaded or private content may be missing.
- Managed AI receives the context you trigger for that action via AGNURA managed AI. Review privacy expectations first: AGNURA Privacy in Plain Language.
- AGNURA does not automate connection requests, bulk DMs, engagement pods, scheduling, or auto-posting.
- No acceptance-rate, reply-rate, or reach promises.
- Follow LinkedIn’s terms and your company’s outreach policy.
Website research before outreach (often useful before a LinkedIn note) lives in What Is Website Intelligence for Sales and Outreach?. Email-side drafting: Research-to-Email Outreach: From Website Context to a Reviewed Gmail Draft.
Related guides
- What Is AGNURA?
- AGNURA Feature Reference by App and Action
- Generate vs Rewrite in Gmail: Which Context Is Used?
- Local Settings vs Local AI: The Privacy Difference
- AGNURA Not Showing or Not Generating: Troubleshooting
Soft next step
Pick one LinkedIn surface you use this week (message, invite, comment, or post), run one generate or rewrite, and force a human edit before you publish. Install AGNURA if you need the on-page controls:
Try AGNURA in Chrome
Draft in Gmail, LinkedIn, WhatsApp, and Reddit. You review every message before send.
Add to Chrome