The ten things people hit first.

1. Go to Settings › Profiles and press Connect Facebook.
2. Log in with the Facebook account that administers the Pages you want to manage, and approve the permissions Facebook lists.
3. You come back to a list of every Page you administer. Each Page that has a linked Instagram account shows that account directly underneath it.
4. Tick only the Pages and Instagram accounts you actually want. Nothing is imported until you confirm the selection — connecting Facebook by itself adds no accounts.
5. SupahPost then does a first sync and your posts start appearing. The first sync of a busy Page takes a while; you do not need to wait on the screen.

Your connections are kept private, and SupahPost never asks for and never stores your password for any connected platform — you sign in on that platform's own screen and it hands us a token, not a credential. You can disconnect an account at any time, from SupahPost or from the platform's own app settings; our Privacy Policy sets out, platform by platform, what we hold and how to remove it.

The list is exactly what Facebook returns for your account, so a missing Page is almost always one of these:

• You are not an admin of the Page. A Page you only moderate or edit may not appear. Ask the Page owner for an admin role and reconnect.
• You unticked it during the Facebook permission screen. Facebook lets you deselect individual Pages while approving. Reconnect and make sure the Page is ticked there, not just in ours.
• The Instagram account is personal, or not linked to the Page. We only see Instagram accounts that Facebook reports as a Business or Creator account attached to a Page. Convert it in the Instagram app, link it to the Page, then reconnect.
• Your access is older than the feature you're trying to use. If posting fails but analytics work, your connection was created before publishing permissions were granted. Reconnect Facebook and the new permissions apply.

If none of the above fits, email support with the Page name — we can see exactly what Meta returned.

1. Open the Scheduler tab and start a new post.
2. Pick the accounts it goes to. One post can target several accounts at once.
3. Write the caption. You can then override the caption per account — useful when the same content goes to a Facebook Page and an Instagram account that want different wording.
4. Attach media. You can upload directly, pull from your library, or send something straight over from the Create tab.
5. Optionally set a first comment, which is posted automatically right after the post goes live.
6. Choose a time — drag it onto the calendar, type one, or let SupahPost take the next open slot for that account based on when that account's own audience has actually shown up.

To change the time later, edit the post — a draft, scheduled or failed post can be moved or rewritten. Deleting a scheduled post also withdraws it from Facebook if it had already been handed over.

SupahPost publishes to Facebook Pages, Instagram, TikTok, YouTube and X. That is the whole list. There is no LinkedIn, Threads or Pinterest publishing — we would rather do five platforms properly, with real account access and real error reporting, than list twelve. You can also pull source material from X links inside the Create tab; that is a different thing from publishing.

The limits that bite in practice:

• Instagram requires media. A text-only Instagram post is not possible — that is Instagram's rule, not ours. Facebook allows text-only posts.
• Facebook posts cannot mix photos and video, and take at most one video. Instagram may mix.
• Carousels are up to 10 items on Instagram. That is the limit of Instagram's publishing API, even though the Instagram app itself allows more.
• Instagram caps how many posts an app may publish for you in a rolling 24 hours (currently around 50). SupahPost reads your remaining allowance from Instagram directly and, if you are near the cap, holds the post and tries again shortly rather than burning it on a rejection.
• Accepted files: JPEG, PNG, WebP and GIF images; MP4 and MOV video. iPhone HEIC photos are converted to JPEG automatically when you upload them.
• Stories are a single item.

Four separate things, and you can use any of them without the others:

• It makes posts. Paste an X or Facebook link and it builds a finished tweet-screenshot composite. Describe a topic and it designs a graphic in your template. Give it a list and it builds a carousel.
• It writes captions and headlines, using your own published posts as the reference for voice.
• It edits by conversation. Inside the editor you can ask for a change in plain language instead of clicking — and everything it does is a normal edit you can undo or adjust by hand.
• It reads your images. Every image you post is run through text recognition, which is why you can search your own history for a name or a phrase that only ever appeared inside a graphic.

The Assistant tab is separate again: it answers questions about your own numbers — "which posts did best last month, and what did they have in common?" — from your synced data.

