Publish and preview
Choose Create post in the web app, select the target accounts, write the message, and attach any images or videos. Review each platform's preview and settings before choosing a posting action.
Draft, publish, or schedule
- Save as Draft stores your work without publishing. Drafts can be incomplete; blocking platform validation runs before publishing or scheduling.
- Post Now sends the post to the selected accounts. Check each account's result before assuming everything published.
- Schedule for Later stores the post for a future time. Read scheduling, including what happens if your trial expires before delivery.
Open drafts and future scheduled posts from Posts to edit them. Editing or deleting a published SimplePost record does not edit or remove the original social post; use the social network for those actions.
Different content for each account
Use the account's advanced editing controls to customize its text, media, or thread. A field without an override inherits the shared content. Check the preview for each selected account. In API requests, use accountOverrides keyed by connected account ID; provider settings such as a Pinterest board belong in accountOptions. Payload fields.
Media and platform settings
SimplePost checks content length, supported media combinations, required fields, and file limits. Fix blocking errors before publishing. Warnings can indicate that a platform will omit unsupported content.
Instagram needs media; YouTube needs a video; Pinterest needs media and a board. Facebook publishes to Pages. TikTok may require audience and consent choices in the web app. Use account requirements and the platform matrix for details.
Upload local files through the web app. For MCP, use an attached/generated file exposed by the assistant or a public media URL. A local filesystem path or browser blob: URL cannot be fetched by the remote service. MCP media uploads.
Upload limits
The file limit depends on how you upload to SimplePost storage:
| Interface | Maximum per file |
|---|---|
| Web app | 50 MiB |
| Scheduler API and MCP | 500 MiB |
| CLI using Scheduler-connected accounts | 500 MiB (local files are uploaded through the API) |
| Direct SDK and local CLI accounts | Provider and configured storage limits; the hosted upload cap does not apply |
MiB means 1,048,576 bytes. Provider limits also apply after upload: a successfully uploaded file can still be rejected by a platform. For example, Bluesky's 300 MB video allowance does not increase the web app's file picker limit. Use the API, MCP, or hosted CLI for larger supported files.
Public media URLs bypass the local upload step, but must stay reachable for the provider and satisfy its file-size, format, duration, and URL requirements. MCP may fetch an attached file before uploading it, so its upload limit still applies. See the platform limits and media storage guide.
Threads and quotes
Native reply chains are supported on X, Bluesky, Threads, and Telegram. Other selected platforms receive the root content, with a warning for unsupported follow-ups. The trial permits twenty total segments; other interface limits still apply. The remote MCP tools currently accept text-only follow-ups with media on the root.
Quote an existing SimplePost post using its quote action. Native quote behavior is available on X, Bluesky, Threads, and LinkedIn; other destinations receive an ordinary post. A quote of a scheduled source must publish after that source.
Previews in chat
Ask your assistant to show a preview. show_post_preview renders a visual preview in supported clients; preview_post returns validation and scheduling details as data. A preview does not publish or schedule anything. Tell the assistant explicitly when to save a draft, schedule, or publish. Assistant workflow.
Check the outcome
A post can succeed on one account and fail on another. Inspect the account results and published links. For failures, use Edit and Retry and review the selected targets before sending again. Failure recovery.