Content DistributionCan make changes
Publish X Post
Publish a final X post or thread within the run's explicit publication intent.
Branding plugin
X API
X API publishing provider contract for intent-scoped posts or threads.
Connection facts
What the X API connector actually exposes.
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
- Connection method
- OAuth connection
- Setup
- Create or select an X developer app with posting access, complete the required plan/app review, and store OAuth material in StackOS.
- Capability groups
- Content Distribution
- Action boundaries
- 1 write action
Action catalog
Actions listed for X API.
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
1 matching action
Direct answer
How does the X API integration work?
People continue using X API as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
- 01Your requestStart in your AI
- 02StackOS planExpands the steps
- 03X APIDoes its bounded part
- 04Checked resultKeeps the proof
More from Branding
Related integrations.
Branding
Channel Metrics
Provider-neutral metrics contract for channel-native outcome snapshots.
Outcome Learning
Branding
Email Service Provider
Provider-agnostic ESP contract for digest or standalone authority emails with list management, opt-in, unsubscribe, and metrics owned by the ESP.
Content Distribution
Branding
Git Remote
Git-backed canonical publishing target for static sites or repository-rendered blogs.
Content Distribution
Common questions
X API and StackOS.
What can the X API integration do in StackOS?
The current catalog includes 1 X API action across Content Distribution. The exact actions used depend on the workflow and approval rules.
Does StackOS replace X API?
No. X API remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.