Two things you may expect and not find: AI image generation is not switched on, so there is no button for it. Web photo sourcing is limited; if it is not enabled for your workspace, upload a photo or use your library.

There are daily ceilings on AI actions per workspace, set so a day's work sits inside them and a runaway loop cannot empty your balance overnight. If you hit one, it says which one and resets at midnight UTC.

Open the post in the Scheduler. Each target account carries its own status and, when something went wrong, the actual message the platform returned — not a generic error.

Two different things can happen, and they look different on purpose:

• Held, and retried automatically. If Instagram's rolling publishing cap is nearly full, or a workspace limit is reached, the post is held and tried again shortly. Nothing is lost and no attempt is used up.
• Failed, and waiting for you. If the platform rejected the post while publishing it, SupahPost stops and tells you. It deliberately does not retry. Meta can return an error after having actually published, so an automatic retry risks posting the same thing twice on your live page. Check the account, then either fix and reschedule the post or delete it.

Failures raise an in-app notification, and a Slack message if you have connected one. They do not send you an email. You choose which emails you get in Settings › Account › Email notifications; sign-in and billing messages cannot be switched off, because those are the ones that stop you losing the workspace by surprise.

The most common causes: an expired or revoked Facebook connection (reconnect in Settings › Profiles), media that breaks a platform rule from question 4, or an Instagram account that has been switched back to a personal account.

SupahPost keeps its own copy of your data and every screen reads from that copy, which is why a screen does not wait on the platform and why looking at your numbers is not billed.

• New posts are picked up automatically every few minutes.
• Performance figures refresh on a full sync, which you can run at any time and which also runs on its own schedule.
• Earnings, for Facebook Pages in Meta's Content Monetization Program, refresh on a tiered schedule: posts from the last two weeks every time, posts up to two months old weekly, older posts monthly. Meta keeps adjusting recent figures, so recent posts are checked hardest.
• History: a normal sync covers the last 90 days. If you want your full back catalogue, ask for a backfill — it reaches back about two years and takes a while to run, so it is done deliberately rather than automatically.

About earnings figures specifically: the dollar amounts come from Meta. The rate per thousand views is SupahPost's own calculation and is labelled as an estimate everywhere it appears — it is not a number Meta reports. Pages outside the monetization program work exactly the same; the dollar column is simply empty.

Your Facebook connection is checked daily. If a token has expired or been revoked, Settings › Profiles shows it and reconnecting fixes it.

SupahPost runs an MCP server, so an AI assistant can work with your own data and tools directly. Open Connect your AI in the sidebar; it walks you through three steps — copy your link, add it as a connector in Claude, then approve. For Claude Code and other MCP clients the same page makes a key and writes the exact config block for you.

266 tools are available: your profiles and performance data, search across your own posts including the text inside images, your content library, your scheduled posts and drafts, and tools that make graphics.

You choose what a key is allowed to do, from three tiers:

• Read — looks at everything, changes nothing.
• Schedule — can also put posts on your calendar, but cannot publish immediately.
• Publish — can put a post in front of your audience.

The raw key is shown once, at creation; after that we only hold a hash of it and cannot recover it for you. Every call a connected AI makes is written to an audit log you can read in the app, kept for 90 days. You can revoke one key or all of them at any time, and revoking takes effect immediately. Creating and revoking keys is an admin action.

Connecting an AI is a way to ask SupahPost things. A webhook is the other direction: you give us an address, and we tell your own systems the moment something happens — a post publishes, a post fails, a report finishes. People use it to drop a row in a spreadsheet, page whoever is on call, or kick off the next step of their own pipeline.

Add one in Settings → Integrations → Webhooks: paste an https:// address, tick the events you want, and press Add. There is a Send test button beside it, and a log of the last 50 deliveries with what your server answered and how long it took.

The events you can subscribe to:

• post.published — a post went live on one account (once per account).
• post.failed — a post did not go out on one account.
• post.scheduled — something entered the queue.
• post.approval_requested — a post is waiting on a person.
• post.approved — an approver released it.
• post.changes_requested — an approver sent it back with a note.
• account.needs_reconnect — a connection stopped working.
• account.rpm_drop — a page's revenue per view fell well below its own normal.
• account.reach_collapse — an account has stopped reaching people, and whether we held its posts.
• report.generated — a report finished building.

