LinkedIn steps that a person sends, on purpose
A LinkedIn step is a real part of a SAGARIS sequence, and a person sends it. The step puts the contact on a daily shortlist with the context already assembled, and the sequence holds there until a rep has sent the message and it is logged. SAGARIS makes no LinkedIn API calls, holds no LinkedIn credential of yours, and automates no account.
Performed by a person. A LinkedIn step in a sequence is real and it is performed by your rep. SAGARIS makes no LinkedIn API calls and holds no LinkedIn credential of yours.
Last verified October 5, 2026. All integrations
What moves, and which way
None, deliberately. No LinkedIn credential is held and no LinkedIn API call is made.
- Into SAGARIS
- Nothing automatic. SAGARIS does not read your LinkedIn inbox, your connections or your feed, so nothing from LinkedIn enters the record unless a person puts it there. What the sequence tracks is the step: that it is due, that it was sent, and when, which is what lets the cadence resume correctly.
- Back into LinkedIn
- Nothing is sent by us. When a LinkedIn step comes due, the contact lands on a daily shortlist with the reason and the context attached, and the enrollment parks. A rep opens LinkedIn, writes and sends the message themselves, and marks it done. That completion is what advances the sequence.
- The boundary
- This is a floor rather than a gap waiting to close: automating a LinkedIn account means holding a credential, driving a session, and exposing your team's accounts to enforcement action under LinkedIn's own terms, and we are not doing that on your behalf. The cost is honest too. A LinkedIn step needs a person, so it does not scale the way an email step does, and a sequence full of them will move at the speed of your reps. Publishing to social networks is a separate module, and it is not something you can turn on in the live product today.
Running a LinkedIn step
- 01
Put a LinkedIn step in the sequence
It is one of the step channels available when you build the cadence, alongside email, SMS, calls and tasks. Use it where a touch genuinely belongs on LinkedIn rather than everywhere, because each one costs a rep a minute.
- 02
The contact arrives on the daily shortlist
When the step comes due the contact appears on the rep's LinkedIn shortlist for the day, with the context needed to write something specific, and the enrollment parks rather than advancing past it.
- 03
The rep sends it themselves
From their own LinkedIn account, in their own words. Nothing is pre-sent, queued or drafted into LinkedIn on their behalf, and no session of theirs is driven by us.
- 04
Logging it resumes the cadence
The sequence advances on the logged completion. A step nobody does holds the enrollment rather than silently skipping ahead, which is the behaviour you want: a cadence that pretends a touch happened is worse than one that waits.
What SAGARIS automates instead
Email, SMS and calls dispatch automatically, on one sequence model, with send windows in the contact's local time and a cap of one sequence email per account per day enforced at dispatch so a cadence cannot swarm an account. Those are the channels where automation is both permitted and safe, and they carry the volume.
A LinkedIn profile is also still useful to the system even though no message is sent through it: research and enrichment run on a contact whether or not LinkedIn is one of their steps, so a rep opening the shortlist already knows why this person is worth a message today.
If what you want is a tool that sends LinkedIn messages from your reps' accounts on a schedule, SAGARIS is not that and is not going to become it quietly. That position is worth knowing before an evaluation rather than after.
How we checked
Read from the sequence engine rather than from a probe. planSequenceStepAction in src/lib/sequence-step-dispatch.ts maps the linkedin channel to advance: "manual", and linkedin is in the set of channels that park an enrollment until a rep-completion hook fires. The shortlist send route makes no outbound LinkedIn HTTP calls. Separately, the sequence engine carries no dispatch arm for the social channel, so a social step is skipped rather than performed, and the published /social page states the module is not available yet, both re-checked on October 5, 2026.
Verified October 5, 2026. If this is out of date or wrong, email founders@sagaris.ai and we will correct it and move the date.
LinkedIn and SAGARIS, the questions people actually ask
- MOST ASKED
No. A LinkedIn step parks the sequence and puts the contact on a rep's daily shortlist. The rep sends the message from their own account. SAGARIS makes no LinkedIn API calls and holds no LinkedIn credential of yours.
Because automating a LinkedIn account means holding a credential and driving a session, which exposes your reps' accounts to enforcement under LinkedIn's own terms. We are not taking that risk on your behalf and would rather say so than bury it in a settings toggle.
No. The enrollment parks and waits. A cadence that advances past a touch nobody performed is reporting work that did not happen, which is worse than a cadence that stalls visibly.
Not today. Publishing to social networks is a separate module from the sequence step described here, and it is not something you can turn on in the live product. In the sequence engine there is no dispatch arm for a social step, so one is skipped rather than performed. We are not putting a date on it here.
No. There is no read access to LinkedIn of any kind: not your inbox, not your connections, not your feed.