XPlanner

Docs

App Guide

Quickly set up a workspace, X account, and content flow in the XPlanner app.


Overview

What does this guide cover?

This section describes the day-to-day work in the XPlanner interface rather than the API. The goal is that you can follow the same flow, step by step, from the first account to publication.

  1. First select the workspace and active X account.

  2. Capture your ideas in the Ideas screen and separate them into folders if necessary.

  3. Turn ready-made ideas into posts or create a new post from the Posts screen.

  4. Save the post as a draft, schedule it on your calendar, or share it on X if it's ready.

First Setup

What to have ready before you start

XPlanner manages the content production flow around the workspace and X account. If you're working with multiple brands or customer accounts, it's important to choose the right context first.

  1. Select the correct workspace from the top bar.

  2. Choose the account you want to work with from the X account selector.

  3. If there is no account, link account X from the Account Settings > Accounts screen.

  4. For scheduled posts and publishing, make sure you have an active subscription and a healthy account connection.

Open accounts screen

X account linking and managing linked accounts screen.

Open

Open subscription screen

Check plan, limit and usage status.

Open

Recommended Stream

The simplest daily usage flow

For regular sharing, the cleanest model is to use XPlanner first as an idea pool and then as a post planning tool.

  1. Save the raw notes that come to your mind as ideas first.

  2. Separate ideas into folders such as campaign, product, build-in-public, or customer question.

  3. Turn the idea you're ready to share into a post.

  4. Schedule shipping and check weekly distribution in the Calendar screen.

It is safer to keep texts of which you are not yet sure as ideas; Only move them to the post feed when they're close to sharing.

How will the guide be updated?

When a new user flow occurs, this section is added as a new page to the same docs structure.

When the display language changes, the actual button and title names are checked again with Playwright smoke.

API-related flows are cross-linked to the relevant API v1 page.