LinkedIn Sequence

Quick path

Create a LinkedIn sequence and enroll candidates.

Select candidates
Where: Candidate profileSequence
Add to sequence
Where: Add to sequenceLinkedIn
Create a sequence
Where: Add to Sequence+ Create new LinkedIn sequence
Set the schedule
Where: Sending scheduleCreate sequence
Activate
Where: Add to SequenceSave and activate sequence
Manage sequences
Where: SidebarLinkedIn Sequences

A LinkedIn Sequence sends connection requests and LinkedIn messages to candidates according to your steps and sending schedule. When a sequence includes a connection request, the candidate’s messages wait for them to accept before the sequence can continue. Replies stop further steps for that candidate.

Before you start

LinkedIn sequences must be enabled for your organization. If LinkedIn is unavailable in the channel picker, ask your Scout admin or Scout Support about access.
Connect your LinkedIn account through Scout’s Chrome Extension. LinkedIn connection and message steps require your connected account to be available.
A candidate needs a LinkedIn profile URL. When you select multiple candidates, Scout can add candidates with a URL and skip those without one. If none have a URL, the panel shows LinkedIn profiles required.
If Scout reports Cannot add profile to flow (out of network), first connect with the candidate on LinkedIn, then retry enrollment.
The sender’s schedule controls the allowed sending days, hours and time zone. Scout may adjust delivery timing slightly.
Sequences are listed for the user who created them. A sequence you create is not a shared team sequence.

Steps

CREATE a LinkedIn sequence

Select candidates in New Search, Talent Map or a project and click Add to sequence. On a candidate profile, choose Add to Sequence from the actions menu, or open the Sequence tab and click Add to sequence.
Choose LinkedIn in the channel picker.
In Add to Sequence, click + Create new LinkedIn sequence.
Read the warning in New LinkedIn Sequence: using an automated connection tool without LinkedIn Premium may result in your LinkedIn account being locked out.
Enter a Sequence name. Scout may prefill a message step with suggested sample copy. Review and personalize it before sending.
Send connection request is on by default. When enabled, review the Connection request message. Scout’s creation panel warns that request limits may delay extra requests. The edit screen recommends keeping a connection note below 300 characters; this is guidance, not a documented sending limit. Turn this setting off if you do not want the sequence to send a connection request.
Choose whether to Send first message immediately. If it is off, the first step’s delay applies. Edit the message body, then click Add step to add follow-ups and set each delay in hours or days. A sequence can have up to 5 steps and must have at least one. Every LinkedIn step needs a message body.
Click Configure sending schedule. Choose the sending days, start and end times, and time zone. New sequences default to Monday through Friday, 8:00 AM to 6:00 PM. Scout initially selects a time zone matching your browser when available; otherwise, the default is Singapore time. There is no separate all-day option in this form.
Click Create sequence. This creates the sequence and returns you to Add to Sequence with it selected. Creation does not enroll or start candidates by itself.

ENROLL candidates in a sequence

Select candidates and choose Add to sequence, then choose LinkedIn.
In Add to Sequence, choose a sequence from the Sequence dropdown. The panel shows its steps and sending schedule so you can check the configuration before enrolling.
Choose what happens next:
- Save sequence and don’t activate enrolls eligible candidates without starting sends. You can activate the sequence later.
- Save and activate sequence enrolls and starts eligible candidates. Sending still follows the configured schedule and requires your LinkedIn account to be connected.

If some selected candidates have no LinkedIn URL, Scout adds only those with a URL. Candidates already enrolled in the selected sequence are skipped. Adding an archived candidate restores their previous enrolment without resending messages already sent. Restored enrolments may be scheduled, paused or stopped depending on their previous progress and replies; restoration does not guarantee sending resumes. A partially sent enrolment cannot be restored while the candidate is active in another sequence. New enrolments can be saved while another sequence is active, but cannot be activated until that sequence stops.

When Send connection request is enabled, a candidate’s current step can show Scheduled to send request or Pending Connection Acceptance. The message sequence does not proceed until the connection is accepted. LinkedIn request limits can delay requests; Scout’s interface does not promise an exact delivery time for delayed requests.

EDIT a sequence

Open LinkedIn Sequences from the sidebar and click Edit for a sequence.
On the Edit tab, update message bodies, delays, sequence settings, connection request note or steps. You can have 1 to 5 steps. Click Save changes to save the edits. If a save fails, your edits remain on the page so you can try again.
On the Schedule tab, edit sending days, hours or time zone and click Save schedule. The page shows Unsaved changes until saved. If saving fails, your changes remain available to retry.
The Overview tab shows sequence statistics and enrolled candidates. If you leave with unsaved changes, choose Leave to discard them or Keep editing to stay.

