Docs / Insight
who_went_cold
List the conversations that went quiet.
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 |
|---|---|---|
connectionIdoptional | A connection id. Restrict to one LinkedIn sender. Omit to span all live senders. | Run list_linkedin_accounts and use accounts[].id from its answer.15 more places to get it
|
daysoptional | A number, 1 to 365. Consider a conversation cold when there's been no message for at least this many days (default 14). | You write it. |
onlyWithReplyoptional | True or false. true = only threads where the other person replied at least once (skips pure no-response outreach). Requires the full thread to be synced. | You write it. |
limitoptional | A number, 1 to 200. Max threads to return (1–200, default 100). | You write it. |
Call it
curl -X POST https://api.heyreagent.com/v1/actions/who_went_cold \
-H "Authorization: Bearer YOUR_KEY" \
-H "content-type: application/json" \
-d '{}'The same call in JavaScript
const response = await fetch("https://api.heyreagent.com/v1/actions/who_went_cold", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_KEY",
"content-type": "application/json",
},
body: JSON.stringify({}),
});
const answer = await response.json();
console.log(answer);The same call in Python
import requests
response = requests.post(
"https://api.heyreagent.com/v1/actions/who_went_cold",
headers={"Authorization": "Bearer YOUR_KEY"},
json={},
)
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/who_went_cold |
| 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 |
{}Put your own key where it says YOUR_KEY. New here? Start with your first call.
What you get back
When it worked, the answer is { "ok": true, "result": { … } }. Inside result:
summary | |
coldConversations | |
nextAction | |
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
- It reads the stored inbox; see needsInboxSync.
- hasInboundReply is null when the whole conversation is not stored.
What its answer goes into
get_profileGet a profileget_profile_detailsGet a profile in depthsend_invitationSend an invitationget_conversationGet a conversationsend_messageSend a messagesync_inboxRefresh the inboxstart_conversationStart a conversation (InMail, group, company)list_inmailList InMail conversationsget_recent_postsGet someone's recent postslist_posts_by_authorList a person's or company's postslist_comments_by_personList the comments a person wrotelist_reactions_by_personList what a person reacted to
Guides that use it
- Muse spaces: a LinkedIn follow-up board in your Muse app
- Muse voice: talking to your Muse about your LinkedIn
- How to use Grok Bot for your LinkedIn
- An AI SDR for LinkedIn that asks before it sends
- What Claude Duet means for your LinkedIn work
- How to use Claude Haiku 5.5 on your LinkedIn inbox
- LinkedIn message automation, one person at a time
- How to use ChatGPT dots for your LinkedIn
- How to follow up on LinkedIn conversations that went quiet
In Claude or ChatGPT
Once connected, ask in your own words. The assistant sees this action as a tool with the same name, who_went_cold, and the same inputs.
More in Insight
who_is_waiting_on_meWho is waiting on my replyconnections_never_messagedConnections I never messagedengagers_not_connectedEngagers I am not connected to