📣 Social publishing

Connect your social accounts and let the platform post your promotion calendar.

📣 Social is the Social publishing page: connect accounts, compose and schedule posts, and let AI build a whole promotion calendar from the event's own content.

🔌 Connecting accounts

Accounts are connected per event, so each conference can post as its own handle. Four channels, each an expandable row showing ✅ connected (green) or ○ not connected:

Channel	What it needs
Bluesky	An identifier (your handle) and an app password. The page tells you where: bsky.app → Settings → Privacy & Security → App Passwords. This is the smoothest of the four.
X / Twitter	An access token, generated in your X developer account.
Facebook Page	A page ID and a page access token from the Facebook developer tools.
Threads	A user ID and an access token.

ℹ️ Note

There's no OAuth "sign in with…" flow here — you paste credentials you generate on each platform, and they're stored as secrets (the token fields are masked as you type). Bluesky app passwords are quick to create; the other three require a developer app, which is a one-time chore per organization.

⚠️ Heads up

Platform tokens expire. If posts start failing with an error in the history, a stale token is the first thing to check — re-paste a fresh one and save.

✍️ Composing a post

The Compose box takes up to 500 characters ("What's happening at the conference?"), a tick-box per channel — connected ones are pre-ticked, unconnected ones dimmed — and a date-and-time picker. Press Schedule.

One post can go to several channels at once, and each channel's result is tracked separately, so a failure on one doesn't hide a success on another.

✨ The AI campaign calendar

✨ AI campaign calendar drafts a whole run of posts from what's already in the event — sessions, speakers, description. Set how many you want (1 to 12, default 6) and press Draft calendar from event content.

Choose a post count and draft.
Read the proposal. Each post is listed as +5d: the copy — plus a rationale explaining why it's there and why then. Check the facts: speaker names, session titles and dates come from your data, but the framing is the model's.
Press Schedule all to: bluesky, x — the button names the channels it will use, which are your connected ones. If it says "no channels connected", connect an account first.
Or Discard and re-draft with a different count.

💡 Tip

Draft the calendar after the agenda and speakers are in, not before — it writes from event content, so an empty agenda produces generic posts. Re-drafting once the lineup is announced gets a far better calendar.

⚠️ Heads up

Applying the calendar schedules every post at once. There's no per-post approval step after you press the button, so read the whole list before you do. Spacing comes from the +Nd offsets relative to now.

📋 Queue & history

Everything scheduled and sent is listed newest-first with its time and status — published in green, failed in red, or pending in grey. Under each, per-channel results: bluesky: posted (a link to the live post where the platform returns one), or the error text for a channel that rejected it.

That per-channel breakdown is what to check after a calendar goes out — a post can succeed on Bluesky and fail on X in the same send.

📅 A promotion rhythm that works

Announcement — the event exists, with dates and the link. Point at /interest/{tag} if registration isn't open yet.
Lineup — one post per notable speaker or session as the agenda firms up. This is what the AI calendar is best at.
Deadlines — early-bird ending, hotel block closing. Real deadlines move more tickets than anything else you post.
Final call — the week before, and the day before.
During — a few live moments. Schedule these in advance; you will not have time on the day.
After — thanks, plus a pointer at the recordings in the video library and the interest page for next year.