How to schedule posts at the best time with an automation (without made-up best times)

By Ranjit Bhinge, founder of Blur Studio · Updated · 7 min read

Short answer: There is no best time to post that works for every account, so there is no single time to copy. Instead, set a small number of weekly time slots, let your automation drop each approved post into the next free slot, and run a 4 week test that compares slots on your own numbers. Blotato, a software subscription that publishes to 11 social networks, supports slots you define and a next-free-slot option, but its documentation does not suggest times for you.

Ranjit Bhinge

Every article about the best time to post gives you a different answer, and none of them has seen your audience. Here is how to find your own, using an automation to do the boring part.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Posting time matters less than most guides suggest, and it matters differently for each account. A restaurant with a lunch crowd, a B2B consultant with an office audience and a night owl gaming page do not share a clock. The reliable path is a controlled test on your own account. This guide shows how to build one: slots, automation, a four week plan and a decision rule. It uses Blotato for the scheduling fields, but the test design works with any tool.

This page may contain affiliate links from which Blur Studio earns commissions.

Why there is no universal best time

  • Blotato's documentation gives no recommended posting times. Its help center has growth tips on how many posts a day to aim for, but those are one creator's opinion, not data from your account.
  • Posting-time studies you find online are usually from one tool's customers, in one period, with one mix of industries. Treat them as ideas for what to test.
  • Your audience's time zone, your content type (short video, text, carousel) and the day of the week all change the answer.

So the useful question is not "what is the best time" but "which of my candidate times beats the others on my own account, by enough to matter".

Slots versus fixed times

Two ways to schedule, both supported through Blotato's publish request:

MethodHowGood forWatch out
Fixed timeSend scheduledTime, an ISO 8601 timestamp with a timezone offset, at the top level of the request.A launch or event with an exact time.Your automation must do time zone and daylight saving maths.
Weekly slotsDefine slots (for example Tuesday and Thursday at 9:00) in the Blotato calendar or through the slots calls, then send useNextFreeSlot: true.Steady weekly posting. The automation does not need a clock.The slot must match the platform, account and Page or channel, or the call fails.

Rules from Blotato's reference that bite:

  • Pick one method per request. Setting both a time and useNextFreeSlot still runs the slot check and fails if no slot matches. Do not combine them.
  • These two fields sit at the top level, next to post. If you put them inside post they are ignored and the post goes out at once.
  • If you send neither, the post publishes immediately. A scheduled post is not a draft: it publishes at its time.
  • The API parses and returns scheduled times in UTC (the world time standard) and has no separate time zone field, while the web calendar has its own timezone setting. Convert your local time with the correct offset for that date, and check your times again after each clock change.
  • Blotato lists slot management as REST only (the slot calls are GET /v2/schedule/slots and POST /v2/schedule/slots/next-available), not as an MCP tool. The calendar in the web app also has slots.

A request that uses the next free slot looks like this. The IDs are placeholders.

{
  "post": {
    "accountId": "YOUR_ACCOUNT_ID",
    "content": {
      "text": "Post text goes here",
      "mediaUrls": [],
      "platform": "twitter"
    },
    "target": {
      "targetType": "twitter"
    }
  },
  "useNextFreeSlot": true
}

And one with a fixed time. The offset must match your time zone on that date.

{
  "post": {
    "accountId": "YOUR_ACCOUNT_ID",
    "content": {
      "text": "Post text goes here",
      "mediaUrls": [],
      "platform": "twitter"
    },
    "target": {
      "targetType": "twitter"
    }
  },
  "scheduledTime": "2026-12-01T09:00:00-05:00"
}

Both return a submission ID. When you look it up, a scheduled post returns the status scheduled with its time, and that means queued, not published. Use the status check in fix silent failures so your sheet never marks a queued post as posted.

Use your own data first

Before you test anything, look at what you already have.

  1. Open each platform's own audience insights for when your followers are active. Treat that as a source of candidate times, not as the answer.
  2. List your last 20 posts with posting time and reach or views. If posted times barely vary, you have no data on timing yet, which is why the test below exists.
  3. Note where your audience lives. Posting at 9:00 your time means something else to followers in another time zone.

Blotato's own analytics are limited by plan: Starter gets 4 updates per post over 30 days (day 1, 7, 14 and 30), Creator 18 updates and Agency 20 updates over 90 days. LinkedIn, Slack and Discord return no metrics through it, and very recent posts may have no numbers yet because analytics refresh in the background. For timing tests, read the numbers at a fixed point, such as day 7, and read them inside each platform's own insights if the Blotato figures are missing. See Blotato analytics: what you can see.

The 4 week test

The goal is to compare a few time windows fairly. Use made-up numbers below as a model.

  1. Choose 4 candidate windows per platform. For example 8:00, 12:00, 17:00 and 20:00 local audience time, each as a weekly slot.
  2. Post 5 times a week for 4 weeks on one platform. That is 20 posts. Each window gets 5 posts.
  3. Randomise the order. Do not put all the 8:00 posts in week one. Spread each window over all four weeks and across weekdays, so a holiday or a viral moment does not decide the result.
  4. Keep content comparable. Same content types and same quality in each window. If one window gets all the carousels, the test measures carousels.
  5. Measure at the same age. Read reach or views for every post at day 7, and divide by followers if your follower count changed a lot.
  6. Compare medians, not averages. A single viral post wrecks an average.