Every request is signed, so you can be sure it came from us. The X-SupahPost-Signature header looks like t=1756900931,v1=<hex>, where the hex is an HMAC-SHA256 of <t>.<raw body> using your signing secret. Refuse anything whose t is more than five minutes old. Accept the request if any v1 matches — during a rotation there are two. The exact code to do that is on the Connect your AI page, under “Other AI tools”.

The signing secret is shown once, when you create the endpoint. We store it encrypted and cannot show it to you again. If you lose it, press Rotate: you get a new one and the old one keeps working for 24 hours, so you can deploy the change without missing anything.

If your server is down we keep trying, with a growing gap, for up to 24 hours. We do not retry when your server answers with a 4xx — that means the address is wrong, not that it is busy. After 10 failed deliveries in a row we switch the endpoint off and tell you, in the app and by email; fix it and switch it back on from the same screen.

We will only post to an address that is reachable on the public internet, over https. A private or internal address is refused when you add it, and checked again every time we send.

Four plans, published on the pricing page: Creator $29 a month, Pro $69, Studio $119, Agency $199, each with a yearly rate that works out cheaper. Enterprise starts at $499 and is arranged with us directly. You pick a plan when you sign up and can change it from Settings afterwards.

Every plan starts with a 7-day free trial. A card is taken when you sign up and nothing is charged until the seven days are up; cancel before then and you are not billed. You are told before the first charge.

What is decided, and will not change:

• Flat monthly billing. Not per seat, not per connected account. Running nine accounts does not cost nine times as much.
• You are never billed for reading your own data. Analytics, search and asking the assistant questions are in the subscription however often you look.
• A few actions are counted each month. AI-built reports have a monthly number on every plan, printed on the plan card. Go past it and the work still happens, in a slower lane, rather than stopping.

There is no free plan. Prices are in US dollars, and SupahPost is available in the United States.

Payments are handled by Stripe; SupahPost never sees or stores your card details. Where a workspace has billing enabled, an admin can manage the subscription and payment method through the billing portal from inside the app. If a subscription lapses, the app locks to the billing screen rather than deleting anything — your data stays where it is.

Technical teams on Enterprise can supply their own Anthropic API key instead, in which case AI usage is billed to you by Anthropic and is not metered by us. Ask support to set that up.

Adding a teammate

An admin invites people by email from workspace settings. The invitation link works once and expires. New members start with the analytics tabs and nothing else — creating content, scheduling, publishing, managing accounts and managing users are all switched off until an admin turns them on, and scheduling and publishing are separate permissions, so someone can fill the calendar without being able to fire a post immediately. Permissions are per workspace, so the same person can be an admin in one and a limited member in another.

Forgotten password

Press Forgot password on the login screen and we email you a link to set a new one. The link is good for one use. If you are already logged in, change your password in your account settings instead. If you sign in with Google there is no password to reset — use the Google button. Still stuck: support@supahpost.com from the address on the account.

Removing one Page or Instagram account

Remove the profile from Settings › Profiles. You have to type the account's name to confirm, because removing a profile deletes all of its synced history from SupahPost — posts, insights and earnings — and a later re-add only re-syncs what the platform will still give us. Your actual Facebook Page or Instagram account is completely untouched.

Note that disconnecting Facebook and removing a profile are different. Disconnecting clears the login connection but leaves the individual accounts working. To genuinely stop an account, remove the profile.

Deleting the whole workspace

An admin can delete a workspace from settings, again by typing its name to confirm. It is immediate and it is not recoverable — there is no restore, and no undo window. It removes every record we hold for that workspace: accounts, posts, insights, earnings, scheduled posts, creations and templates, uploaded media, thumbnails, backups, users and sessions.

You are logged out on the spot. Your Facebook Pages, Instagram accounts and anything already published stay exactly as they are — deleting a workspace deletes our copy, not your social accounts. If you want a copy of anything, export it first.

You can also ask Meta to send us a deletion request from your Facebook settings; we handle that the same way and publish a status page you can check.