Register Document Upload
linkedin.register_document_upload
ActionChat & messagingconnection required
Calls the LinkedIn API with the connection's credentials.
Step one of a document upload: reserve the document URN and a one-shot upload URL. Use linkedin.upload_document unless you need the steps apart.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Secret shape
- the LinkedIn OAuth2 access token, or {"access_token": "…"}
- Config it needs
- api_version
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
owner_urn Who owns the uploaded asset: urn:li:person:{id} or urn:li:organization:{id}. It must match the author of the post the asset is used in. | string | Yes | — | — | urn:li:organization:2414183 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"owner_urn": "urn:li:organization:2414183"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
document_urn The urn:li:document: to pass to create_share. | string | — |
upload_url One-shot URL to PUT the bytes to. | string | — |
upload_url_expires_at When that URL stops working (epoch ms). | number | — |
owner The owner URN the upload was registered for. | string | — |
{
"document_urn": "",
"owner": "",
"upload_url": "",
"upload_url_expires_at": 0
}Notes
- An image or document is a three-step dance: register the upload, PUT the bytes, then reference the returned URN as media_urn on linkedin.create_share. The asset must reach status AVAILABLE before the post renders it.
See Register Document Upload run in a workflow.
In a technical demo we add the LinkedIn connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.