Automate Instagram Posts, Reels and Stories

Here is the test that settles it. Schedule one post for ten minutes from now, leave your phone face down in another room, and come back in twenty. If the post is live, you bought automation. If a notification is waiting and the caption is sitting in your clipboard, you bought a reminder app with a calendar view.

That difference is the whole subject. You can automate Instagram posts, Reels and Stories without touching a phone, but only under conditions plenty of tools quietly fail to meet. Below: what publishes, the account type that gates it, the format limits that bite, and how to verify on your own account before you commit a quarter’s content to a queue. If you want the wider picture first, start with automating posting everywhere at once.

Auto-publish versus reminder

Reminders are not laziness on the vendor’s part. They exist because a platform’s API either cannot publish a format or will not publish it for that account, and a notification is the honest fallback. Instagram is a good case: its API publishes more than most people assume, and tools fall back anyway.

Instagram’s content publishing documentation covers single images, single videos, Reels, Stories and carousels of up to 20 items. All five publish without anyone touching a phone. So when a tool offers you a reminder for Instagram Stories, the API is not the blocker. The tool simply has not built that path, or has not asked you for the permission it needs. Stories are the one honest exception, for a reason covered below.

Four ways to tell before you pay:

• Read the format table, not the network list. Support is per format. A tool can auto-publish feed images and Reels and still only remind you for Stories and carousels.
• Search the pricing and help pages for the words. “Reminder”, “notification”, “push to publish” and “manual publishing” are the giveaways, usually in a footnote rather than the feature grid.
• Watch what account type it asks for. API publishing requires an Instagram professional account. A tool happy to connect a personal account is not publishing through the API, which leaves a reminder or something worse.
• Run the ten-minute test on the trial. Every tool worth buying has a trial long enough, and one post answers a question no feature page answers honestly.

The distinction decides which tool you buy. If you are still choosing, the tool comparison splits the field on exactly this.

The account type requirement

Instagram’s publishing API works on professional accounts, which means Business or Creator. A personal account cannot be published to, and no tool can route around that. This is the single most common reason scheduling fails, and it usually fails at connection time with an error message vague enough to look like a bug.

The second gate is the connected Page, and it catches far more people. Where a professional account is connected to a Facebook Page that requires Page Publishing Authorization, Instagram says publishing fails until that authorization is completed. Meta is blunt about the awkward part: there is no way for an app to tell in advance whether a given Page requires it, so the documentation recommends completing it preemptively. Do it on day one rather than at 7am on a launch day. For the Page side, see the Facebook guide.

Two more conditions sit on the same Page relationship. Your user must be able to perform the MANAGE or CREATE_CONTENT tasks on the linked Page, so an editor-level role is not always enough. And if that Page requires two-factor authentication, the Facebook user behind the connection must have completed two-factor too, or the request fails.

What does converting change? Less than the forum threads suggest. The documented difference is capability: a professional account gets the publishing endpoints, insights and the Page relationship, and you switch back in the app’s settings. The widely repeated claim that Business accounts lose access to parts of the audio library does not appear on any first-party page I could find, so treat it as folklore and test it on your own account. As part of automating social media end to end, the account switch is the cheapest step and the one everything else waits on.

What each format supports

Every figure below comes off Instagram’s own developer pages, checked October 2026.

Format	Auto-publishes	Ratio and limits that bite
Feed image	Yes	JPEG only, 8MB maximum, ratio within 4:5 to 1.91:1, width 320 to 1440
Feed video	Yes	Same container rules as Reels
Carousel	Yes	Up to 20 images, videos or a mix. Every item is cropped to the first item’s ratio, default 1:1. Reels cannot be carousel items
Reel	Yes	300MB maximum, 9:16 recommended, accepted ratio anywhere between 0.01:1 and 10:1, 23 to 60 FPS
Story (image)	Yes	JPEG, 8MB maximum, 9:16 recommended. No link, poll or location stickers
Story (video)	Yes	100MB maximum, 60 seconds maximum, 3 seconds minimum, 9:16 recommended

