LinkedIn: Upload Image
Upload local image files directly to LinkedIn so the returned asset URN can be attached to posts.
Audience: Content teams and operators attaching images to LinkedIn posts.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Content teams and operators attaching images to LinkedIn posts.
LinkedIn: Upload Image
Upload local image files directly to LinkedIn so the returned asset URN can be attached to posts.
Philosophy
The image upload tool handles the entire binary transfer internally, returning the required asset URN immediately.
Technically Managed By
- Direct workspace file access reads local image paths or URLs.
- Handles LinkedIn upload registration and binary push internally in a single step.
- Returns a stable asset URN (e.g., urn:li:share:123) for post composition.
How Users Should Use and Manage It
- 1Verify that the target file path exists in your workspace before calling the tool.
- 2Provide the returned URN as the media attachment in nexus_linkedin_post.
How It Fits in Nexus
- Supplies the URN for post attachments, making image sharing seamless.
What Matters
- Direct workspace path mapping
- URN generation
- Auto-managed registration step
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.