Scheduling social media posts across Instagram, Threads, Facebook, TikTok, Pinterest, X and LinkedIn comes down to one repeatable loop: connect each account, compose once, assign the content to a recurring slot or queue, send it for approval, and let it publish into the next open slot. The hard part isn't the calendar — it's the seven sets of platform rules hiding underneath it. Instagram won't publish from a personal account, TikTok makes you declare branded and AI-generated content, Pinterest refuses a pin without a board, and X can't fan out a multi-tweet thread from any normal dashboard. This guide walks the full workflow for all seven networks Zilfu supports, then hands you a per-platform gotchas table so nothing gets stuck in "processing" at 9am on a Wednesday.
Why schedule instead of posting live
Posting in real time scales to exactly one person with nothing else to do. The moment you run more than one account, or want to publish at your audience's peak rather than whenever you happen to be at your desk, you need a schedule. The modern best practice — endorsed by every major scheduling study — is content batching: block out one or two days, produce four to eight weeks of content at once, then drop it all into a queue that publishes on a fixed cadence. Sprout Social's batching guidance frames this as ideation, production and scheduling done in efficient cycles rather than a daily scramble, which kills the decision fatigue that wrecks consistency.
That matters because the algorithms reward reliable cadence. A mediocre slot posted every week beats a perfect slot posted erratically — the platform learns to expect you, and your audience does too. Scheduling is what turns "I'll post when I remember" into a real publishing operation, and it's the only way a small team keeps seven networks alive at once. Buffer's own queue model captures the idea: determine your optimal times, set them once, and simply add new content to the top of the queue.
The five-step scheduling workflow (every platform)
Whatever the network, the loop is identical. Master it once and you can run all seven from one screen. Here it is end to end, then we'll break down where each platform makes you do something extra.
- Connect the account. Authorize each social account once via OAuth. This is where the per-platform account requirements bite — an Instagram personal account or an un-admin'd LinkedIn Page simply won't connect for publishing.
- Compose the content. Write the post, attach media, and apply each network's per-platform settings (TikTok privacy and disclosure, Pinterest board and link, Threads topic tag). A live character counter keeps you inside each platform's limit.
- Assign a slot or queue. Either pick an exact date and time, or drop the post into a recurring weekly slot so it lands in the next open window automatically — no manual calendar juggling.
- Approve. If the post was composed by someone who needs sign-off, it waits in review until an approver (a teammate or a client reviewer) green-lights it. Approving schedules it exactly as planned.
- Publish. At the scheduled moment the post is sent to the platform's publishing API. Any optional Threads follow-up comment fires after the post goes live.
The rest of this guide is really about step 1 and step 2 — the connect and compose stages — because that's where the seven networks diverge. Get those right and the slot/approve/publish half runs itself. For how this five-step loop fits into a wider publishing operation, see the complete scheduling guide.
Per-platform gotchas: the fine print for all seven networks
Every network publishes through its own API with its own rules. Miss one and the post either gets rejected at upload or silently fails to publish. Here's the one-row-per-network breakdown of the requirements that actually trip people up in 2026.
| Network | Account / setup requirement | The gotcha that bites | Char limit |
|---|---|---|---|
| Business or Creator account linked to a Facebook Page | Personal accounts can't publish via API at all; every post needs at least one image or video | 2,200 | |
| TikTok | Account with Content Posting access | You must set privacy and disclose branded and AI-generated content; non-disclosure risks a 4-tier penalty ladder | 4,000 |
| Business account; a destination board | No board = no pin; video pins need a cover image; add a destination link or the pin drives no traffic | 500 | |
| X (Twitter) | Connected X account | No multi-tweet thread scheduling from the dashboard — single post plus media only; threads are API/MCP-only | 280 |
| A Page you administer (not a personal profile) | Publishes feed text/link, photos, video and link posts — not Reels or Stories | 63,206 | |
| Personal profile and/or company Pages you admin | Personal profile and each company Page are separate destinations with different reach behaviour | 3,000 | |
| Threads | Threads account (Instagram-linked) | One topic tag per post; supports a single auto follow-up comment, posted after the parent goes live | 500 |
Instagram: Business/Creator account + linked Facebook Page
Instagram is the network people get wrong first. You cannot schedule to a personal Instagram account — only Business or Creator accounts can publish through the Graph API, and the account has to be linked to a Facebook Page because permissions flow through that Page. If your scheduler says it can't connect, this is almost always why; switch the account type in the Instagram app first. Every Instagram post also needs at least one image or video — there's no text-only post — and a single video publishes as a Reel. Meta caps API publishing at 100 posts per rolling 24 hours, which no normal schedule comes close to. Meta's content-publishing docs spell out the two-step container-then-publish flow your scheduler handles for you.
TikTok: disclosure flags for branded and AI content
TikTok's Content Posting API makes you declare more than any other network. For each post you set a privacy level (public, friends, followers, or private), choose whether viewers can comment, duet or stitch, and — critically — toggle content disclosure when the post promotes a brand, product or service. The branded-content toggle only works for new posts and forces public or friends visibility. Separately, TikTok's 2026 synthetic-media rules require you to flag AI-generated content — synthetic faces, voice clones, AI backgrounds, or photorealistic AI product shots. Skipping disclosure isn't a soft warning anymore: TikTok runs a four-tier penalty ladder (warning → 7-day posting restriction → 30-day suspension → permanent ban). A good scheduler surfaces these toggles at compose time so you declare once and move on. See the 2026 disclosure rules for the full label taxonomy.
Pinterest: pins need a board and a destination link
Pinterest is the only network where the destination is mandatory metadata, not an afterthought. Every pin requires a board — pick it before you publish or the API rejects the pin outright. You also get a pin title (up to 100 characters) and an optional destination link, and you should always set the link: a pin without one looks pretty but drives zero traffic, which defeats the point of Pinterest as a discovery-to-click engine. If you're publishing a video pin, it needs a cover image for the thumbnail. One naming note: Pinterest's "Idea Pins" no longer exist — they were folded into standard video Pins back in 2023–2024, so ignore any old guide that tells you to create one.
X (Twitter): no dashboard thread scheduling
Here's the one that surprises people: you cannot schedule a multi-tweet thread as a single unit from a normal posting dashboard. The in-app composer publishes one post per network — text up to 280 characters plus media — and that's it. If you want a chained X thread (parent tweet → reply → reply), that lives at the API level via parent_id chaining, or through an MCP server driving the same endpoints. When a single idea runs past the 280-character cap, the cleanest fix is to split it into a numbered thread before you queue it. In Zilfu specifically, multi-post X threads are an API/MCP feature, not a dashboard one. The timing trick that does work from the dashboard on X: keep your link out of the main post and the reach holds up better — though note that on Zilfu the automatic follow-up comment is currently a Threads feature, not an X one.
Facebook: feed, photos, video and links — not Reels or Stories
Facebook publishing runs against Pages you administer, never a personal profile. What a scheduler can post is narrower than the app suggests: feed text and link posts, single and multi-photo albums, and native video. It does not publish Facebook Reels or Stories through the standard publishing flow, so don't plan a Reels-only Facebook strategy around a scheduler — those still need the native app. When you connect, you pick exactly which Pages to import, and each Page becomes its own account you can publish to in any combination.
LinkedIn: personal profile vs company Page
LinkedIn is two products wearing one login. Your personal profile and each company Page you admin are separate publishing destinations, authorized in one step but behaving differently: personal posts generally see stronger organic reach, while Page posts are better for brand consistency and analytics. Decide per post which one you're speaking as — a founder's take usually belongs on the personal profile, a product announcement on the Page. When you connect, import one, several, or all of the profiles and Pages you have rights to, and treat each as its own account.
Threads: a single follow-up comment
Threads shares Instagram's account graph but has its own rules. You get one topic tag per post (no # symbol needed) to surface in that topic's feed, and Threads is the network where Zilfu's scheduled follow-up comment lives today: write one comment at compose time, choose how long to wait after the parent publishes (presets from 5 minutes up to 2 hours, schedulable up to 7 days out), and it posts itself once the parent is live. If the parent never publishes, the follow-up is automatically skipped. This is the cleanest way to keep a call-to-action link out of the main post — a documented reach tactic — without doing it by hand.
Step-by-step: schedule a post across all seven networks
Now the concrete walkthrough. This is the exact connect → compose → slot → approve → publish loop, written so it works whether you're scheduling to one network or all seven at once. Do it once and the per-platform settings above slot naturally into step three.
- Connect each account once. Authorize every social account via OAuth. Watch the per-platform requirements: Instagram needs a Business or Creator account linked to a Facebook Page, Facebook needs a Page you administer (not a personal profile), and LinkedIn lets you import your personal profile and any company Pages you admin as separate destinations. Connect once and the accounts stay linked.
- Compose the post and attach media. Write your content with a live character counter so you stay inside each network's limit (X 280, Threads and Pinterest 500, Instagram 2,200, TikTok 4,000, LinkedIn 3,000, Facebook 63,206). Attach images or video — required on Instagram, TikTok and Pinterest, optional elsewhere. Pick which accounts the post should go to; a single multi-account post counts once against your monthly limit.
- Apply each platform's settings. This is where the networks diverge. On TikTok set privacy, comment/duet/stitch permissions, and disclose branded or AI-generated content. On Pinterest choose a board (required), add a pin title and a destination link, and a cover image for video pins. On Threads add a topic tag and, if you want, a single follow-up comment timed after the parent goes live. Instagram, Facebook, LinkedIn and X publish from the shared content with no extra card.
- Assign a recurring slot or an exact time. Either pin the post to a specific date and time, or drop it into a recurring weekly slot so it publishes into the next open window for that network automatically. Define each network's good windows once — Facebook Thursday 9am, LinkedIn Wednesday 4pm, Pinterest Saturday evening — and the queue keeps your cadence consistent without re-picking times every week.
- Send for approval if needed. If the post was composed by someone who needs sign-off, it waits in review instead of going live. An approver — a teammate with the Approve posts permission or a client invited as a free reviewer — approves, requests changes, or comments. Approving schedules the post exactly as the author intended, and internal notes stay hidden from client reviewers.
- Let it publish and check results. At the scheduled moment the post is sent to each platform's publishing API, and any Threads follow-up comment fires after the post goes live. Afterwards, review reach, likes, comments and saves per post in the analytics view to refine which slots earn their place — drop the weakest windows, double up on the best.
After the first cycle you'll rarely touch steps one or four again — accounts stay connected and your slots are already defined, so day-to-day scheduling collapses to compose, drop into queue, done.
Recurring slots vs one-off scheduling
There are two ways to put a post on the calendar, and the difference matters for how much manual work you sign up for.
- One-off scheduling pins a post to an exact date and time. Use it for time-sensitive content — a launch, an event, a reaction. The cost is that you're picking a moment by hand every single time.
- Recurring weekly slots are the batching workflow's secret weapon. You define each network's good windows once — say Facebook Thursday 9am, LinkedIn Wednesday 4pm, Pinterest Saturday evening — then drop content into a queue and each post flows into the next open slot for that network automatically. This is how you maintain a consistent cadence across seven platforms without re-picking times every week.
The practical move is to use slots as your default and one-off scheduling for the exceptions. If you're unsure what windows to set, our companion guide on the best time to post on social media gives a per-network starting point, and the per-platform timing guides (linked from there) go deeper. Set those as your slots, then let your own reach data narrow them over a couple of weeks.
Building approval into the schedule
For anyone publishing on behalf of a client or a wider team, "schedule" and "approve" are the same step. A clean approval workflow means a post composed by a junior, a freelancer, or a client-side contributor doesn't go live until the right person signs off — and it does so without email threads or spreadsheets. Sprout Social frames a centralized approval system as what gives everyone confidence: one place to review, one clear expectation.
In Zilfu, this is built into the same compose flow. Members who need sign-off compose exactly like everyone else; when they save, the post goes to review instead of going live. An approver — a teammate with the Approve posts permission, or a client invited as a free reviewer — approves, requests changes, or comments. Approving schedules the post exactly as the author intended. Reviewers can't compose, publish, connect accounts or change settings, and internal notes stay hidden from them automatically, so you can bring a client right into the workspace without exposing your back-office chatter. Approvals and free reviewers are on every tier, including the free plan.
Flat, unlimited accounts vs per-channel pricing
Most schedulers meter you in one of two ways: per social account (you pay more as you connect more) or per seat (you pay more as your team grows). Both punish exactly the workflow this guide describes — running many accounts across seven networks with a few collaborators.
Zilfu's model is deliberately flat. You connect unlimited accounts per network in a single workspace at no extra charge, every feature is unlocked from signup, and pricing is per plan rather than per seat — so you can invite as many teammates and free client reviewers as you want without the bill moving. That's the structural difference from a per-channel tool: if you're weighing Zilfu against a metered competitor, our Zilfu vs Buffer comparison lays out where flat, everything-included pricing changes the math for agencies and multi-location brands. The free plan covers 20 posts a month across up to two accounts — enough to run the whole connect-compose-slot-approve-publish loop on a couple of networks before you ever pay.
How Zilfu runs all seven schedules from one queue
The reason teams abandon multi-platform scheduling is that doing it by hand means tracking seven different sets of rules and seven different calendars every week. Zilfu collapses that into one workflow. You compose once, apply each network's per-platform settings inline — TikTok privacy and disclosure, Pinterest board and link, Instagram media, Threads topic tag — and drop the post into recurring slots or an exact time. A live character counter applies each network's own limit when you publish, so a 1,200-character LinkedIn thought doesn't get silently truncated on X.
Because every account lives in one workspace, a single multi-account post counts once against your monthly limit no matter how many networks it hits. After posts run, the analytics view shows reach, likes, comments and saves per post — for impressions, CTR or a computed engagement rate, you'll want each platform's native analytics or our free engagement-rate calculator, since the dashboard deliberately doesn't invent numbers it can't verify.
For automated stacks, the same scheduling logic is available programmatically: push posts into the queue — including chained X and Threads threads via parent_id — through Zilfu's full REST API and MCP server, with webhooks to notify your systems when a post publishes. And the link-in-bio page gives you a hosted home for the destination links that platforms penalize in the main post. Honest scope note: Zilfu doesn't import your posting history, doesn't AI-write captions for you, and isn't a social inbox — it's a scheduler and publisher, and it does that across all seven networks without metering your accounts.
Ready to set it up? Start on the pricing page — the free plan is enough to schedule across two networks today — or skim the per-network detail on the Instagram and X channel pages first.
Frequently asked questions
How do I schedule social media posts across multiple platforms at once?
Use one repeatable loop on every network: connect each account once, compose the post, assign it to a recurring slot or exact time, approve it if sign-off is needed, and let it publish. A scheduler that holds all your accounts in one workspace lets you compose once and apply each platform's settings inline, so you're not opening seven apps. The differences between networks live in the connect and compose steps, not the calendar.
Why won't my Instagram account connect to a scheduler?
Almost always because it's a personal Instagram account. Only Business or Creator accounts can publish through Instagram's API, and the account must be linked to a Facebook Page because permissions flow through that Page. Switch the account type in the Instagram app, link it to a Page, then reconnect. Every Instagram post also needs at least one image or video — there are no text-only posts.
What does TikTok require me to disclose when scheduling a post?
Two things in 2026. First, if the post promotes a brand, product or service you must enable content disclosure (which forces public or friends visibility). Second, TikTok's synthetic-media rules require you to flag AI-generated content — synthetic faces, voice clones, AI backgrounds, or photorealistic AI product shots. Skipping disclosure can trigger a four-tier penalty ladder from a warning up to a permanent ban, so declare it at compose time.
Why does my Pinterest pin fail to publish?
A Pinterest pin requires a destination board — without one the API rejects it. Pick the board before publishing. You should also add a destination link, or the pin drives no traffic, and video pins need a cover image for the thumbnail. Note that "Idea Pins" no longer exist — they were folded into standard video Pins in 2023–2024, so ignore older guides that reference them.
Can I schedule a multi-tweet X (Twitter) thread from a dashboard?
Not as a single unit from a normal posting dashboard. The in-app composer publishes one X post — text up to 280 characters plus media — at a time. Chained threads (parent tweet → reply → reply) live at the API level via parent_id chaining, or through an MCP server. In Zilfu, multi-post X threads are an API/MCP feature, not a dashboard one.
Can I schedule Facebook Reels or Stories?
No — not through the standard publishing flow. Facebook scheduling covers feed text and link posts, single and multi-photo albums, and native video, published to Pages you administer (not a personal profile). Facebook Reels and Stories still need the native app, so don't build a Reels-only Facebook plan around a scheduler.
What's the difference between scheduling to a LinkedIn profile and a company Page?
They're two separate destinations authorized in one step. Your personal profile generally sees stronger organic reach and suits a founder's personal take; each company Page you admin is better for brand consistency and Page analytics. Decide per post which one you're speaking as, and treat each imported profile or Page as its own account.
How do recurring slots differ from picking an exact time?
One-off scheduling pins a post to a specific date and time — good for launches and reactions, but you choose a moment by hand every time. Recurring weekly slots let you define each network's good windows once (e.g. Facebook Thursday 9am, LinkedIn Wednesday 4pm), then drop content into a queue so each post flows into the next open slot automatically. Slots are the better default for a consistent cadence across seven platforms.
Can clients approve scheduled posts before they go live?
Yes. In Zilfu you can invite a client as a free reviewer: they review and approve (or request changes) right alongside your team, but can't compose, publish, connect accounts or change settings, and your internal notes stay hidden from them. Approving a post schedules it exactly as the author intended. Approvals and free reviewers are available on every tier, including the free plan.
Does Zilfu charge per social account?
No. You connect unlimited accounts per network in a single workspace at no extra charge, and pricing is per plan rather than per seat — so inviting teammates and free client reviewers doesn't move the bill. That's the structural difference from per-channel tools; our comparison pages and the Zilfu vs Buffer breakdown show where flat pricing changes the math for agencies and multi-location brands.
Which platforms support an automatic follow-up comment?
Today the scheduled follow-up comment is a Threads feature in Zilfu. Write one comment at compose time, choose how long to wait after the parent publishes (presets from 5 minutes up to 2 hours, schedulable up to 7 days out), and it posts itself once the parent goes live. If the parent never publishes, the follow-up is skipped. It's the cleanest way to keep a call-to-action link out of the main post.
What analytics does Zilfu show after a post publishes?
The dashboard surfaces reach, likes, comments and saves per post. For impressions, clicks, CTR or a computed engagement rate, use each platform's native analytics or our free engagement-rate calculator — the dashboard deliberately doesn't invent metrics it can't verify from the platform.
Can I schedule posts programmatically instead of in the dashboard?
Yes. The same scheduling logic is available through Zilfu's full REST API and MCP server, including chained X and Threads threads via parent_id, with webhooks to notify your systems when a post publishes. It's the same queue and the same per-platform rules — just programmatic input instead of the compose screen.
Does Zilfu write captions or import my old posts?
No on both. Zilfu is a scheduler and publisher — it doesn't AI-write captions or content for you, doesn't import your posting history, and isn't a social inbox or DM tool. What it does do is run the connect-compose-slot-approve-publish workflow across all seven supported networks (Instagram, Threads, Facebook, TikTok, Pinterest, X and LinkedIn) without metering your accounts.