X/Twitter: Post
Publish updates directly to an authorized X account immediately, supporting text and reply-to threading.
Audience: Social media operators and marketing teams publishing directly via Nexus.
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
Social media operators and marketing teams publishing directly via Nexus.
X/Twitter: Post
Publish updates directly to an authorized X account immediately, supporting text and reply-to threading.
Philosophy
Provide instantaneous publishing to X, ensuring text length constraints are validated beforehand.
Technically Managed By
- OAuth-authenticated client credentials authorize the publish request.
- Supports replyToTweetId parameter to chain replies or construct threads.
- Limits post text to standard 280 characters with prompt-time validation.
How Users Should Use and Manage It
- 1Draft and preview the post content in Chat first.
- 2Provide a replyToTweetId if you are replying to an existing conversation thread.
How It Fits in Nexus
- Allows the Assistant to act as an active publisher on social channels under human oversight.
What Matters
- Immediate X publishing
- Thread chaining via reply-to
- Content previewing
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.