/v1/actions/linkedin-archive-message/run/liveArchive Message archives a LinkedIn conversation thread programmatically, moving it out of your primary inbox while keeping the full message history queryable. It runs on the LinkedIn level against the account you connect to Edges, so every archive action is logged against your authenticated session and reversible from the LinkedIn app.
Use it to keep the LinkedIn inbox focused on live conversations without losing context — the thread is not deleted, just hidden from the default view.
You pass the conversation identifier (or the participant's profile URL) and Edges flips the archive flag on that thread through your connected LinkedIn session. The action is synchronous: by the time the run returns, the conversation no longer appears in your main inbox and has moved to the Archived view inside LinkedIn. No browser, no cookies, no scraping on your side.
Archiving is idempotent — running the action on an already-archived thread returns a clean status rather than an error. If the thread has been deleted, Edges returns a typed error so your workflow can branch.
Reach for Archive Message when inbox organization is part of your automation, not a manual chore. The action is a clean primitive for a "done" signal — close a deal in your CRM, archive the LinkedIn thread; mark an opportunity lost, archive the thread; tag a conversation as handled inside Edges, archive the thread.
It pairs with the LinkedIn messaging & outreach API use case, where teams orchestrate send, read, and archive steps around their CRM state.
markAsRead or chain into Mark Message As Read first if you want the counter to clear before the thread disappears.One conversation thread per run. Archive Message is a single-record primitive; for volume archiving, fan it out from a list produced by Extract LinkedIn Conversations and pace the calls.
Your LinkedIn account. You connect LinkedIn to Edges once and the archive action is executed through that authenticated session. The operation appears in your own activity log, not a shared pool.
Yes. Typical chains include Extract LinkedIn Conversations to build a candidate list, Mark Message As Read to clear the counter, and then Archive Message to close out the thread.
Run Archive Message from the Edges library, wire it into your CRM state machine, or call it from the Edges API. Browse the full Actions library to compose it with read, extract, and send actions into a complete inbox-management workflow.
curl -X POST "https://api.edges.run/v1/actions/linkedin-archive-message/run/live" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"input": {
"linkedin_thread_id": "example_value",
"custom_data": "example_value"
}
}'{
"linkedin_thread_id": "example-123"
}