Sequences

The plan of touches each lead gets, why nothing is sent before an approval, and how the runner paces itself.

A sequence is a short plan for reaching one lead: react to their post, ask to connect, wait for an answer, then message or email. A lead has at most one open plan, and the Sequences page lists plans by where they stand.

Where a plan comes from

The outreach agent on the Agents page writes a draft when a new lead arrives and one of its rules matches. Texts are drafted once, from the lead's activity and your writing instructions. What you approve is exactly what goes out later.

Approving

Open a lead from the Awaiting approval group, read each step and press Approve and start. Problems such as an email with no subject or a missing sending account are listed above the button; fix them first.

Approval sends as the plan's chosen accounts, so they must be yours. A plan using a teammate's account needs that teammate, an owner or an admin.

Each change to a step makes a new version, and every version needs its own approval.

In Auto mode the outreach agent approves its own untouched drafts that have nothing blocking them. A plan a teammate made or edited always waits for a person. Owners and admins pick the mode; Review is default.

Steps and branches

Steps can react, comment, open a profile, ask to connect (note up to 300 characters), send a LinkedIn message, look up an email, email from Gmail or hand the lead to Lemlist. A check step branches on a profile, a first-degree connection, an accepted invitation, an opened message or a reply, and waits up to the days you set (14 by default) before taking the "if not" path.

Insert fields such as {{firstName}} with Insert a field. If one has no value when its step comes due, the step stops for your review instead of sending a gap.

Pacing

The runner paces itself:

• at most one step per lead per day, counted in the sender's time zone;
• two to eight minutes between actions from one account;
• daily limits per account, set under Connected accounts.

A step LinkedIn refuses is not retried in a loop. The plan moves to Stuck with the reason, as does any plan using an account that dropped off.

Sometimes the connection drops after a step was handed over but before LinkedIn or Gmail confirmed it, so it may already have gone out. Harken never sends such a step again on its own, not even after an edit, a new approval or Resume. Check the conversation in LinkedIn or Gmail: if it went out, choose I did it myself; if it did not, choose Send again.

Pausing and finishing

Pause stops new steps at once. Resume continues from the step it stopped at, provided the current version has an approval. When the last step is done the plan moves to Finished. I did it myself marks a step you handled by hand, and the plan moves on.