Automate & publish
Publishing
Choose a finished video and destination, review the post and track its publishing result.
Interface version 2.2.4 · 2026-10-24
Publish shows publishing records. Platform accounts are managed in Browser Pool in the sidebar. An empty Publish page offers New publish and Add account.

Content kinds: video / image-text / article#
New publish offers the kinds each platform supports — not every platform takes all three:
| Platform | Video | Image-text | Article (column) |
|---|---|---|---|
| Xiaohongshu | Upload video | Note: up to 18 images, body ≤1000 chars | — |
| Douyin | Publish image-text: up to 35 images, title 20, body 1000 | — | |
| WeChat Channels | Publish post: up to 18 images, title 22, body 1000 | — | |
| Bilibili | — | Column: title 50, body 100000 (can't be edited after publishing) | |
| TikTok | Photo carousel: up to 35 images, title 90, body 4000 | — | |
| X | Up to 4 images, title folded into the body | — | |
| YouTube | — | — |
Image-text and article take images (except articles): the asset field turns into the asset picker / an image grid. An article is one long text with no media; Bilibili columns are set to "only me" before submitting because they can't be edited afterwards.
Create a publish task#
Choose New publish, select an imported or exported video (or a set of images / a body for image-text and articles), add title, body and tags, then pick a platform account. The form shows the fields that platform and content kind need. AI copywriting requires a configured chat model.

Social uploads run in the desktop worker's embedded browser. A remote backend can store and queue tasks, but a connected desktop worker must perform the browser upload. Hosting the web interface alone does not provide that execution environment.
Manage sign-ins#
Add a platform account or general browser profile in Browser Pool. Open the account, sign in, complete verification and re-check its status. Sign in again if it expires. Proxies and sharing are configured per profile; see Browser Pool.
An account belongs to whoever added it: the destination list shows only your own accounts and those colleagues have shared into the workspace. An account someone hasn't shared can't be used to publish — not from the Publish page, a workflow's Publish node, a scheduled task or the agent. A scheduled task publishes as the task's owner; the agent publishes as whoever approved its confirmation card.
Review and submit#
Only supported platform options appear, such as visibility, originality declarations or YouTube's made-for-kids setting. Review the media, account, copy and options before submitting. Available options and authentication can change with the platform; complete verification in the account browser when prompted.
Publishing records show progress, errors and successful links. The task center and notifications also reflect progress. Workflow publishing nodes use the same publishing capabilities.
After it goes out: the post record#
When a publish succeeds, Mosael reads the post's id from the platform's own publish response (Douyin / TikTok item_id, Bilibili bvid, Xiaohongshu note id, YouTube video id) and stores it with the link and publish time on the record; the detail view has View on the platform. If the platform's response did not include it, the record says the post id was not read — the post itself went out, the field is simply empty rather than invented.
- A workflow's Publish node exposes Post ID and Post link outputs, so downstream steps can look up that post's data (with the TikHub plugin, or the analytics templates).
- The agent can list publishing records with the read-only
list_publish_taskstool. - Deleting a record that already went out only removes the local entry; nothing is taken down on the platform.
If queued publishes never start, the Publish page tells you the desktop publisher isn't running: keep Mosael open (closing the window only sends it to the tray), or restart the app.


