Two years ago a woman who makes handmade jewellery asked me whether eight Instagram accounts could hand bulk posting to a computer. The accounts were split by collection. One round a day, and the tapping alone took over two hours.
I asked where those two hours went. She said each piece of content was already prepared. The photos were a batch shot the week before, and the captions were written and kept in a notes app. The time went into posting: open the app, tap the plus, find the matching photo in the library, paste the caption in, add hashtags, choose a location, pick a cover, tap share. One round took seven or eight minutes. Eight accounts took over two hours, and they had to be done one by one.
The content was already ready. What remained was a fixed sequence of taps. This post is about handing that sequence to a computer.
Where it gets stuck
The assets and the publish step stay together. The photos are in the phone library, and the publish entry is in the phone app. The work happens on the phone. Trying to finish it while sitting at a computer does not get it done.
Every account still walks the full flow. The app can switch accounts inside one phone. After the switch you still start from the top: pick the photo, paste the caption, add hashtags, set the location. Switching accounts only saves logging in again. The number of taps on the screen does not go down.
The content differs, so it is easy to mix up. Collection A’s hashtags differ from collection B’s, and the cover position differs too. While you tap by hand, you have to hold eight accounts’ settings in your head at once. One or two mistakes in a day is normal.
What needs a person is deciding what to post. The rest is mechanical. Auto-posting can take that second part.
Ten steps for one post
I had her read the actions for one post out loud, step by step. This is what I wrote down:
- Unlock the phone and open Instagram
- Tap the plus in the middle of the bottom bar
- Find the chosen photo in the library
- Tap next into the edit screen (she usually changes nothing and skips it)
- On the caption screen, paste the text written earlier
- Add 5 to 8 hashtags after the text
- Tap add location and search for the shop’s address
- Pick a cover, if the post has several images
- Tap share
- Wait until publishing finishes, then return to the home feed
Ten steps. Steps 3, 5, 6, and 7 change every time. The other six stay fixed.
The parts that change can be prepared ahead of time. The only judgement left for a person is which post this account sends today.
Those ten steps, written as one paragraph a person would say:
Open Instagram, tap the plus in the middle of the bottom bar, choose the latest photo from the library, tap next and skip editing, type the text I give you into the caption box, then add the hashtags I give you, set the location to the shop’s street, keep the default cover, and stop in front of the share button without submitting.
Keep that last line, the one that says not to submit yet. The first time you run it, leave an action you cannot undo, such as publishing, for a person to confirm. Once the flow has run cleanly for several days in a row, take that line out.
Send the paragraph on the conversation page. The first time, switch to refinement mode. Details you cannot state clearly, it will ask about: which photo in the library, and whether the hashtags go after the caption or on a new line. After a few rounds, a vague description becomes copy whose steps are clear.
Save the finished version on the Prompts page. Next time you start a new collection, pull it up and change a few words.
Make it a template, one phone per account
A conversation is for trying it. A workflow is for running it every day.
Once it has run cleanly for several days in a row, save it as a workflow. The canvas is those ten steps. When the configuration is done, tap Validate and check that the step connections and parameters are complete, then pick one phone and test run it once.
These four stay as parameters:
| Left as a parameter | Why |
|---|---|
| Caption | Different every post |
| Hashtags | Different by collection, and they can change inside one collection too |
| Cover index | A multi-image post has to say which image is the cover |
| Location | Different accounts map to different shops or cities |
With those four left open, one template covers each account and each post. Hard-code the caption into the template and you get one flow per piece of content, which saves nothing.
Eight accounts could, in theory, be rotated across two phones by logging in and out. The steadier setup is one account fixed on one phone, with the alias set to the account name, such as “A collection” and “B collection”, so you can tell them apart at a glance.
Two reasons. Posting in the wrong place is expensive. Switch to the wrong account and the content goes out on another collection’s account. Deleting it and posting again is the small part. That account’s tags are then a mess. And one device logging in and out of accounts over a short stretch does not look like normal use. That has nothing to do with whether you use automation. Doing it by hand is the same. Aliases and groups are in the Devices documentation.
When the post does not go out on time
Problems cluster in three cases. After a run, check Execution History line by line, in this order:
- If the error says the device is offline, go back to the device page and look at the phone, then check the USB or WiFi settings on the matching install page.
- If the error is image matching or OCR, it is usually an icon-only button. Add an image template for that button.
- If there is no error and it stops on a step, the wait is usually set too short. The next tap fired before the page finished loading. Widen the wait by a second or two and try again.
Spread the publish times for the eight accounts. Do not stack all of them on the same minute. It looks more natural. If something does go wrong, you can also see whether it is one account or the flow itself.
The jewellery maker did not move all eight accounts at once. She ran one account for three days. Once that was stable, she copied the template, changed the parameters, and attached the second. She said the most annoying part of the day used to be still having to go and post. Now that item has left the to-do list. The extra time goes into shooting new pieces.
With one account and one post a day, posting by hand is faster, and this setup does not apply. With several accounts that also need to publish on time, get one account working first and add from there. Installation is on the install selection page.
Frequently asked questions
- Instagram can be posted to from a browser. Why use a phone at all?
- Because the assets and the publish action both sit on the phone side. Photos and clips you shot on the phone are already in the library, ready to be picked. Going through a browser means moving files to a computer first and back afterwards, and with several accounts you repeat that detour every time.
- How many Instagram accounts can one phone hold?
- The app itself lets you switch between accounts on one device, so there is no technical hard limit. I would still keep one account per phone and spread them across devices. Switching to the wrong account is expensive, and an account hopping between logins on the same device in a short window does not look like normal use.
- Location, hashtags and covers differ per account. Can one template cover that?
- Yes. Leave the parts that change as workflow parameters, such as caption, hashtags, cover index and location. The template only freezes the fixed actions: open the app, pick the image, tap next, fill the fields. Each account passes its own values in at run time.
- How do images reach the library on several phones?
- Use bulk file push from the workstation into each device library. On iPhone you must grant photo library permission first, or the file arrives but never saves. For large batches, push in stages rather than all at once, or you saturate the network.
- Will the same content across several accounts be flagged as duplicate?
- The risk is real. Instagram treats duplicated and reposted material firmly, and pushing one set of images across many accounts raises the odds noticeably. The steadier approach is to give each account its own direction, so assets may share a source but the finished posts differ.
- A post did not go out. Where do I start?
- Check the status and error for that task in Execution History. Three causes cover most cases: the device was offline, a cover or button could not be recognised, usually because it is a bare icon, which an image template fixes, or the wait was too short so the next step fired before the screen loaded. Working through those takes a few minutes.
- Should the accounts post at different times?
- Spread them out rather than stacking every account on the same minute. It looks more natural, and when several fail together you cannot tell whether one device is at fault or the flow itself is.
- I only run one account. Is any of this worth setting up?
- For a single account posting once a day, the app itself is faster and this is not worth the setup. The payoff starts at the second account, and grows with how many accounts you run and how strictly they need to publish on time.
Start with one account
Freeze the posting flow into a template and let each phone run its own
Software is completely free and runs on your own computer.