Download a LinkedIn attachment

What Download a LinkedIn attachment does

Download a LinkedIn attachment fetches the raw file behind a LinkedIn message attachment, so documents, images, and other files shared in a conversation land in your own storage instead of sitting in the LinkedIn inbox. It runs on the LinkedIn level via a GET call that uses your connected identity plus the LinkedIn DMS URL; the response body is the binary file, ready for archival, scanning, or downstream automation.

Use it when inbox attachments are part of your pipeline — contracts, resumes, slide decks, screenshots — and you need them outside LinkedIn.

How it works

You call the action with the DMS (direct messaging service) URL for the attachment and the identity that has access to the containing thread. Edges streams the file back as raw bytes; you receive the binary response, the original filename, the MIME type, and the byte size. The call is authenticated against your connected LinkedIn session, which is why the DMS URL resolves — those URLs are scoped to a participant of the conversation.

Because the response is binary, you typically pipe it into storage (S3, GCS), an antivirus / DLP scanner, or a downstream parsing step such as resume or contract parsing. Edges does not transform the file; you get exactly what was uploaded.

When to use Download a LinkedIn attachment

Use this action when a workflow needs the file itself, not just the message text. Candidate resumes, signed order forms, vendor quotes, shared decks — any of these land in LinkedIn as attachments and typically need to move into your CRM, ATS, or document store.

It pairs with the messaging-side actions inside the LinkedIn messaging & outreach API use case — extract the conversation, find attachment URLs, download them into your storage.

Use cases

• Recruiting: save candidate resumes. When a candidate attaches a CV in LinkedIn chat, Download a LinkedIn attachment pushes the file into your ATS with correct filename and MIME type.
• Sales: archive signed documents. Move contracts and order forms out of the LinkedIn inbox into a secure document store for compliance.
• Security scanning. Route every inbound attachment through an antivirus or DLP scanner before your team opens it.
• Knowledge capture. Pull decks and PDFs shared by prospects into a searchable internal library.
• Automated parsing. Feed PDFs into an extraction pipeline (contract terms, RFP responses) triggered the moment the attachment arrives.

Best practices

• Validate MIME type before trusting the filename. LinkedIn passes through whatever the sender uploaded; use the mimeType field rather than a filename extension for routing decisions.
• Scan before you store or share. Treat LinkedIn attachments as untrusted input — scan with your standard tooling before broad distribution.
• Cache the binary on your side. DMS URLs expire; once downloaded, persist the file in your own storage and reference that path internally.
• Pair with conversation extraction. Chain from Extract LinkedIn Messages or Extract LinkedIn Conversations to discover attachment URLs across a thread, then fan out downloads.

Common questions

How many attachments can I download per run?

One file per call. For bulk processing, list attachments first via Extract LinkedIn Messages and fan out Download a LinkedIn attachment calls with server-side pacing handled by Edges.

Does Download a LinkedIn attachment use my LinkedIn account or a shared pool?

Your LinkedIn account. DMS URLs are scoped to conversation participants, so the action only succeeds when the identity you pass is a member of the thread. There is no shared pool.

Can I chain Download a LinkedIn attachment with other Edges actions?

Yes. Typical chains start from Extract LinkedIn Messages, pick out attachment URLs, then fan out Download a LinkedIn attachment calls to persist each file into your storage or trigger a parsing step.

Get started

Call Download a LinkedIn attachment from the Edges API, point it at a DMS URL and your connected identity, and stream the file straight into your storage. Browse the full Actions library to see what you can compose with it on the messaging side.