Messagingsales nav

Extract Sales Navigator Messages

Sales Navigator Message Scraper extracts messages from a Sales Navigator conversation thread.

POST/v1/actions/salesnavigator-extract-messages/run/live

Try it live See pricing

Edges is not related to LinkedIn and is not an official LinkedIn product.

Input

Request parameters

FieldTypeRequired

cursorstringno

Cursor value obtained from the `X-Pagination-Next` response header of a previous request, used to continue pagination. Cursors expire after 24 hours. If a cursor has expired or is invalid, pagination must be restarted from the beginning.

page_sizeintegerno

Maximum number of results per page (read-only; defined by the endpoint, actual count may be lower in some cases like throttling or internal limits).

Input parameters

FieldTypeRequired

sales_navigator_thread_urlstringyes

A message thread url should look like: 'https://www.linkedin.com/sales/inbox/2-YTcwY2QwNDMtZjE4OS00YmQ2...MzFkMjk4XzAxMw==/'.

Integration

FieldTypeRequired

identity_idsarrayyes

Array of identity UUIDs to use for the action

identity_modestringyes

Mode for identity handling: direct, auto, or managed.

Description

What Extract Sales Navigator Messages does

Extract Sales Navigator Messages pulls the full message history from a Sales Navigator conversation thread into structured rows you can archive, analyse, or feed downstream. Each row is a single message with sender, timestamp, body, and attachment metadata.

It is the Sales Navigator twin of Extract LinkedIn Messages. The action is designed for teams who treat SN InMail and SN inbox threads as a channel that belongs in the CRM.

How it works

You pass a sales_navigator_thread_url from the SN inbox. Edges reads the thread through your authenticated Sales Navigator session and returns typed message rows, including LinkedIn and SN profile IDs for the counterpart.

The operation runs live. A malformed thread URL or a thread the seat cannot see returns a typed error.

When to use Extract Sales Navigator Messages

Use this when you already have a thread URL — from Extract Sales Navigator Conversations or from a known InMail conversation — and need the bodies, not just the inbox index.

Typical placement is after a conversations extract that detected a new or updated thread.

Use cases

Archive SN InMail threads into a data warehouse for compliance or coaching.
Feed reply text into a classifier or an agent that drafts the next message.
Attach the latest SN message to a CRM activity on the contact.
Pull attachments metadata for downstream document handling.

Best practices

Resolve the inbox with Extract Sales Navigator Conversations first; only fetch messages for threads that changed.
Cache on sales_navigator_thread_id. Do not re-extract an unchanged thread on every poll.
Run large backfills async with a callback rather than a tight live loop.
Do not pass a LinkedIn messaging/thread URL here — that belongs to Extract LinkedIn Messages.

Common questions

What do I pass in?

A Sales Navigator inbox thread URL (linkedin.com/sales/inbox/...). Get it from Extract Sales Navigator Conversations or from the SN UI.

Does this list every conversation?

No. One thread per call. Use Extract Sales Navigator Conversations for the inbox index.

Do I need a Sales Navigator seat?

Yes. The action reads the SN inbox on the connected identity.

Get started

Take a thread URL from Extract Sales Navigator Conversations, call Extract Sales Navigator Messages, and write the rows to your CRM or warehouse. Browse the library for InMail send and other SN messaging actions.

Request

curl -X POST "https://api.edges.run/v1/actions/salesnavigator-extract-messages/run/live" \
  -H "X-API-KEY: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
  "identity_ids": [
    "your-identity-uuid"
  ],
  "identity_mode": "direct",
  "input": {
    "sales_navigator_thread_url": "https://www.linkedin.com/in/example-profile"
  }
}'

Response

200 OK · application/json

[
  {
    "sales_navigator_thread_id": "example-123",
    "delivered_at": "example_value",
    "first_name": "John",
    "last_name": "Doe",
    "full_name": "John Doe",
    "linkedin_profile_id": 42,
    "sales_navigator_profile_id": "example-123",
    "content": "example_value",
    "message_id": "example-123",
    "type": "example_value",
    "attachments": [
      1,
      2,
      3
    ]
  }
]

Build this with your agentMCP

Connect our docs MCP server and your coding agent can search every action and write this call for you.

docs.edges.run/mcp

// Related

Other ways to work with Messaging.

linkedin-accept-invitationAccept InvitationAccept a pending LinkedIn connection invitation so new relationships appear in your network.linkedin linkedin-accept-invitationsAccept pending LinkedIn invitations (bulk)Accept many pending LinkedIn invitations in one automated run. Use async or scheduled execution to process your inbox at scale and grow your network faster. For a single invitation, use the live Accept LinkedIn invitation action.linkedin linkedin-archive-messageArchive MessageArchive a LinkedIn conversation thread to tidy your inbox while keeping message history available.linkedin linkedin-download-attachmentDownload a LinkedIn attachmentDownload a file from a LinkedIn message attachment. The public API uses GET with your identity and the LinkedIn DMS URL; the response is the raw file (binary), suitable for storage, scanning, or further automation.linkedin linkedin-extract-conversationsExtract LinkedIn ConversationsLinkedIn Conversation Extractor extracts conversations from your LinkedIn account.linkedin linkedin-extract-messagesExtract LinkedIn MessagesLinkedIn Message Scraper extracts messages from a LinkedIn conversation.linkedin

Try it with 100 free credits.

No card. Copy the snippet, paste your key, hit enter.

Get API key ← Back to library