Docs / Messages

`get_conversation`

Read your whole conversation with one person.

This action only reads. It changes nothing, so it is safe to try.

What you give it

Input	What it is	Where to get it
`conversationUrl` needed	A conversation link or a profile link. The other person's LinkedIn profile URL (https://linkedin.com/in/…) — preferred — or a /messaging/thread/ URL.	Open the person's profile on LinkedIn and copy the address from your browser. It looks like https://www.linkedin.com/in/their-name Or run `search_people` and use `people[].profileUrl` from its answer. 30 more places to get it `list_conversations` → `inbox[].conversationUrl` `get_my_profile` → `accounts[].profileUrl` `list_connections` → `connections[].profileUrl` `list_sent_invitations` → `pendingInvitations[].profileUrl` `list_received_invitations` → `invitations[].profileUrl` `list_followers` → `followers[].profileUrl` `list_conversations` → `inbox[].participantProfileUrl` `list_chat_attendees` → `attendees[].profileUrl` `list_inmail` → `inmail[].participant.profileUrl` `search_posts` → `posts[].author.profileUrl` `search_linkedin_people` → `results[].publicProfileUrl` `search_linkedin_people` → `results[].profileUrl` `search_linkedin_sales_navigator_people` → `results[].publicProfileUrl` `who_is_waiting_on_me` → `waitingOnYou[].profileUrl` `who_went_cold` → `coldConversations[].profileUrl` `connections_never_messaged` → `leads[].profileUrl` `get_profile_details` → `publicProfileUrl` `list_chat_participants` → `participants[].profileUrl` `get_chat_attendee` → `profileUrl` `get_inmail_conversation` → `participant.profileUrl` `get_post_engagers` → `reactors[].linkedinUrl` `get_post_engagers` → `commenters[].linkedinUrl` `list_post_comments` → `comments[].authorDetails.profileUrl` `list_post_reactions` → `reactions[].author.profileUrl` `list_job_applicants` → `applicants[].publicProfileUrl` `get_job_applicant` → `publicProfileUrl` `engagers_not_connected` → `leads[].profileUrl` `search_people_sales_navigator` → `leads[].linkedinUrl` `find_decision_makers` → `leads[].linkedinUrl` `get_conversation` → `participant.profileUrl`
`connectionId` optional	A connection id. Which of your senders owns this conversation (its linkedinConnections _id). Omit to search your live senders; for a live fetch the first live sender is used.	Run `list_linkedin_accounts` and use `accounts[].id` from its answer. 15 more places to get it `get_my_profile` → `accounts[].connectionId` `list_connections` → `connections[].connectionId` `list_connections` → `summary.accounts[].connectionId` `list_sent_invitations` → `pendingInvitations[].connectionId` `preview_withdraw_invitations` → `breakdown[].linkedinConnectionId` `list_conversations` → `inbox[].linkedinConnectionId` `list_inmail` → `inmail[].connectionId` `get_inmail_credits` → `accounts[].connectionId` `list_sales_navigator_contracts` → `accounts[].connectionId` `who_is_waiting_on_me` → `waitingOnYou[].connectionId` `who_went_cold` → `coldConversations[].connectionId` `connections_never_messaged` → `summary.accounts[].connectionId` `get_usage` → `connectionId` `get_inmail_conversation` → `connectionId` `get_conversation` → `connectionId`
`refresh` optional	True or false. true = fetch live from LinkedIn even if cached. false (default) = return the cached thread when available, else fetch live.	You write it.

Call it

curl -X POST https://api.heyreagent.com/v1/actions/get_conversation \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"conversationUrl":"PASTE_PROFILE_LINK_HERE"}'

The same call in JavaScript

const response = await fetch("https://api.heyreagent.com/v1/actions/get_conversation", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "conversationUrl": "PASTE_PROFILE_LINK_HERE"
  }),
});
const answer = await response.json();
console.log(answer);

The same call in Python

import requests

response = requests.post(
    "https://api.heyreagent.com/v1/actions/get_conversation",
    headers={"Authorization": "Bearer YOUR_KEY"},
    json={
        "conversationUrl": "PASTE_PROFILE_LINK_HERE",
    },
)
print(response.json())

The same call in n8n

Add an HTTP Request node and fill it in like this:

Method	`POST`
URL	`https://api.heyreagent.com/v1/actions/get_conversation`
Send Headers	On. Name `Authorization`, Value `Bearer YOUR_KEY`
Send Body	On. Body Content Type `JSON`, Specify Body `Using JSON`, then paste the body below

{
  "conversationUrl": "PASTE_PROFILE_LINK_HERE"
}

Put your own key where it says YOUR_KEY. Put your own value where it says PASTE_…_HERE: the table above says where each one comes from. New here? Start with your first call.

What you get back

When it worked, the answer is { "ok": true, "result": { … } }. Inside result:

`source`
`connectionId`	A connection id. Other actions take it.
`exists`
`participant`
`chatId`	A chat id. Other actions take it.
`inbox`
`messageCount`
`messages`
`note`

A field that does not apply to an answer is left out, or is null.

When it did not work, the answer is { "ok": false, "error": "…", "message": "…" }. What each error means.

Good to know

chatId and participant come back only when source is "live". An answer from the stored copy (source "cache") has neither; refresh true forces a live read.
A linkedin.com/messaging/thread/… link works only for a stored conversation. For a live read pass the person's profile link.
For an InMail, Sales Navigator or Recruiter conversation the answer adds replyWith with the chatId: reply there with send_chat_message. send_message by profile link would start an ordinary conversation instead.
exists false with uncertain true means it could not be checked, not that there is no conversation.

In Claude or ChatGPT

Once connected, ask in your own words. The assistant sees this action as a tool with the same name, get_conversation, and the same inputs.