Posting Across Several X Accounts Without Living in the App

Last year a friend who runs cross-border commerce news asked me whether automatic posting on Twitter could actually work. He posts close to 20 times a day.

I asked how he does it. He said when he sees news worth passing on, he posts it, and it takes under a minute. It does not sound like much.

That minute arrives about 20 times a day, and the time is set by the news, not by him. He is in a meeting with a supplier, the phone buzzes, and he has to stop and post. At 11 at night he is about to sleep, another item comes out, and he gets up to post again. By the end of the day the real work is unfinished, and he is exhausted. What he wanted was for the post to go out without him standing there.

X runs on how often you show up

X is different from Instagram and Pinterest. Those two can accumulate slowly and live on the long tail. A Pinterest Pin can still bring traffic six months later. X depends more on how often you appear, and that is especially true with several Twitter accounts. Leave an account quiet for three days and readers forget you. The timeline keeps filling with new posts.

On this kind of account, a well-written single post does not replace showing up steadily.

Showing up steadily means breaking off from the work in front of you, again and again. Protect the unbroken blocks of time and the account goes quiet. Being more disciplined does not fill that gap. The method has to change.

One post is four steps, and the content comes first

The publish actions split into four steps:

1. Open X
2. Tap the compose entry
3. Type the content
4. Tap send

Automatic posting on X is those four steps. They are short enough that a lot of people think this is not worth automating.

Four steps is about 40 to 50 seconds. Twenty posts a day is about 15 minutes of actual operation. Those 15 minutes are cut into 20 pieces, spread across a dozen hours from morning to night.

The operation itself is a few dozen seconds. What takes time is pulling yourself out of the work in front of you, posting, going back, and spending a few minutes getting into it again. Twenty times is dozens of times getting back into the work.

The operating time is only about 15 minutes. What automatic posting on X removes is the need to be there.

A lot of people get stuck on the automation when the step before it is still unfinished: the content is not ready.

Spend ten minutes or so in the morning lining up what goes out today. Through the day, only let it go out at the set times.

You do not have to think about format while you line it up. A list is enough:

• First: a retelling of one news item, plus two lines of my own comment
• Second: a set of figures compared
• Third: a look back at yesterday’s post
• And so on

Deciding which item is worth posting is still your work. The computer cannot do it. It can be done in one sitting, instead of being scattered through the day.

The lined-up content can be saved on the Prompts page. If the posts follow a fixed shape, for example conclusion first and the basis after it, keep that there. When you set up a flow later, call it up.

On the conversation page, select the phone and put the whole action into ordinary words:

Open X, tap the compose entry at the bottom, type the text I give you, attach the image I name, and stop in front of the send button. Do not send yet.

Do not send automatically the first time. When it runs on a schedule you are not there. For the first few runs, have it stop in front of the send button, and come back to confirm the actions are right. That is less work than tracing a problem afterwards.

Save that version on the Prompts page. Next time you switch accounts, call it up.

Save it as a template, and leave only the text and the image

Once the flow has posted correctly for several days in a row, save it as a workflow.

In one post, the only things that change are the text and which image. Write the rest in.

The more parameters you leave open, the more you have to prepare before each run, and in the end it can be more trouble than posting yourself.

Scheduling goes wrong most often on the type of content.

Suits a schedule: news retellings, opinions, figures, product updates, looks back at earlier posts, and regular columns. These do not depend on reacting in the moment. Posting two hours earlier or two hours later makes little difference.

Does not suit a schedule: joining a live conversation about something happening now, replying to someone, and an event that is still building. The value there is the moment. A schedule gets in the way.

The part that can be scheduled is the larger share, and it goes out at the set times. Leave the rest in your hands, and post it when you see it. The timely posts stay. Most of the interruptions go.

X has a lot of bare icon buttons. Compose, repost, and attachments are graphics, with no text to read.

When you hit a button like that, add an image template. Take a screenshot, crop the small patch that is the button, give it a name, and write down when to use it. After it is saved, the flow looks for that picture on the screen when it reaches the step. It does not take long, and whether the flow holds depends on it.

Offset the accounts, and check after it runs

Several Twitter accounts means two things.

Offset the accounts from each other. Do not let three or four accounts move in the same minute. Clumped together, it does not look like ordinary use. If something actually breaks, you also cannot tell whether it is one account or the template itself.

Spread a single account too. Ten posts in a day should not all sit at 9 in the morning. Scatter them across several parts of the day, with a gap in between. It looks ordinary, and the reach is more even.

If the time passes and nothing moves, check two things first: whether the workstation on the computer is open, and whether the computer went to sleep. Scheduling happens on your own machine. Those two explain most cases where nothing happens.

At the start, open every item in Execution History. It has the task source, the status, the target device, and the error.

In the first week or two you will meet a wait that is too short, an image that cannot be found, and an account that went offline. All of those show up in Execution History. Once the problems thin out, switch to spot checks.

The news friend now spends half an hour in the morning lining up the day’s 20 posts, and leaves the rest to the template to send at the set times. He said he used to be pulled along by the news. Now he decides when to look at it.

If you only post now and then, and you are not chasing a rhythm, doing it by hand is enough. If you want frequency to hold an account steady, try this on one account for a week. The install steps are in the install guide.