Weekly slots fill in calendar order, because useNextFreeSlot: true takes the earliest matching free slot. So you cannot assign a post to a particular window with that option. To randomise, shuffle the order of your content rows and keep the content types balanced, or send a fixed scheduledTime chosen from a shuffled list of windows. Either way, the automation fills the slot and you only keep the log.

A decision rule I would use (my rule of thumb, not a statistical standard): a window wins only if its median is at least 20 percent above the second best, and at least 3 of its 5 posts beat the second best window's median. If no window clears that, timing is not your problem, and you should spend the effort on content instead. Twenty posts is a small sample, so repeat the test in another season before treating the result as settled.

Log template

DatePlatformContent typeWindowSubmission IDStatusPublic URLDay 7 reachNotes
2026-12-01InstagramReel08:00(filled by the automation)published(filled)(you type)Public holiday

The sample row is just a format. Fill your own.

Adjust

  • If a clear winner appears, set your weekly slots there and keep one slot in the second best window as a control.
  • If results are mixed, keep two windows and test again with different content.
  • Re-test every quarter, and after big changes: new audience, new content type, daylight saving changes.
  • Do not let the automation fill every slot. A post that is not ready should leave a slot empty, not go out weak.

Mind the limits. Blotato queues up to 200 scheduled posts on Starter, 1,000 on Creator and 3,000 on Agency, and each platform has its own daily caps, so check the live limits before you pack slots. The scheduling horizon differs between Blotato's pages: the help centre says 9 months on every plan, while its rate card dated 10 September 2026 lists more on higher plans and the main pricing page lists none. Plan on 9 months, and try one test post 10 months out if you need more.

What other tools do

Some schedulers show suggested posting times based on your own account history. Later, for instance, lists best time to post features for Instagram, Facebook and TikTok on its own pricing page. If you want the tool to suggest times, compare that with Blotato's slots in Blotato versus Later. A suggestion from a tool is still a starting hypothesis. The test above is how you confirm it.

Who should skip it

Skip Blotato for this job if you want the tool to suggest times from your history, because its documentation describes no such feature. Later lists one on its plans page.

  • Accounts that post fewer than 3 times a week. The test takes too long to give a signal.
  • Time-bound businesses such as restaurants and events, where the right time is set by the offer, not the algorithm.
  • Anyone whose reach problem is content, not clock. If every window gets near zero, change the content first.

You can look at the plans on Blotato's site. The API route needs a paid Blotato plan. Starter is $29 a month billed monthly as of November 2026. The web app calendar can do slots without the API, and the 7 day trial includes the web app but not the API.

How this page was checked

The facts come from Blotato's publish-post reference, its scheduling and limits pages, its analytics page and pricing page, and Later's plan page. Last checked 21 November 2026, refreshed every 90 days. Blur Studio has not run Blotato itself, so the test plan is yours to run. Blotato's docs give no best time, and nothing here is an earnings or reach promise.

How I'd approach this

Week 0: write down your four candidate windows and make the log. Week 1 to 4: run the test with a shuffled slot column and read each post at day 7. Week 5: apply the decision rule and set your permanent slots. If you do not want to build any of this, schedule by hand into two slots and spend the time on better posts. For a plain plan to keep a weekly rhythm, see social media content in two hours a week. A free AI brainstorm call can help you set up the test, and the free AI tools need no payment.

Questions people ask

What is the best time to post on social media?

It differs by account, audience and content type. Blotato's docs give no time that works for everyone, and neither does this guide. Run the 4 week test on your own numbers.

What does useNextFreeSlot do in Blotato?

It schedules the post at the next slot you defined for that platform, account and Page or channel. It fails if no matching slot exists. Do not send it together with a fixed time.

Why did my scheduled post go out immediately?

Blotato's reference says scheduling fields must be at the top level of the request, next to the post object. Inside the post object they are ignored and the post publishes at once.

Can an AI choose the best time for me?

It can suggest candidates, but the answer has to come from your own results. Some schedulers suggest times from your history. Blotato's documentation describes no such suggestion.

How many posts do I need to test timing?

The plan above uses 20 posts over 4 weeks with 4 windows. That is a small sample, so treat the result as a lead and repeat the test later.

Which time zone do slots use?

Blotato's API parses and returns scheduled times in UTC, and the web calendar has its own timezone setting. Re-check your local audience time after each daylight saving change.

Does scheduling change reach compared with posting live?

Platform documentation lists no reach penalty for approved scheduling, but that is an absence of mention, not proof. Compare a few live posts with scheduled ones in your own log. See Blotato pricing explained for plan limits.

More in this topic: Social media: automation with n8n, Make and Zapier (27 guides) →

Sources

Ready for the next step?

A free 15-minute AI brainstorm. We find 3 broad areas where AI could help your business.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.
Book a free AI brainstorm call

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…