The feed ratio window is narrower than the app suggests. 4:5 is the tallest frame the API accepts, which is why 1080×1350 is the default tall feed size. The maximum width is 1440, so a 1080-wide export passes through untouched.

Carousels crop to the first slide. Put a 4:5 slide first and a square one second and the square gets letterboxed or trimmed. Build the set at one ratio, because the API gives you no per-item framing control. Anyone cutting one shoot into several formats hits this constantly, which is where best content repurposing tools earn their keep.

Stories publish, but naked. Instagram’s media reference states that publishing stickers, specifically link, poll and location, is not supported, while mentioning users without a sticker is. So if your Story playbook is link stickers and polls, the API cannot deliver it and a reminder is the correct answer rather than a cop-out. Decide which Stories are reach plays, which can be automated, and which need a thumb.

Reel length: the sources disagree

Do not code a hard cut at one number, because Instagram’s own pages do not agree. The developer reference for creating media gives Reels 15 minutes maximum, 3 seconds minimum. The help centre article on recording a reel says you can record and edit videos up to 20 minutes. A 60-second maximum also circulates and still surfaces as a help-page title in search results, though the help page behind it does not carry that figure.

If your pipeline has to validate against something, use the developer reference’s 15 minutes, because that is the page governing API publishing. That is a build decision, not Instagram’s maximum, and the gap between the two pages is real. The more useful line from the same help article is a distribution note rather than a limit: reels over three minutes will not be recommended to new audiences. That is the threshold that matters for reach, and it sits well below any of the duration figures. 9:16 is only a recommendation, not a requirement: a horizontal clip will publish and look exactly as bad as you expect. Vertical discipline is the habit the TikTok guide argues for.

The posting limit, and Instagram contradicting itself

This is worth reading twice. Instagram’s content publishing guide states in its rate limit section that accounts are limited to 100 API-published posts within a 24-hour moving period, and that carousels count as a single post. Further down the same page, in the carousel section, it states that accounts are limited to 50 published posts within a 24-hour period, and again that a carousel counts as one.

Same page, same day, two numbers. I have no way to tell which one enforcement actually uses, and neither does your scheduler. Our call: plan against 50. If 50 posts a day is not enough, the problem is your content strategy, not your rate limit, and the cost of guessing the other way is a queue that silently stops publishing mid-afternoon. You can check where an account stands by querying the content_publishing_limit endpoint, the one API call worth wiring into any dashboard you build.

Two related caps come from the media reference rather than the publishing guide. Containers expire after 24 hours unpublished, and an account can create only 400 containers in a rolling 24 hours. Both bite the moment you pre-build a week of posts in one batch job.

One number you will see quoted is not Instagram’s: the scheduling window. Instagram’s publishing endpoints take no scheduling parameter. Your tool holds the post and fires the call at the chosen minute, which makes the window, anything from a few minutes ahead to roughly 90 days on the vendor pages we reviewed, a property of the tool you bought. Those vendor figures were read off marketing pages rather than tested, so check yours.

How to automate Instagram posts, start to finish

All of it takes about an hour of setup. Six steps, and the fifth is the one everybody skips.

1. Convert the account to professional in Instagram’s settings, Business or Creator, then connect it to the Facebook Page you will use.
2. Complete Page Publishing Authorization on that Page before you connect anything, and confirm your own role can perform MANAGE or CREATE_CONTENT. If the Page enforces two-factor, finish two-factor on your Facebook user too.
3. Connect the tool and read back what it says. It should name the account, identify it as professional, and list which Instagram formats it publishes rather than reminds. If it cannot tell you that, stop there.
4. Schedule one of each format, ten minutes apart. A JPEG feed image at 1080×1350. A two-item carousel, both items at the same ratio. A 9:16 Reel under 300MB. One Story. Four posts, under an hour, and you know what you actually bought.
5. Verify in the Instagram app, not in the tool’s calendar. A green tick in a scheduler means the API returned a success, which is not the same as the post looking right. Check that the Reel landed in the Reels tab, that the carousel cropped the way you expected, and that the caption kept its line breaks. If your tool surfaces a container status, ERROR and EXPIRED are the two values that mean it did not work.
6. Build the calendar against 50 posts a day and hashtags you have counted. Captions take 2,200 characters, 30 hashtags and 20 mentions, all documented. How many you should use is convention, never published first-party, so pick a count and test it. If you park hashtags in a first comment, check whether the tool publishes that comment itself or only reminds you. Same question as the rest of this page, on the habit most people have.

