Skip to main content

​
How Swan sends LinkedIn outreach

LinkedIn outreach runs through your own connected LinkedIn account — Swan doesn’t use LinkedIn’s official messaging API (there is no InMail support), it sends connection requests and direct messages as your account, the same way you’d send them by hand. Because of that, all of LinkedIn’s normal account behavior and limits apply, and Swan paces sending specifically to protect your account from being flagged. A sequence can include connection requests, direct messages to connections, or both. LinkedIn requires a connection before you can message someone who isn’t already connected to you, so if a sequence includes both, the connection request step always comes before any message step to that contact.

​
Connection requests don’t hold up the sequence

Sending a connection request is fire-and-forget: Swan sends the invite and immediately moves the contact on to whatever comes next in the sequence. If a LinkedIn message comes next and the contact isn’t connected yet, Swan holds the contact in Pending before running that message step. It doesn’t occupy a sending slot while waiting for acceptance. Earlier email and wait steps keep their existing schedule. See Replies and stop conditions for what happens if the invite is rejected or expires.

​
Sending limits and Sales Navigator

Swan applies daily and weekly per-inbox caps to connection requests and messages to keep activity within what LinkedIn considers normal for a human account. If your connected account has LinkedIn Sales Navigator, Swan detects this automatically at connection time and raises your daily and weekly sending caps accordingly, since Sales Navigator accounts get more headroom from LinkedIn itself. You don’t need to configure anything for this — it’s picked up from your account, and a “Sales Nav” badge appears next to the inbox on its LinkedIn integration card at agent.getswan.com/tools once detected. Sales Navigator also determines whether your connection requests can carry a personal note. LinkedIn heavily restricts note-bearing invites on standard accounts, so Swan only includes a note when the inbox has Sales Navigator — a sequence step can have a note written on it, but if the inbox is a standard LinkedIn account the invite goes out without it. See sending limits for the exact default numbers.

​
Tracking invitation status

Acceptances are picked up in real time. Once LinkedIn notifies Swan that the connection landed, a pending LinkedIn message becomes eligible for the next scheduler cycle (about every 15 minutes), subject to the sending window and inbox limits. A periodic background invitation check handles rejection and expiry after about 2 weeks from when the invitation was sent. Swan skips the remaining LinkedIn messages; LinkedIn-only contacts finish with a connection-expired or connection-rejected reason, while mixed sequences continue through their email steps in order. An acceptance after the contact has finished does not restart sending.

​
When a connection request can’t recover on its own

Before sending, Swan checks whether this inbox already has an outstanding invitation to the contact. If it does, Swan adopts that invitation without sending again or spending a daily slot. When it can reuse a sibling sequence’s pending invite, it keeps that original sent date for the 14-day acceptance clock. If LinkedIn still rejects a send as a recent or duplicate invite, Swan runs the same recovery: a sibling pending invite, then the inbox sent-invitations list. Only if neither works does Swan give up on LinkedIn for that contact — and even then, any email steps in the same sequence keep running. For other kinds of LinkedIn pushback (a restricted profile, an invalid URL), Swan doesn’t retry — retrying against LinkedIn’s own pushback is exactly the kind of behavior that risks your account being restricted.

​
Common questions

Can Swan send LinkedIn messages to someone I’m not connected to? Only by sending a connection request first and messaging once it’s accepted — Swan can’t message a non-connection directly. Can Swan add a personal note to connection requests? Only when the inbox has Sales Navigator. Notes can be up to 300 characters. On a standard LinkedIn account, Swan sends the invite without a note even if the sequence step has one — LinkedIn heavily restricts note-bearing invites on non-premium accounts. Does Swan post, comment, or react on LinkedIn on my behalf? No. Swan can send connection requests and direct messages, and it can monitor engagement (likes/comments on tracked posts) to trigger outreach, but it doesn’t publish or interact with posts itself. What happens if I already sent someone a connection request manually before Swan tries? Swan checks the profile first. If an invitation is already outstanding, it adopts that invite without sending or spending a slot. If LinkedIn still rejects a send as a duplicate, Swan tries to match it to an invitation it can find (from another sequence or in your sent list) and continues from there; if it can’t find a match, it stops trying LinkedIn for that contact while any email steps in the sequence keep going. Do LinkedIn limits reset if I add Sales Navigator later? Yes — Swan detects your account’s tier again when you reconnect, so upgrading to Sales Navigator and reconnecting (from the LinkedIn integration card at agent.getswan.com/tools) raises your caps. Can I connect a LinkedIn company page instead of a personal profile? No, only personal LinkedIn accounts can be used as outreach inboxes. Company pages can be monitored for engagement but not used to send messages.