One idea. A complete publishing workflow.
Build a consistent presence on X with account profiles, rich drafts, planned posts, useful replies, and measured results.
8 min read1. Choose the account you are writing for
Use the header account switcher or Settings → Account & data → X accounts to add, rename, and switch profiles under your owner login. Each profile works with manual publishing; switch to that profile before connecting its optional X API account.
Posts, calendar entries, results, X credentials, and automation settings belong to the selected account. Writing style, Posting Slots, categories, ideas, routines, and manual replies are shared across your workspace. Profiles do not create separate team logins.
Existing content belongs to Main account after upgrading. A scheduled API post keeps its approved destination when you switch profiles, and browser tabs retain their account for edits. Resolve unsaved work when prompted before switching.
An assistant has its own explicit destination: use list_accounts, then pass the local profile ID as workspaceAccountId. Omitting it uses Main account; switching the browser does not redirect the assistant.
2. Turn useful material into your next post
- Save source material in Ideas, or open Write to start from a blank post.
- Write one post, then add another to make a thread. Preview a long-note split before applying it. Valid edits autosave with a visible status.
- Add categories and tags to organize your work. Use search, filters, sorting, and saved browser views in Posts to return to the right draft.
- Connect an MCP assistant if you want help preparing ideas or drafts. Review Suggestions before accepting them, and approve or reject proposed writing-style changes.
A browser recovery copy can retain unfinished text and references to uploaded media. It cannot recover a file that never finished uploading. If edits conflict, copy your changes before reloading the saved version.
3. Give each post the right media
Each post can contain up to four JPG, PNG, or WebP images, one GIF, or one MP4/MOV video. A GIF or video must be the only attachment in that post. Images and GIFs have a 10 MB per-file workspace limit; videos have a 50 MB limit.
Use the video preview's playback and seek controls to check the file. MP4 with H.264 video and AAC audio provides broad browser compatibility; MOV playback depends on the browser and codec. Include video descriptions in the post text.
Manual publication offers the original files for download so you can attach them on X. API publication uploads video in chunks and waits for processing. Your host's request limits can be lower than the workspace limits, and X can reject media that does not meet its requirements.
4. Build a plan you can follow
Set your timezone and preferred Posting Slots in Settings → Posting routine. Move between the Posts list and Month, Week, or Day calendar, keep undated drafts nearby, or create directly from a date.
Use Next available time for a free preferred time, or preview batch planning before applying it. Today brings due posts, delivery needing attention, and pending conversations together. A daily posting goal is optional.
A planned time is a manual reminder unless you deliberately choose and approve X API delivery. Planning alone does not publish anything.
5. Choose manual or approved API publication
Choose Prepare to post → Publish manually to copy the ordered text, download attachments, and open X. After you publish, record the actual publication time and optional X URL. Copying or opening X does not mark the post Published.
For API delivery, connect your own eligible X app, enable publication, and approve the saved text, media, thread order, and destination account. Then choose Publish now or an explicit future API delivery time. Changes to the publication content or account require fresh approval.
The application scheduler sends approved originals without an AI client staying online. If a thread only partly publishes, the workspace records confirmed parts. Check held or uncertain delivery before retrying or switching to manual publication.
6. Keep useful conversations moving
For a manual reply, save an X conversation in Replies with its text, context, and optional screenshot. Request preparation through your connected assistant, review or edit its options, then publish on X and record the result. Reply history stays separate from original-post counts.
Optional reply automation collects eligible targets into a separate inbox. Accepting a target in the app or Telegram authorizes a permitted external assistant to generate and publish one reply to that target without another wording review. Only accept when you want to grant that permission.
Collection, publication, replies, and self-replies have separate controls. An accepted target waits for an available, separately configured agent; Telegram acceptance does not itself start one. You can reject or revoke permission before sending starts.
Target approval for a generated reply is different from reviewing the exact wording of an original post. Both require owner action; an MCP connection alone grants neither approval.
7. Learn from results you actually measured
Open Record results on a Published post or thread. Enter the measurements you can see and their measurement time, or ask a connected assistant to help interpret a performance screenshot. Leave unavailable values blank; use zero only for a measured zero. Later snapshots preserve the earlier history.
Insights compares publication periods, shows measurement coverage, and tracks weekly progress. Review these alongside the individual posts before deciding what to write next; missing measurements are not evidence of poor performance.
With a connected X account and the necessary read access, Sync from X can import recent original posts and append available measurements. The sync is bounded to the latest 100 originals plus up to 100 linked older single posts. It does not turn a thread root's numbers into a whole-thread total.
The landing page's sample posts, numbers, and animated follower, like, and reply notifications are illustrative examples. They use no live account data and are not customer results, a follower-tracking feature, or a promise of growth. Pause motion and your system's reduced-motion preference stop the notification animation.
8. Build toward an audience and paid opportunities
Use a repeatable writing and review routine to give people a reason to follow you. OwnPost helps you prepare, publish, and learn from your posts so you can spend more time sharing useful work and talking to the people it serves.
- Define who you write for, the topics you can help with, and your writing style. Give a connected assistant that context before requesting ideas or drafts.
- Plan useful posts and threads in your Posting Slots. Mix practical lessons, examples from your work, and relevant offers you want your audience to know about.
- Use Replies to prepare thoughtful contributions to conversations. Review manual replies yourself, or deliberately approve eligible targets when using reply automation.
- Record post metrics or use optional X sync, then review Insights for patterns across measured posts. Use what you learn to refine topics and the next week's plan.
- When you have an offer, write a clear post explaining who it helps and the next step. Link to your own product, service, newsletter, or booking page, and measure sales or sign-ups in the service that handles them.
This workflow supports audience building; it does not automatically grow followers or guarantee income. The app has no follower or revenue dashboard and does not unlock monetization eligibility. X payouts and commerce payments happen outside your workspace.
9. Keep your work portable
Choose Cloudflare, Vercel, Netlify, or a VPS for your private deployment. Download a content backup from Account & data to preserve supported content and stored media across all account profiles, within the 25 MB and 2,000-record package limits.
Restore previews the package and requires an initialized, empty content workspace. The destination keeps its owner login; credentials and connections are excluded. Reconnect integrations and deliberately resume routines and automation after checking the restored content.