Scheduled Posting on TikTok: Let It Publish While You Sleep

Last winter a friend who sells home goods complained that he was setting a 3am alarm every day so he could post TikTok in batches.

I thought it was about shipping. He corrected me. It was about videos. He wanted them to go out on their own at the set time, and he did not know where to start, so he had been doing it himself.

His accounts are mainly in the United States. The content is American home scenes, so posts have to land in that evening. 3am here is evening there. He had tried posting in the daytime. The numbers were clearly worse, so he settled on getting up in the middle of the night. After two months of that, he was worn out.

I asked how long one post takes. Under two minutes, he said. The problem is that those two minutes have to land at 3.

Scheduled posting is two pieces, and the time is worked backwards

Posting on its own at a set time splits into two pieces.

The first is fixing the actions. Open TikTok, tap the plus, pick a video from the album, fill in the text, add hashtags, choose a cover, tap publish. Save that chain as a template you can run again. Once that is done, you press once and it runs. You do not have to think it through again.

The second is attaching a time. At a chosen moment, start that template once.

Get the flow running steadily first, then add the time. Reverse the order and the next morning you only have a failure record, with no sign of which step stopped.

An overseas account differs from a domestic platform in the time zone. On a domestic platform you can think in your own zone. With an overseas account, your evening may be the user’s morning, and your morning may be their late night. When you set the time, work out when the user is scrolling, then convert that back to your clock.

1. Decide which market the content is for. People there usually scroll in their evening.
2. Convert that moment into your own time zone.
3. The moment you get is the time to enter in the schedule.

My friend’s accounts target the United States. “8pm US Eastern” converts to about 9 in the morning here, which is his normal working day. He skipped that step at first. He assumed it had to go out in the middle of the night, and that is what put him on the alarm.

Do that conversion and a lot of posts that looked like overnight work actually land in the daytime.

Three checks on the phone, then how to describe the chain

The time answers when to post. You still have to confirm which machine runs it. Three checks, in order.

First, the workstation is installed. Follow the install selection page. If the conversation page can send one instruction to the target phone, the chain is live.

Second, the phone is in the list and has a name. On the Devices page, do four things: scan, add, alias, group. Do not skip the alias. When several accounts cover different markets, “US account 1” in the list and a string of random characters are a different amount of work later.

Third, an offline device can be seen and cannot be run. At the set time, the phone has to be online.

The computer that runs the schedule cannot sleep. Scheduling happens on your own machine. There is no cloud waiting behind it. Turn sleep and automatic updates off.

How well you describe the flow decides how smoothly the rest goes.

On the conversation page, start a new conversation, select the phone, and explain the whole job the way you would to a colleague. The first time, switch to refinement. It will ask back about the details you left out, such as which album item to start from, whether the sound should be named, and whether to return to the home feed after posting.

A description you can edit:

Open TikTok, tap the plus at the bottom, choose the newest video in the album, tap next, put the text I give you in the caption box, use the hashtags I give you, keep the default cover, do not pick an extra sound, and stop in front of the publish button. Do not submit yet.

Keep “do not submit yet” for now. Publishing cannot be undone. For the first few runs, have it stop at the door and wait for you. That is steadier than letting it run all the way through. After several days of correct runs, take that limit off.

The version you worked out can be saved on the Prompts page. When the content line changes later, call it up and edit the wording.

What has to stay a parameter, and how files reach the phones

Once the flow runs steadily, save it in Workflows.

Whatever changes every time stays a parameter. Whatever never changes is written into the template.

Changes every time, so a parameter	Never changes, so written into the template
Caption	Open TikTok, tap the plus
Hashtags	Choose a video from the album, tap next
Which cover	Which step it stops on
Which sound	Whether it returns to the home feed after posting

Leave those four on the left open and one template covers every account and every piece of content. Write the caption into the template as well and you end up with one workflow per video.

When it is set, run validate first. Check that the step connections and the parameters are complete. Then test it on one phone. The test result lands in Execution History, which is more reliable than watching the screen.

For several accounts, the video has to be in the album first. A lot of people get stuck here.

I usually use the first of these.

Push from the workstation. Send the week’s files into each phone’s album. Push in batches. Do not push everything at once, or you fill the network. On iPhone, grant photo library permission first, or the file arrives and still cannot be saved into the album.

Let the flow download it. Put the video at an address the phone can reach, and add a step in the flow that starts the download. Flexible, and slow. It suits topping up a few phones at short notice.

Cloud storage sync. Three to five devices is workable. Once there are more, it gets hard to tell how far the sync has got.

When nothing moves, and how to set the schedule page

Once the time has passed, open that task in Execution History. It has the source, the status, the target device, and the error, which is enough to tell which kind of problem it is.

I look in this order.

If it mentions the device is offline, go back to the device page and look at the phone, then at the connection settings on the matching install page.

If it mentions the automation environment, go back to the install page and check the phone-side program and the related permissions.

If it mentions unauthorised or expired, open the workflow library and see whether this template can still run.

If it mentions image matching or OCR failure, the button probably has no text. Add an image template.

If there is no error and it is stuck on a step, the wait was too short. Widen it by a second or two and try again.

Going through that order locates most cases within a few minutes.

Once the pieces above are running, add the rule on the Schedule page. Posting at a set time is configured on the computer, and the entry is here.

The page has two kinds. A workflow schedule runs a named template at the set time. A conversation schedule runs from the conversation at the set time. Publishing has fixed steps, so use the first.

Offset the lines. Several accounts in different markets should not all move in the same minute. Once they are offset it looks ordinary, and you can tell which device went wrong.

The schedule saves the moment you press the button. The template still has to be changed when it needs changing.

Miss one of these and nothing moves: the workstation on the computer is open, the computer is not asleep, and the target phone is online at the set time, or can connect on its own.

The friend with the 3am alarm later split publishing into three workflows, each with its own time, all worked back from US Eastern, and offset from each other by ten minutes or so. He does not get up for it now. In the morning he gets to the office and opens Execution History. He said what he got back was not those two minutes. It was not having to get up in the middle of the night and wait to tap publish.

Waiting up for the set time is what wears people out. Hand that part over and you have the attention left for the content. Connect one phone from the install selection page first, get the simplest publish flow running, then add the time.