Where the repetition goes
Posting one Xiaohongshu note by hand is a long chain of actions: open the app, enter the publish page, pick images from the gallery (count, order, and the first image all need a check), write the title and body, add topics, choose a cover, set visibility, submit, then wait for the upload to finish. The part that needs thinking is the topic and the copy. The taps after that are the same every time.
A few notes a day can still be tapped by hand. Once the material and the accounts pile up, every note starts from the first tap again. Gallery position and material order are easy to get wrong, and a topic or a cover gets skipped. The same chain has to be repeated many times, and none of those times can be wrong.
iEasyRun has three entries: conversation, workflow, and local MCP. Bulk posting has fixed steps and has to run repeatedly, so a workflow is the right place for it.
For a one-off post, use conversation: pick an online phone, say what to do in plain language, and the AI runs it on the real phone. If the steps are still unclear, switch to refine mode, talk through what to tap first and what to tap next, then dispatch.
A flow you will use again is saved as a workflow. At run time you only pick the phone and the parameters. The workflow library can search, categorize, create, and import. On the canvas you can arrange steps, validate, and auto-layout. When there are many steps, “AI workflow collaboration” can generate or edit them. See the workflow overview.
Local MCP exposes the workstation as an MCP server for external assistants such as Cursor and WorkBuddy. The tools exposed for querying are only list_devices, list_device_groups, list_devices_by_groups, and list_workflows, used to list devices and list workflows. Taps, swipes, and running a workflow cannot go through MCP. They have to run in a conversation or a workflow. Bulk posting still lands on the workflow. The boundary is in the MCP documentation.
| Stage | One note at a time by hand | After it is a workflow |
|---|---|---|
| Enter the publish page and pick material | Every note starts from the first tap | Steps are fixed and run on their own |
| Title / body / topics | Repeated copy and paste | Filled in as parameters, configured once and reused |
| Cover and visibility | Easy to skip a setting | Fixed steps, so the item is included |
| Running on several phones | Operated one phone at a time | Pick a device or a group and dispatch together |
The copy stays with you. The workflow runs the taps that are the same every time.
What to prepare before publishing
- On the Devices page, scan the phone, register it, and give it a recognizable alias. An offline device can be viewed. It cannot run. Confirm the target phone is online before you publish.
- iOS has a USB edition and a wireless edition. Android and HarmonyOS install guides are still being prepared. Choose from the install selection page.
- Put the images in the gallery first. Write the title, body, and topic list as text, so they can go into parameters or prompts.
- Confirm which account this note is for. Avatar and display name affect how the AI reads the interface.
When the request is still vague, go to the Prompts page and talk it through with the AI for several turns. Move it onto a workflow after the steps are clear.
How to configure a publish workflow, then test it on one phone
The steps have to match the real interface on your phone.
- Go to the workflow library and create one. Use a name you can read at a glance, such as “Xiaohongshu image-and-text publish”.
- Build this order on the canvas: start the automation environment, open the app, wait for the interface, enter the publish page, choose the material, fill the title and body, add topics, set the cover, submit, wait for the upload to finish. Other common step types are “start automation environment”, “wait”, “open app”, and “gesture-swipe”.
- When there are many steps, use “AI workflow collaboration” to generate a draft, then check each step.
- Save, then validate, and see whether any step link or parameter is missing.
- If OCR cannot recognize an icon or button, go to Image Templates, crop a small image, write what it is and when to use it, then attach it in the conversation or the workflow.
- You can also run one publish through in Conversation first, then move the steps you have already talked through into a workflow.
Get it through on one phone before spreading it to other devices.
- Tap test run in the workflow library or on the canvas, and pick one online target phone.
- In Execution History, check the source of this run, whether it succeeded or failed, which device it ran on, and the error message if it failed.
- If it reports the device offline, look at the Devices page and the install page. If it reports the workflow unauthorized or expired, check the status in the workflow library. If it reports an image-match or recognition failure, add an image template.
- After one phone runs cleanly, hand it to more phones. Once there are many devices, grouping is clearer than remembering each name.
Use a schedule to set the posting cadence
Posting too densely throws the account’s rhythm off. iEasyRun’s Schedule page has two kinds of tasks.
A conversation schedule is bound to a conversation session or a task description. You set the run time and the repeat rule, and when the time arrives it runs the session content on the target phone. A workflow schedule selects a workflow template and a target phone, and fires on a time rule.
Bulk posting uses a workflow schedule. The steps are fixed, and the result is easier to check. Three things matter when you set it: the iEasyRun workstation on the computer has to be open, because scheduling is local and there is no cloud; the target phone has to be online, or able to connect on its own when the time arrives; if it is on USB, that cable still has to be connected at that moment. Details are in Schedule.
Results from both kinds of schedule go into Execution History. Whether today’s post went out is in the record.
Start with one workflow, one phone, and one fixed time. Run it for a few days, see whether execution history stays steady, then add devices or change the frequency. A similar case is short-video auto publish. The software is free and runs on your own computer. Try it on one phone you already have.
Frequently asked questions
- What does bulk Xiaohongshu posting mean in practice?
- It means publishing several Xiaohongshu notes in one session without repeating the same taps by hand. The posting steps stay identical, so only the images, caption, and topics change from note to note.
- Do I need to write code to automate Xiaohongshu posting?
- No. You describe the posting flow in plain English in the Conversation page, and the AI operates a real phone. When you want to repeat it, save that flow as a Workflow template. Nothing is scripted by hand.
- How many phones can one computer manage for posting?
- There is no fixed limit in the software; it depends on your USB ports, network, and phone performance. If you run several phones, group them in the Devices page so you can pick a group instead of single devices.
- Can a Xiaohongshu posting task run while the phone is offline?
- No. An offline device can be viewed but not run. Conversations, workflows, and scheduled tasks will not execute on an offline phone, so confirm the target phone shows as online before you dispatch.
- What is the best way to handle captions that change every time?
- Leave the changing parts as workflow parameters. Fix the actions in the template, such as where to tap and which field to fill, then pass the caption, topics, and image index at run time. One template then covers every note.
- Can I schedule Xiaohongshu posting at a fixed time?
- Yes. In the Schedule page you can create a workflow schedule or a conversation schedule that fires at a set time. The workstation must stay running on your computer, and the target phone must be online or able to connect at that moment.
- How do I find out why a posting run stopped?
- Open Execution History. Each record shows where the task came from, its status, the target device, and the error message. Common causes are an offline device, an unauthorized workflow, or a failed image match or OCR step.
Get Started
Turn Your Xiaohongshu Posting Loop Into a Reusable Template
Software is completely free and runs on your own computer.