Publishing a post

One draft. Four platforms. One tap — yours.

When Ashley finishes a post, you get an editable card in the chat: caption, hashtags, images, and a toggle for each platform. Publishing is what happens after you've read it, changed what you wanted, and pressed the button. Unyo never presses it for you.

Where a post can go

Four destinations, each with its own real API flow — not a link dump, not a "share sheet".

Publish a draft

1. Open the post card in your Ashley conversation.
2. Read the caption. Edit it directly on the card — the text, the hashtag chips, the image order. Every platform tab shows a live character count against that platform's real limit.
3. Toggle the platforms you want. Ashley suggests a set; you decide.
4. Press Publish.
5. Unyo pre-flights every platform you selected. If one isn't connected, it stops there and tells you which one — before anything goes out.
6. All selected platforms are published in parallel. A toast tells you what went out and names any platform that failed, and the card's activity row keeps a per-platform Published/Failed record you can open.

Real native carousels

A carousel isn't four posts and it isn't one image with a collage. Each platform gets its own correct flow:

• Instagram — every image becomes a child container, they're assembled into a real CAROUSEL parent, and that parent is published. Swipeable in the app, exactly like one you'd make by hand. Up to 10.
• Facebook — the images are uploaded unpublished, then attached to a single multi-photo post. Up to 10.
• LinkedIn — each image is registered and uploaded through LinkedIn's own Assets API before the post is created. Up to 9.
• X — each image is uploaded to the media endpoint and the ids are attached to the post. Up to 4.

Ask for a carousel and you get one. Ask for a post and you get exactly one image — Ashley is instructed never to invent a carousel you didn't ask for.

When one platform fails

This is the normal case at some point, and it's designed for rather than hidden.

The four publishes run at the same time and are independent, so a dead LinkedIn token cannot block a successful Instagram post. The successes stay published and the failure is isolated. Open the card's activity row to see the per-platform breakdown: Published for what worked, Failed for what didn't. You fix the one thing and re-run the one thing.

Every failure comes back as an actionable code rather than a shrug — a missing connection, an expired token, a missing permission, a rate limit, or a platform rule you hit. When it's a token, the toast names the platform that failed — reconnect it from Integrations in the sidebar.

Click twice, post once

Before it publishes anything, Unyo fingerprints the job: a SHA-256 hash of the message, the platforms, the full caption, the sorted image URLs and the schedule time. That hash is the job's key.

So if you double-tap, or your Wi-Fi drops mid-request and you retry, or you press Publish again because nothing seemed to happen — you get the existing job back, not a second post. A job still running says so. A job that already published hands you back the permalinks it already has. Duplicate posts are structurally impossible, not merely unlikely.

Connection checks fail closed

Publishing and scheduling both check every targeted platform's connection first, and if the check itself errors, it blocks rather than guesses — nothing goes out to a platform Unyo can't confirm you're connected to.

Connect and reconnect accounts from Integrations in the sidebar. See the guides for Instagram, Facebook, LinkedIn and X.

Platform rules worth knowing before you tap

After it's published

• Per-platform status — open the card's activity row to see which platforms went out and which didn't.
• Optional follow-through — if you turn them on, a successful publish can save a formatted summary to Google Drive, create a page in your Notion content library, and announce the post in Slack. This is strictly opt-in: with nothing enabled, nothing runs.
• Save the images — say "save these images" and the post's images are filed into a colour-coded folder in your Neural Core, each with the prompt that made it.

Tips

• Write for the tightest platform first. If it reads well in 280 characters, it reads well everywhere.
• Check the Instagram tab last — it's the one that refuses text-only posts, and it's usually the one that matters most.
• Publishing now and scheduling later are the same card. See Scheduling a post for the timing side.
• Once you have published a few posts, ask Ashley what's actually working — Social analytics reads your own numbers, not invented benchmarks.

FAQ

Troubleshooting

"Instagram is not connected" but I connected it. The token may have expired. Open Integrations in the sidebar and reconnect — the card's error tells you which account.

Instagram refused my post. Two likely causes: the post has no image (Instagram requires at least one), or the connected account is personal rather than Business/Creator. Convert the account in the Instagram app, then reconnect.

My X post is cut off. X's 280-character limit is enforced at publish time and longer captions are truncated. Check the counter on the X tab before publishing.

Some platforms worked and some didn't. Open the card's activity row for the per-platform breakdown. To retry, deselect the platforms that already published, leave the failed one selected, and press Publish — that's a new job, so the successful posts are untouched.

Nothing happened when I pressed Publish twice. That's the idempotency guard doing its job. The second press found the first job and returned it. Check the card for the result.