MANAGE LinkedIn sequences

In LinkedIn Sequences, search the currently visible page by sequence name with Search visible sequences, filter that page by Status, and use Columns to show or hide optional columns. Select rows to Archive several sequences. The list shows sequences created by your user account.

The table’s Audience counts show Pending, Messaged and Total candidates. The LinkedIn counts show Requests, Accepted and Replies. Progress shows Completed and Stopped counts. These are counts, not the sequence’s overall status. The status filter includes statuses such as Scheduled, Active, Paused, Stopped, Archived and delivery errors.

Use View to open the sequence. The Overview tab includes candidate names, roles, recent projects and current step. Search and filter this table by name, job title, location or current step. The current step can also explain why a candidate is waiting or show a delivery error. Use the row’s switch to start or stop an individual candidate, or Archive from sequence to remove them from this sequence. You can select multiple candidates and archive them from Bulk actions. Archived enrolments can be restored by adding that candidate to the same sequence again.

Use the sequence row’s switch to activate or deactivate the sequence. If the current status cannot be refreshed, use Retry status before changing sending. Delete in the row’s menu archives the sequence from the active list, although the confirmation dialog warns that the action cannot be undone. Confirm the action in the dialog.

What you should see

Successfully activated candidates appear in the overview with their current step. Requests and messages follow the configured sending schedule. Candidates who are not yet connected wait for connection acceptance before message steps proceed. A detected reply stops further steps for that candidate. Check each candidate’s current step and status rather than treating the aggregate Completed and Stopped counts as a delivery record.

Common problems

Problem	Cause	Fix
LinkedIn profiles required	None of the selected candidates has a LinkedIn profile URL available for enrollment	Select candidates with LinkedIn URLs or enrich the profile. If only some candidates are missing URLs, Scout can add the others.
LinkedIn is unavailable in the channel picker	LinkedIn engagement is not enabled for your organization	Ask your Scout admin or Scout Support about access.
Cannot add profile to flow (out of network)	Scout’s LinkedIn check reported the candidate as out of network, not simply as an unaccepted connection	Connect with the candidate on LinkedIn, then retry enrollment.
Candidate is waiting for acceptance	A connection request has been sent but not accepted	Wait for acceptance. The LinkedIn message steps do not proceed before the connection is accepted.
A request or message has not been sent	The candidate is not active, the schedule window has not opened, a LinkedIn request is delayed by sending limits, or your LinkedIn account is unavailable	Check the sequence and candidate status, the schedule, and your linked account in the Chrome Extension. See Troubleshooting.
A candidate cannot be activated in this sequence	They are active in another sequence, have completed this sequence, or activation failed	Stop the other sequence first if applicable. Review the activation error and the candidate’s current step and status in the sequence overview.

Frequently asked questions

Does creating a sequence start sending?

No. Creating the sequence returns you to Add to Sequence. Enroll candidates and choose Save and activate sequence to start sending, or save without activating and start later.

Why is a candidate’s LinkedIn sequence waiting?

If the current step is Scheduled to send request, Scout has not sent the request yet. If it is Pending Connection Acceptance, the request is waiting for the candidate to accept. The message steps proceed after acceptance, subject to the sending schedule.

What happens when a candidate replies?

Scout stops further steps for that candidate. Their reply is counted in Replies, and the candidate’s progress shows Replied. Other candidates in the sequence continue independently.

Can I add someone who is already in another active sequence?

For a new enrolment, yes: Scout can save it, but cannot activate it until the candidate’s other active sequence stops. Candidates already in this exact sequence are skipped. Adding an archived candidate restores the previous enrolment without resending already-sent messages, but a partially sent enrolment cannot be restored while another sequence is active. Completed or replied enrolments remain stopped when restored.

How many connection requests can Scout send?

Scout applies connection-request limits and can delay requests. The creation panel displays a limit of 100 new requests per week, but server-side sending also applies a separate daily cap. Because the limits differ, treat requests as delayable and check the candidate’s current step instead of relying on a fixed send date.

Pro Sourcing Tip

Personalize the connection note and each follow-up. Keep the note concise, and check the candidate’s current step if a request or message is waiting.

Request Access → Login