LinkedIn Connection Request Messages: 3 Frameworks With Examples

I checked the last 100 connection requests in my LinkedIn inbox. Only 15 included a note. A message is already a visible difference, but that advantage disappears when the note is a generic pitch that could have been sent to anyone.

A useful connection request does one simple job: it makes the reason for reaching out easy to understand before the recipient accepts. Write it around context, intention, and an easy next action. Which context and action you use depends on why this person is hearing from you now.

The three examples below cover three situations: someone has already shown interest, there is a time-bound event, or the person is part of a cold outbound audience.

#What a LinkedIn connection request message needs

A connection note is too small for a company introduction, a feature list, and a meeting request. Give the recipient enough information to answer three questions instead:

• Why this person? Name the action, event, role, or signal that made them relevant.
• Why are you connecting? Make your intention explicit, especially when the note is not a sales pitch.
• What happens if they reply? Offer the smallest useful next step: a resource, more details, or a practical exchange.

The note does not have to explain everything. On LinkedIn, your profile carries part of that context. The message still has to stand on its own, but it can leave the company history and full product explanation for the recipient who wants to inspect them.

#Inbound: Offer help based on what they did

When someone has already signed up, requested something, or used part of your product, the signal gives you a real reason to connect. The mistake is treating that signal as permission for a generic sales follow-up.

Use the person's action as context, then show what help would be useful now. In this Twain example, the user had created a campaign but had not yet used chat to iterate on the messaging:

The note works because the sender can explain why Mark received it. It does not say “I saw you signed up” and jump straight to a calendar. It identifies one unfinished part of the product experience and offers material that helps with exactly that.

To adapt it, replace the Twain action with a real point in your own customer journey:

• they created the first project but did not invite their team;
• they imported data but did not configure the result;
• they attended a webinar but did not use the checklist that followed;
• they requested a trial and have not reached the first useful output.

Do not invent the gap or imply that you monitored more than you actually did. Use an action your product or team legitimately knows about, and offer help that matches it.

#Event-based: Give people a real reason to answer now

An event invitation is different because the date creates a real decision. The recipient does not need a broad product pitch. They need to understand what the event is, why it is credible, and whether they want the details.

For one Twain event, we led with the venue because the Sequoia name was more likely to be recognized than ours. The message then moved straight to the date and invitation:

The reusable lesson is to build the invitation around the strongest honest reason to attend. In this case, the venue supplied trust and the date supplied urgency. For another event, that reason could be the speaker, a narrow peer group, the problem being worked through, or a format people cannot get from a recorded webinar.

The CTA is direct because the event is time-bound. “Would you like to join?” is enough. Adding a product demo request or several links would make the recipient decide about too many things at once.

If the event itself is not yet compelling, rewrite the event before rewriting the note. A polished connection request cannot create a reason to attend that the event does not have.

#Cold outbound: Qualify with one direct question

Cold outbound does not have an inbound action or event date to carry the message. You need a relevant question that quickly tells the recipient what the conversation is about.

In this example, the opener qualifies for a specific use case, the next line explains why this person was selected, and the close offers practical guidance instead of asking for a meeting:

The question filters out people who have no interest in the use case. That is better than maximizing acceptance from people who do not want the conversation.

The second line must contain a real selection reason. A role can be enough when responsibility is clear, but a recent move, team change, campaign, hiring pattern, or other current signal is stronger. Twain's deep research is built for finding that evidence before the sequence is written.

The last line handles the meeting objection directly. Nadja is not being asked to book a demo; if she replies, she gets the best practices to test with her team.

#Choose the framework from your reason for reaching out

Start with the situation, not the template:

• They already did something: name the action and offer help with the next useful step.
• You have a time-bound reason: lead with the strongest credible part of the event and ask directly.
• You are starting cold: use one qualifying question, one selection reason, and one low-friction offer.

If none of those reasons is available, more personalization will not repair the campaign. Define the audience, reason, angle, and offer first. Twain's Campaign Brief keeps those decisions attached to the campaign, while the research and message change for each lead.

If the request is accepted but gets no reply, use these follow-up angles. If a real conversation later goes quiet, use the re-engagement frameworks.

For automation, see the n8n LinkedIn workflow. The framework stays consistent; the evidence and final wording belong to the individual person.