LinkedIn invites and Instagram DMs to people who commented

LinkedIn invites and Instagram DMs to people who commented

An n8n workflow for the people who comment on your posts. You paste a post's address into a form. Through Unipile, the
workflow reads the post's comments and looks up each commenter. On LinkedIn, anyone who is not yet a connection gets a
connection request with a short note. On Instagram, a commenter who passes two checks gets a direct message. It waits a minute
after each send.

Read Good to know before the first run. LinkedIn and Instagram both forbid this kind of automation in their terms.

What is inside

• workflow.json: the workflow as n8n exports it, 29 working nodes and three sticky notes. It holds no credential and no
  key. Several nodes carry their author's notes, which n8n shows in each node's settings.
• README.md: these notes.

What we changed from the original copy

• Get Post ID reads the post's number with activity-(\d+)- again. The export had dropped the backslash, so the pattern
  looked for the letter d and every LinkedIn run stopped there.
• Get Post ID1 lost two backslashes the same way, and its pattern would not even parse. It reads the code from a /p/,
  /reel/ or /reels/ address again.
• The sample note in the node notes of both message nodes was signed with a person's first name. It now says Your name.
• The form and the two waits lost their webhook ids, and the workflow carries this listing's name.
• API Setup already held the placeholders YOUR_UNIPILE_DNS and YOUR_UNIPILE_API, so they stay as they came.

Before you start

• An n8n instance, on n8n Cloud or your own server.
• A Unipile account, its API key and its DSN.
• Your LinkedIn account, your Instagram account or both, connected in Unipile.

Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick workflow.json.
2. In Unipile, connect the accounts that should send. The workflow uses the first LinkedIn account and the first Instagram
   account that Unipile lists.
3. Open API Setup. Replace YOUR_UNIPILE_DNS with your DSN: the host and port your Unipile dashboard shows, without
   https://.
4. In the same node, replace YOUR_UNIPILE_API with your Unipile API key.
5. Read the template in ✍️ Generate Personalized Message and ✍️ Generate Personalized Message1, and change it to
   sound like you.
6. Save, open the test address of 📋 Form: Enter Post URL and paste a post with two or three comments.
7. Check each send in the run. Press Publish only if you want the form's live address.

How a run goes

1. The form takes one address. API Setup holds your Unipile values, and 🔍 Get Accounts lists your connected accounts.
2. If sends an address that contains linkedin.com to the LinkedIn row. Anything else goes to the Instagram row.
3. The LinkedIn row:
   - Get Post ID takes the number after activity- and the id of your first LinkedIn account.
   - 🔍 Fetch LinkedIn Post and 🔍 Fetch All Comments read the post and its comments. 📤 Split Comments Array makes
   one item for each comment.
   - 🔄 Loop Over Items hands over one commenter at a time, and 🔗 Check Connection Status reads their profile.
   - ❓ Should Send Request? passes only a profile whose is_relationship is false.
   - ✍️ Generate Personalized Message writes the note, and 📨 Send Connection Request sends the request with it.
   - ⏱️ Wait (Rate Limiting) waits one minute before the loop takes the next commenter. A skipped person or a failed send
   goes straight to the next one.
4. The Instagram row:
   - Get Post ID1 takes the post's code from the address and the id of your first Instagram account.
   - 🔍 Fetch Instagram Post and 🔍 Fetch All Comments1 read the post and its comments.
   - For each commenter, 🔗 Get Profile Info asks for your own profile and 🔗 Check Followers Status for theirs.
   - If1 lets them through when both relationship_status.followed_by and relationship_status.has_received_invitation
   are false.
   - ✍️ Generate Personalized Message1 writes the text, and 📨 Send Connection Message starts a chat with it.
   - ⏱️ Wait (Rate Limiting)1 waits one minute before the next commenter.

The form answers as soon as you send it, and the run goes on behind it. Thirty commenters who all get a send take at least
half an hour.

The note

Both message nodes share one template. Words in braces, split by |, are picked at random, so two commenters rarely get the
same note. {{fullname}} becomes the commenter's name. {{signatureName}} becomes your account's name in Unipile, or
My Brand when it has none. A LinkedIn note uses the first and last name, an Instagram one the profile's full name.

Hi Sam Lee,

I appreciate you engaging with my post.

Happy to connect and exchange ideas.

Cheers,
Jane Doe

Unipile's documentation allows 300 characters in an invitation note. The template stays well under that unless you add a lot.

Change the look

• The note: template in both message nodes. Keep {{fullname}} and {{signatureName}}.
• The pause: ⏱️ Wait (Rate Limiting) and ⏱️ Wait (Rate Limiting)1, one minute each. A longer wait is kinder to your
  account.
• Who gets a LinkedIn request: the condition in ❓ Should Send Request?.
• Who gets an Instagram message: the two conditions in If1.
• The form's words: 📋 Form: Enter Post URL.

Good to know

• LinkedIn's User Agreement, section 8.2, forbids bots and other unauthorized automated methods to add contacts or send
  messages. Instagram's Terms forbid accessing it or collecting information by automated means without its express
  permission. An account that sends too many requests or messages can be restricted.
• Unipile's Terms of Use, section 6, forbid using its service in a way that breaks a connected platform's terms.
• LinkedIn limits how many invitations an account can send each week. Unipile's provider limits page, read on 3 November
  2026, gives a paid account about 200 a week. A free account gets about 5 invitations with a note a month, and this
  workflow always adds a note.
• The same page suggests at most 10 Instagram actions an hour and 100 a day. Sending once a minute goes past that on any busy
  post. Keep runs to a handful of commenters, or set both waits far longer.
• The author's node notes on both waits describe a random wait of one to two hours. The nodes themselves wait one minute.
• The LinkedIn row checks only is_relationship, so someone you already invited is asked again. Unipile's documentation
  lists a recent invitation to the same person among the reasons for a 422 error. A refused send moves on without waiting.
• Only the first page of comments is read. Unipile returns a cursor for the rest, which the file does not follow.
• A LinkedIn address needs activity- and a number in it, as a post's share link has. Other LinkedIn addresses stop the run
  at Get Post ID. Any address without linkedin.com goes down the Instagram row.
• 🔗 Get Profile Info fetches your own profile for every Instagram commenter, and nothing reads the answer.
• Some spun combinations read badly, such as "you taking time to liking". Trim the choices before a real run.
• No AI model runs here. The cost is your Unipile plan.
• Each commenter's name and profile pass through Unipile and your n8n, and every note goes out from your own account.
• The Unipile key sits in API Setup in plain text, so take it out before you share the workflow.