nv.syncConversation

This action loads your Sales Navigator message history with a person. It finds the person's Sales Navigator threads and reads each of them. Read the history, together with the new messages the inbox captures, through /inbox/poll with personUrl. See Loading conversation history for when you need it.

💡 Run it once per person – not to check for new messages. New messages reach you through inbox monitoring.

Constraints

⏺️ Root Start: allowed, when personUrl parameter is provided.

⬆️ Parent Actions: st.openPersonPage, nv.openPersonPage.

⬇️ Child Actions: N/A.

Parameters

{
  "actionType": "nv.syncConversation",
  "label": "sync1",
  "personUrl": "https://www.linkedin.com/in/person1",
  "days": 14
}

In AI assistants, the MCP server runs this action as the nv_sync_conversation tool.

  • label (optional) – custom label for tracking this action in workflow completion.
  • personUrl (required for root start, forbidden for parent start) – public or hashed LinkedIn URL of the person whose conversation you want to load.
  • days (optional) – how many days Linked API keeps adding this person's new messages to the loaded history, from 1 to 90. Defaults to 30.

Syncing period

💡 days is the syncing period, not the depth of history. It sets how many days new messages keep being added; the action always reads the whole conversation, however old it is.

Linked API keeps adding this person's new messages to the loaded history until the syncUntil moment returned by this action, counted from the moment the action starts running. With inbox monitoring enabled, new messages from this person keep arriving through the inbox after that moment as well.

After that moment nothing is deleted: polling keeps returning the messages collected so far. Running this action again for the same person keeps the accumulated history and never shortens the period: syncUntil stays at the later of the current end and the new one.

A reply from the other person does not extend the period.

A thread read back to its first message is reported with historyComplete: true when you poll the person. A very long conversation may not be read to its start within the action's time limit: the messages read are kept, and the thread stays historyComplete: false.

This action does not enable inbox monitoring and does not produce inbox webhook events.

Result options

  1. Successful syncing:
json
{
  "actionType": "nv.syncConversation",
  "label": "sync1",
  "success": true,
  "data": {
    "syncUntil": "2026-09-09T09:55:31.582Z"
  }
}
  • label – included only if specified in the action parameters.
  • data.syncUntil – moment until which Linked API keeps adding this person's new messages to the loaded history.
  1. Failed syncing:
json
{
  "actionType": "nv.syncConversation",
  "label": "sync1",
  "success": false,
  "error": {
    "type": "noSalesNavigator",
    "message": "Your account does not have Sales Navigator subscription."
  }
}
  • label – included only if specified in the action parameters.
  • error.type – enum with the following possible values:
    • noSalesNavigator – your account does not have Sales Navigator subscription.
    • personNotFound – provided URL is not an existing LinkedIn person.