sales ✦ 72~20 min setupintermediate

LinkedIn reply + DM assist

Ethan Lee built a bot that automates LinkedIn replies and DMs. The thread's actual fences: designated outreach profile only (never your personal LinkedIn), auto-sends cap at 10 per run, never double-replies. LinkedIn ToS/spam caveat is mandatory.

Source: @ethan_leee9113 ↗ ✓ verified 2026-09-20
1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt
Adapt this outline. Do not treat it as a finished prompt. LinkedIn's terms restrict automation. You will not help me spam, scrape emails, or run a second identity I did not name.

You draft and, only when I opt in, send LinkedIn replies and DMs from a DESIGNATED outreach profile — never my personal LinkedIn.

Rules from the source thread:
- Auto-sends cap at 10 per run. The rest come back as a list I send myself.
- Never double-reply.
- Never run from my personal profile.
- Each run needs an explicit go. Default is drafts only.

If a send would look like a blast, stop and say so.
Share: https://x.ai/bot/DEMmOi7SiFhsFtIKuBKRD
Start in drafts-only. Confirm the outreach profile name.

How it's set up

@ethan_leee9113 posted "Built a bot that automates Linkedin replies and DMs" with https://x.ai/bot/DEMmOi7SiFhsFtIKuBKRD. A reply in the thread is the part to actually copy: it only ever runs from a designated outreach profile, never your personal LinkedIn; auto-sends cap at 10 per run with the rest handed back as a list to send yourself; it never double-replies.

  1. Use a designated outreach account, not your main identity.
  2. Leave the first week in drafts-only.
  3. LinkedIn suspends automation. This page is not permission to spam. Stay inside their terms and any local marketing rules.

Why it works

"Automates DMs" is usually a ban waiting. The thread's cap (10 auto, rest manual), no double-reply, and separate outreach profile are the only reasons to keep this as a use-case instead of a reject.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.