LinkedIn Automation for Connection Requests, Paced by the Week

How Quicklead automates LinkedIn connection requests

In Quicklead a connection request is a step inside a sequence, not a standalone blast. It sits after the warm-up actions you choose and before the branch that splits accepted from not-accepted leads. That position is what makes the automation useful: each invite is timed, counted against a budget, and followed by a plan for both outcomes.

1. 1

   Import and score

   Pull leads from Sales Navigator, LinkedIn search, post engagers or a CSV; AI ICP scoring (Scale plan and up) keeps poor fits out.

2. 2

   Visit the profile

   Your name can appear in their profile viewers a day or so before the request arrives.

3. 3

   Like a recent post

   Optional, with a delay you pick after the visit so the two actions do not look scripted.

4. 4

   Send the invite

   With or without a note, inside that day's sending window.

5. 5

   Branch on the outcome

   Accepted leads move to the message path; the rest wait for the withdraw rule or an Open Profile message.

Note or no note: the setting follows the account type

LinkedIn treats invitation notes differently by subscription. Its Help Center says free members can personalize only a small number of invitations each month, while Premium members can add a note to every one, and it gives 200 characters as the note length for free accounts (300 for Premium). Quicklead works with those rules rather than against them: the note option is for accounts with LinkedIn Premium, and the note field is held to the length that account is allowed.

On a free account, a campaign built around a note would exhaust the quota within days and then send blank invites anyway. It is cleaner to design that campaign without a note from the start and let the profile visit and post like supply the context.

Every note needs a fallback note as well, used when a field such as {CURRENT_COMPANY} is blank. You also decide whether a reply to the note itself should end the sequence. For the wording of the note, our guide to the perfect connection request goes deeper; this page sticks to the automation.

Weekly pacing for automated connection requests

LinkedIn's 'Invitation limit reached' help page confirms that limits exist but gives no number. Senders consistently observe about 100 invitations per rolling week. Quicklead turns that into a daily invite cap per LinkedIn account, and a per-day schedule decides which days the campaign sends. Twenty a day over five weekdays reaches the weekly figure; sixteen a day leaves room for invites you send by hand.

New or long-dormant accounts should not start at the ceiling. Quicklead's warm-up ramp raises activity gradually over the first weeks, and randomized timing spreads the day's invites across the window. LinkedIn's own help page on invitation restrictions names sending many invitations 'within a short amount of time' as a trigger, separate from the weekly total.

Withdraw rules for pending invitations

Pending invitations pile up quietly. LinkedIn lists having too many outstanding invitations among its invite restrictions, and that restriction can lock you out of sending new ones for as long as a month. Each invite step in Quicklead therefore has a withdraw setting: after the number of days you choose, an unaccepted invite is withdrawn automatically and the lead moves on to whatever you planned for non-accepters.

• Withdraw after 10 to 15 days, so pending invites never sit for a month.
• A withdrawn prospect cannot be re-invited straight away (LinkedIn's help page puts the wait at up to three weeks), so no instant retry.
• The prospect is not notified of the withdrawal; the request simply disappears from their list.
• Leaving the setting at zero keeps invites open indefinitely, which is rarely what you want.

Open Profile fallback for prospects who do not accept

Open Profile is a setting some Premium subscribers turn on; with it, a stranger can write to them with no connection and no InMail credit spent. Quicklead detects Open Profile status automatically when leads are imported, so the sequence knows in advance who can be reached this way. Two patterns work: run the Open Profile message as a parallel branch for those leads, or keep the invite and send the Open Profile message only when the invite goes unanswered.

One limit to plan for: LinkedIn says it limits how many Open Profile messages you can send in a given period, and senders on free or basic accounts feel that cap first. LinkedIn does not publish the number. Treat the branch as an extra route for high-fit leads, not a replacement for the invite budget.

Engagement sequences for invites that stay unaccepted

Prospects without Open Profile are not a lost cause either. Quicklead's engagement sequence for unaccepted invites keeps your name in front of them without a second request: follow their profile, like a later post, and comment when they write about a topic you know. If Email Finder returns a triple-verified work address, the sequence can carry on by email instead.

Keeping connection requests from colliding across campaigns

Teams running several campaigns, or several LinkedIn accounts, can end up inviting the same person twice. Quicklead can remove overlapping contacts across campaigns before launch, so a prospect sits in one campaign at a time. Contact tags record why someone was excluded, and each account keeps its own daily invite cap, so one busy seat never borrows budget from another.