One more thing from the test: video uploads are asynchronous, so a container ID is not proof the upload worked. Instagram recommends polling a container’s status once a minute for no more than five minutes. A tool that marks a Reel scheduled and never looks again is where silent failures come from.

Automating from an agent

If an AI agent or a script is doing the posting, you have two routes, and both have the same shape: upload the media, then create the post.

Going direct to Instagram is a two-call sequence. You create a media container at the media endpoint, passing the media URL and, for anything but a single image, a media type of REELS, STORIES or CAROUSEL. Then you publish that container by its ID. Large videos get a resumable upload session, which pushes the file to Meta’s upload host first. Either way the media must sit on a publicly reachable server, because Instagram fetches it.

The container lifecycle trips up agents. A container is good for 24 hours and you get 400 a day, so an agent pre-building a fortnight of content will expire most of them and burn the budget doing it. Build containers near publish time, not planning time.

The other route is a scheduler that exposes an API or an MCP server, which is what most people should use. SchedPilot is the clearest example: its MCP server exposes eight tools, including upload_media and create_post, and because SchedPilot holds the platform OAuth, your agent carries one key instead of a Meta app, a Page token and a permissions review. It also has an explicit human approval step before publish. Its honest drawback is cost structure rather than capability: there is no free tier, only a seven-day trial that asks for a card, and the AI features are metered in credits.

Whichever route you take, put a human gate in front of publish. An agent with publish authority and a 50-a-day budget can produce a week of embarrassment in minutes, and the API’s reference says the delete operation “is not supported”, so the cleanup is manual, one post at a time or through the app’s own multi-select. The same holds on every network, which the LinkedIn guide covers at more length.

What not to automate

Publishing is automation. Engagement is impersonation, and that is where accounts get hurt.

Leave comment replies, direct messages, follow and unfollow cycles and anything resembling an engagement pod alone. Not because the API makes them hard, but because they are the behaviours platforms hunt for and the output is weak even when it works. A generic reply under a customer complaint costs more than silence would.

Be precise about what Meta actually says, because most pages on this subject are not. Meta’s spam policy describes “Posting, sharing, engaging with content… either manually or automatically, at very high frequencies”. The rule is frequency-based, not a ban on automation. Manual activity at a high enough rate is covered by the same sentence. The next line matters more: Meta reserves restrictions for accounts acting at lower frequencies too, where either other indicators of spam, repetitive content among them, or signals of inauthenticity are present. Repetitive content is what a queue produces, so our reading is that staying under a frequency is no defence. Meta also documents no equivalent of X’s explicit line prohibiting automated likes, so do not assume one exists or let anyone quote one at you.

Rate and pattern are the risk, not the tool. A queue publishing four times a week looks like a person who plans ahead. A script firing follows, likes and templated comments at machine speed looks like what it is, and randomised delays do not fix the pattern.

So the decision comes down to this. Convert to a professional account, complete Page Publishing Authorization before you need it, and buy a tool that auto-publishes every format you use rather than one that reminds you about the awkward ones. Build the calendar against 50 posts a day and run the ten-minute test on the trial before you pay for a year. Automate the publishing, keep the replies, the DMs and the Story stickers in human hands, and spend the time you saved on the one thing no API will do for you: deciding what to post.