Posts and threads
Plan X in the same workspace as the rest of your channels.
X
Keep the idea sharp from first post to final reply
Plan X posts and ordered threads beside the rest of your campaign, adapt the copy for the feed, and keep every delivery result visible.
Publishing requires an X developer app and API access for the connected account. BlendDuck shows that access state before scheduling.
X publishing flow
Channel version
ValidatedTomorrow 09:30
X
Delivery state visibleMedia-aware drafts
Shape the native format before it reaches the publishing queue.
Target-level delivery
Keep access, delivery, and provider state visible to the team.
Plan X with the rest of the campaign
Start from the shared brief and Brand Soul, then give this channel the timing, copy, and creative treatment it needs.
- Keep the source idea connected to every channel version
- Review the destination and schedule before delivery
- Use one calendar for the complete campaign
X plan01
1Posts and threads
2Media-aware drafts
3Target-level delivery
Workspace state Reviewable
Publish formats that belong on X
BlendDuck keeps native settings where they matter and applies platform validation before the provider receives the request.
- Concise text posts
- Ordered reply threads
- Supported images and video
Supported workflow02
1Per-post copy and timing
2Media validation before delivery
3Idempotent publish requests
Workspace state Reviewable
Know what is ready, what shipped, and what needs attention
Connection grants and provider responses stay separate from optimistic UI, so the team can act on the exact missing permission or failed target.
- Published URL
- Provider response state
- Connection and API-access status
Operational evidence03
1Connection checked
2Content validated
3Delivery recorded
Workspace state Reviewable