App Logo
linkedin.com

Sales Navigator – Get conversation thread

Fetch a full LinkedIn Sales Navigator conversation thread by its threadId (from get_inbox), pulling up to messageCount messages. Returns the counterpart participant(s), totalMessageCount, whether it was truncated, and every message in chronological order (oldest first) with body, subject (for InMails), whether it is a regular message or an InMail, deliveredAt, lastEditedAt, attachments, and direction (sent/received). A 1:1 thread has one counterpart, group threads list all; if returnedCount is below totalMessageCount, raise messageCount. Needs a Sales Navigator seat.

Input

threadId required

Conversation thread id from get_inbox (e.g. '2-NWU3...XzEwMA==').

messageCount optional

Max messages to fetch. Default 100 — enough for the whole thread in most cases. Compare returnedCount to totalMessageCount to detect truncation and raise this.

Default: 100

Output

messages required

Chronological, oldest first.

threadId required
archived optional
truncated optional

true when returnedCount < totalMessageCount — raise messageCount.

viewerUrn optional
viewerName optional
unreadCount optional
participants optional

Counterpart(s) — everyone except the viewer.

returnedCount optional
totalMessageCount optional

FAQ

Fetch a full LinkedIn Sales Navigator conversation thread by its threadId (from get_inbox), pulling up to messageCount messages. Returns the counterpart participant(s), totalMessageCount, whether it was truncated, and every message in chronological order (oldest first) with body, subject (for InMails), whether it is a regular message or an InMail, deliveredAt, lastEditedAt, attachments, and direction (sent/received). A 1:1 thread has one counterpart, group threads list all; if returnedCount is below totalMessageCount, raise messageCount. Needs a Sales Navigator seat.
Required: threadId. Optional: messageCount.
It returns archived, messages, threadId, truncated, viewerUrn, viewerName, unreadCount, participants, returnedCount, totalMessageCount.
Yes. It acts as you on linkedin.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the linkedin.com cookies saved by the Reduck extension.
Unknown: its author has not declared whether it changes anything on linkedin.com, so treat it as if it could.
Ask an AI agent connected to Reduck to run reduck/linkedin.com/sales_navigator_get_thread, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/linkedin.com/sales_navigator_get_thread
It is part of Reduck's official curated catalogue.

Start building not clicking