Create a LinkedIn outreach sequence in ChatGPT

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own contacts and signals to see live results.

Most LinkedIn connection requests say the same thing. “I’d love to connect and learn more about what you’re working on.” The ones that get accepted reference something specific — a role change, a company milestone, a shared context that makes the request feel considered rather than automated. This prompt uses Lusha in the ChatGPT Marketplace to verify the contact, pull the strongest signal at their account, and write a complete LinkedIn outreach sequence. Connection request, InMail, and follow-up note. All grounded in verified data, not template filler.

How to start

1

Open Lusha in ChatGPT

Go to the ChatGPT Marketplace, search for Lusha, and click “Start chat.” Every conversation started this way is automatically Lusha-enabled.

2

Or invoke Lusha in any existing conversation

Type @Lusha in the prompt bar and select Lusha from the dropdown. Unlike Claude, Lusha does not activate automatically in every ChatGPT conversation. You must invoke it every time.

3

Fill in the brackets and send

Copy the prompt below, replace the bracketed placeholders with your contact and product details, and send. Lusha verifies the contact, pulls the signals, and writes the full LinkedIn sequence in one pass.

The prompt

Start from the ChatGPT Marketplace or type @Lusha before sending.

@Lusha Build a LinkedIn outreach sequence for the
following contact. Verify the contact via Lusha first,
pull the strongest signal at their account, then write
a signal-grounded connection request, InMail, and
follow-up note.

CONTACT:
Name: [full name]
Company: [company name or domain]
LinkedIn URL (if available): [URL or leave blank]

MY PRODUCT:
[One sentence describing what you sell and the
problem it solves]

MY TARGET OUTCOME:
[What you want from the sequence, e.g. a reply
that leads to a discovery call]

Using Lusha, do the following:

1. CONTACT VERIFICATION
   Verify the contact is still in seat.
   Return their current title and tenure.
   If a recent hire (under 6 months), flag it
   as the primary hook.
   If departed, stop and flag it.

2. SIGNAL PULL
   Check what buying signals are firing at
   this account right now.
   Return the top 3 signals with type,
   score, and date.
   Select the strongest signal as the hook
   for the sequence.

3. BUILD THE SEQUENCE

   CONNECTION REQUEST NOTE
   Under 300 characters (LinkedIn limit).
   References the signal or the contact's
   role change in one sentence.
   Does not pitch. Does not say "I'd love
   to connect." Ends with a specific reason
   the connection makes sense right now.

   INMAIL MESSAGE
   Subject line under 8 words.
   Body under 200 words.
   Opens with the signal.
   Connects the signal to a specific problem
   your product solves for this role.
   Ends with a single low-friction ask.
   No bullet points. Conversational tone.

   FOLLOW-UP NOTE (if no reply after 7 days)
   Under 100 words.
   Does not repeat the InMail.
   References a new signal or a different
   angle. One direct ask.

4. For each element, note in one line which
   signal or verified data point was used
   and why it makes the message more relevant
   than a generic template.
Built by: Lusha
Time to build: 5 min
Difficulty: Easy
Tools: ChatGPT, Lusha
Type: Template

What you’ll get back

A verified contact profile, the top signals at their account, and a complete LinkedIn outreach sequence ready to send. Here’s what the output looks like:

LinkedIn outreach sequence — Lusha

ElementSignal usedOutput
Contact verifiedTenure 3 weeks ⚑ recent hireR.M. · VP of Sales · [Company A] · joined 3 weeks ago
Top signalNew VP in seat · Series B closed · 11 days ago · score 84Primary hook for all three elements
Connection requestNew VP · Series B context“Congrats on the new role at [Company A]. Saw you just closed a Series B. Connecting with sales leaders building their outbound stack at this stage.” (187 characters)
InMail subjectSeries B · SDR scaling motionScaling the SDR team at [Company A]
Follow-up noteIntent signal · score 74 on prospecting data79 words · new angle · direct ask for 20-minute call

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own contacts and signals to see live results.

Why use Lusha in ChatGPT for LinkedIn outreach

LinkedIn is the most crowded outreach channel in B2B. Every VP of Sales receives connection requests and InMail messages every day. The ones that get accepted and replied to are not the best written. They are the most specific. A message that references something real about the recipient’s situation — their new role, their company’s recent funding, a hiring surge that signals they are building something — stands out because it proves the sender did more than paste a name into a template.

Lusha gives that specificity a verified foundation. The signal is not inferred from a LinkedIn post or a news mention that may or may not be accurate. It is pulled from Lusha’s verified B2B database — confirmed, dated, and scored. The contact’s tenure is verified. The company’s funding event is confirmed. The hiring surge is real. When that verified context shows up in a 280-character connection request, the contact knows immediately that the outreach is informed rather than automated.

Running this inside ChatGPT with @Lusha means the verification, signal pull, and writing happen in one conversation before the rep opens LinkedIn. The connection request is ready to paste. The InMail is written. The follow-up is drafted. Nothing is improvised at the point of send.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is GDPR compliant and covers contacts across North America, EMEA, and APAC.

FAQ

  • What is the LinkedIn connection request character limit and does this prompt respect it?

    LinkedIn connection request notes are limited to 300 characters. The prompt explicitly specifies under 300 characters for the connection request element and the example output comes in at 187 characters. When you paste the output into LinkedIn, check the character count before sending — if Lusha generates a note that runs slightly over, trim the middle sentence rather than the opening or the closing line. The opening establishes the signal. The closing gives the reason to connect. Both are more important than the middle context.

  • Should I send the connection request before or after the InMail?

    Connection request first, always. The InMail lands differently if the contact has already accepted the connection — it arrives from someone they recognised rather than a stranger. Wait 3 to 5 days after the connection request is accepted before sending the InMail. If the connection request is not accepted after 7 days, send the InMail directly without the connection. The follow-up note in this sequence is designed for that scenario — it uses a different signal angle so it does not feel like a repeat of the InMail.

  • Can I use a LinkedIn URL instead of a name and company to look up the contact?

    Yes. Add the LinkedIn URL to the contact section of the prompt and Lusha will resolve the contact from the URL directly. This is the most reliable identifier when the name is common or when you are not certain of the exact company name spelling. The LinkedIn URL resolves to a unique contact in Lusha’s database, which reduces the chance of a mismatched result. If you have the URL available, use it as the primary identifier rather than the name and company combination.

  • How is this different from using LinkedIn Sales Navigator to write outreach?

    LinkedIn Sales Navigator shows you what the contact has published and what they have engaged with inside LinkedIn. Lusha shows you what is verified and happening at their company right now — funding events, executive moves, hiring surges, intent signals — that may never appear on LinkedIn at all. A Series B that closed last week may not have a LinkedIn announcement yet. Eight SDR roles posted on a job board may not be mentioned on the contact’s profile. Lusha surfaces that context before LinkedIn does, which means the outreach arrives before competitors who are waiting for the LinkedIn signal.

Related Plays

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.

Get free access Read the Docs