Last year a friend in industrial components asked me whether LinkedIn automation was reliable.
He does B2B and finds customers on LinkedIn. The customers are small and mid-sized factories in Europe. The method was the usual one: search for a procurement contact, look at their profile, send an invitation, and attach one line of explanation. A few dozen a day. Over a quarter that builds up some leads.
The clicking can go to a computer. The hard part is choosing the person, and how that line is written.
LinkedIn works differently from a posting platform
Instagram, Pinterest, and X run on reach. One extra post, at most, is something nobody sees.
LinkedIn runs on relationships. The person who receives the invitation sees your name and your title, decides whether to accept, and can report you. After a careless send, the account stays in their list, and that impression is hard to take back.
Here the aim is a small volume, kept steady, and aimed accurately. The repeated clicks can be standardised. Choosing the person and writing the line stay with you.
He read the actions out, and I wrote them down like this:
- Open LinkedIn and go to search
- Enter keywords, such as “procurement manager” plus a city
- Scroll the results and pick the ones that fit
- Open the profile and glance at their history and recent activity
- Tap Connect
- Choose Add a note
- Write a line or two
- Send
- Return to the search results and continue with the next person
Of the nine steps, steps 3, 4, and 7 are judgement. The rest are operations. Pick the wrong person and better wording afterwards still does not help.
Which actions to hand over
| Action | Can it be handed over? | Why |
|---|---|---|
| Open search, enter keywords | Yes | The action is fixed |
| Scroll the list, open the profile | Yes | The order is fixed |
| Read the profile and decide whether this person fits | No | This is judgement |
| Tap Connect, choose add a note | Yes | Fixed |
| Write the invitation text | Partly | The text has to be prepared per person, and it can be written ahead of time. The flow only fills it in |
| Send | Yes | Leave it for a person to confirm the first time |
| Record who was contacted | Yes | Check it from Execution History |
You can hand over the stretch from tapping Connect through sending and recording. Search and filtering can also be a template when the criteria are clear, such as industry, job title, and region. Which specific people to open is still yours to decide.
Frequency matters more than volume
On X or Pinterest I would usually start the frequency low, watch the numbers, and raise it from there. On LinkedIn, stay more conservative. Hold a very small volume first, get the acceptance rate to a level you are satisfied with, then consider adding more.
The risks on the two sides differ. Extra content, at most, goes unseen. Extra invitations get the account restricted. That account may have been maintained for a long time, and the content and the connections are still on it.
When you configure the flow, do two things.
Write a daily ceiling into the flow or the schedule. Set a number, for example twenty, and stop when you reach it.
Space the actions out. Twenty invitations inside ten minutes does not look like a person. Spread them across different parts of the day, with a gap between them.
The ceiling and the gaps are there to keep the account.
Leave the wording as parameters, and fill the log every time
Prepare several versions, grouped by who you are writing to. One for factory procurement contacts, one for brand marketing contacts, one for independent store owners. The tone and the emphasis differ in each.
Inside each version, leave variables, such as the company name, something they posted recently, and a mutual contact. At run time, pass the values for that person into the flow. The flow does not assemble the sentence on its own.
Written this way, it is one fixed line:
Hello. I saw that you work in manufacturing. We have related products, and I would like to connect.
Written this way, it is aimed at a specific person:
I saw the post you made last month about supplier lead times. We make components, and our main customers are also small and mid-sized factories in Europe. I would like to connect.
In the second, “supplier lead times” and “small and mid-sized factories in Europe” are both variables. The flow’s job is to fill them in.
After two weeks he found that a few customers had received the invitation twice, and a batch of people had been contacted and then forgotten for follow-up.
Remembering who has already been sent to, in your head, falls apart after a few dozen. Looking only at the status on LinkedIn, such as Pending, is unsteady too. The status changes, and you cannot filter it by your own categories.
Keep a table, one row per person:
| Column | Contents |
|---|---|
| Name | The person’s name |
| Company | The company they belong to |
| Date sent | The day the invitation went out |
| Status | Sent / accepted / replied / no response |
| Notes | Which wording was used, and how far the conversation got |
After the flow runs, check Execution History once through, and write that day’s updates back into the table. The table can stay simple. Update it every time.
Keep posting and invitations apart, one phone per account
Keep posting and invitations as two workflows.
A post is three or four steps. The only parameters are the body text and the image index.
An invitation is longer: search, open the profile, tap Connect, add a note, fill in the text, send. The parameters include which wording set, the variables, and that day’s volume.
Once they are separate, a change to the invitation wording does not touch the posting flow.
With more than one LinkedIn account, fix one account on one phone, and set the alias to the account name or the market it covers.
One send from the wrong account can leave a record on both accounts.
The fixed clicks, the filling in, and the submit can be standardised. Whether this person is worth adding, how the line should be written, and when to follow up are still yours to decide. You set the search criteria, you pick the people, you write the wording. The rest it can run.
He later handed the repeated clicks in the invitation flow to the computer, dropped the daily volume from a few dozen to under twenty, and the acceptance rate went up. In his own words, it used to be “I have to send fifty today”. Later it became “there are twenty today that are worth sending”.
If you are also finding customers on LinkedIn, connect one phone from the install selection page first, try a very small volume for a week, and look at the acceptance rate before you decide anything further.
Frequently asked questions
- What makes LinkedIn different from the posting platforms?
- It runs on relationships rather than reach. An extra Instagram post that nobody sees costs you nothing. A careless invitation on LinkedIn is seen by a named person who can accept, ignore, or report it, and that impression is hard to undo. The goal here is stable and precise, not more.
- How many invitations a day is safe?
- No universal number. It depends on the age of the account, how active the content is, and what share of invitations get accepted. Start low, say ten to twenty a day, watch acceptance and account standing for a week, and decide from there. A large batch from a standing start carries noticeably more risk.
- How do I stop the invitation reading as mass mail?
- Two things. Do not use one identical line everywhere; prepare several versions by segment, and inside each one leave variables such as the company name or something they posted recently. Then leave the wording as a parameter passed in per person, rather than baked into the flow.
- How do I track who has already been contacted?
- This is the part that breaks first. Keep a table with one row per person: name, company, date sent, current status. After a run, check Execution History and write the day updates back into the table. Do not rely on memory, and do not rely only on the platform status.
- Should posting and inviting be separate flows?
- Yes. They share almost nothing. A post is write, attach, publish, two or three fixed actions. An invitation is search, open profile, tap connect, add a note, send, five or six steps with a decision in the middle. Combined, changing one disturbs the other.
- What about buttons that are only icons?
- Part of the LinkedIn interface uses bare icons with no text. Add an image template for those: crop the button from a screenshot, describe when to use it, and the flow will look for that picture.
- How should several accounts be spread across devices?
- One phone per account, aliased with the account name or the market it covers. Choosing a device then means choosing an account, so nothing has to be held in memory and there is one less chance of a mistake.
- What if the account gets restricted?
- Reduce the volume first and pause for a few days rather than pushing more through. Then check two things: whether the wording reads as mass mail, and whether a lot of actions happened within a very short window. Those two are the usual causes.
Move the repetitive part out
Hand over the searching, opening and inviting
Software is completely free and runs on your own computer.