Skip to main content
A sequence can act on LinkedIn as well as email. Those steps run in your own browser through the Oneprofile extension, using the LinkedIn account you are already signed in to.
The sequence builder's step picker open on the LinkedIn tab, listing View profile, Send connection request, Send message, Send InMail, Withdraw connection request, Follow contact and Like latest post, each with a one-line description and a credit price.

The step picker, on its LinkedIn tab.

These steps need a LinkedIn account connected first. See Connect LinkedIn.

​
Add a LinkedIn step

On the Builder tab, open the step picker on any connector. Under LinkedIn the actions are View profile, Send connection request, Send message, Send InMail, Withdraw connection request, Follow contact and Like latest post. Each one spends credits, and the editor header estimates the whole sequence. The three that carry words are the connection note, the message and the InMail. Switch one to Written by the agent and give it a prompt, and the sequence’s agent writes it per contact. It keeps the voice of the emails, and anything it is unsure about waits in Tasks. To watch one run before you build a sequence, queue a single step from the sender’s LinkedIn tab. See Connect LinkedIn.

​
Branch on the answer to a connection request

A Send connection request step waits for the person’s answer, then sends them down a branch. Connected takes everyone who accepts, and anyone already connected. Not accepted takes everyone else, including people the request can’t reach.
1

Add the request

Point at the gap between two steps, click Add a step here, and choose Send connection request. The steps that followed carry on from Connected, and Not accepted gets a Withdraw connection request.
2

Set how long it waits

The Not accepted branch reads “Not accepted in 14 days”. Click the number and type how many days to wait, from 1 to 90.
3

Add steps to each branch

Point at either branch, under its name, and click the plus button to add what happens next, such as a message on Connected.
To give already-connected contacts a branch of their own, open the request and unfold More options. Switch on Give already-connected contacts their own branch, and Connected becomes Accepted beside a new Already connected branch.

​
Good to know

The mode decides whether queued steps go out on their own. On Manual run, every step waits in Tasks for Approve, and none joins the sender’s queue until you approve it. Checks of your own inbox, sent requests and new connections run on their own in either mode.Each sender’s mode is set in the dropdown beside Limits on their own LinkedIn tab. A sequence can ask for approval on top, under LinkedIn approval on its Settings tab.
On Automatic run, connection requests, messages and InMails send from your own LinkedIn account without you watching. Start on Manual run until you trust the sequence.
From the sender’s own LinkedIn, in their browser. While answers are due, it checks the sender’s newest connections regularly. If it still can’t tell when the wait runs out, it looks at the person’s profile once.Both need a browser with the extension, so keep one open for the sender and keep the extension up to date. The look costs and counts like a View profile step, and waits for Approve in Tasks whenever the sequence’s LinkedIn steps do.If even the look can’t tell, the contact reads Interrupted on the Audience tab, and Retry looks again.
They didn’t accept before the wait ran out, they declined, or the request never reached them. LinkedIn may not offer Connect, may ask for their email address, or may not show their profile. A contact with no LinkedIn URL gets no request, and neither does one whose request waited too long for a browser to come online.Their history on the sequence’s Audience tab names the reason, such as “LinkedIn didn’t offer Connect on their profile”. Skipping the request in the extension’s side panel sends them down Not accepted too, while rejecting it in Tasks stops them instead.
They run once the answer is in. A contact stays at the request until they accept, or until the wait runs out, and the next step’s wait counts from then. So one day after Connected means a day after they accepted.When no branch has a step after the request, the contact finishes once it is sent. Whether they accept is still recorded in their history. Add a step to a branch later, and contacts whose answer takes that branch go on to it.Deleting the request asks first, and keeps the branch with steps on it. When more than one branch has steps, it asks which carries on. A branch holding only a withdraw counts as empty.
While it is still pending. A new Send connection request comes with Withdraw connection request on its Not accepted branch, so a request nobody answered is taken back. The step opens the profile in the sender’s browser and presses LinkedIn’s own Pending control, the same way a person would.A request that expired or was withdrawn somewhere else is skipped, and the contact moves on. Its row on the sender’s Activity tab reads Skipped, and opening it says nothing was pending.When the person is already connected, nothing is withdrawn. The contact stops at that step and reads Already connected, with no Retry, since there was nothing to withdraw.So a withdraw can’t go on Connected or Already connected. One left there from before is flagged when you launch, and Move to Not accepted in its panel moves it.
It was added before a connection request could branch on its own answer, and it keeps working as before. A check placed right after its request is now part of that request. One placed further along stays where it is.To use the branches instead, drag its steps onto the request’s Connected and Not accepted branches, then delete the check. See Branch on a condition.
The contact stops at that step and reads Interrupted on the sequence’s Audience tab. Hover it to read the reason in the browser’s own words, such as a Connect button Oneprofile could not find. A failure never moves the contact on or marks them Finished.The step also shows under Failed in Tasks, and as Failed on the sender’s Activity tab. A failed step never runs again on its own.A connection request, profile view, follow, like or withdrawal cut off because the sender’s browser went offline, such as a laptop closed mid-step, does not fail. The contact waits under Browser offline, and the step finishes once the browser is back. It checks LinkedIn first, so nothing is sent twice.If the browser stays away for days, the step fails instead. Its reason says Oneprofile cannot tell whether it happened, so check LinkedIn before you retry.Open the row in Tasks and click Retry. On the Audience tab, choose Retry in the contact’s row menu or on a selection, or Retry all on the banner above the list. Retry runs the same step again with the same note or message and the approval it already had, and never restarts the sequence.Retry checks LinkedIn first. A step it finds already done is marked done and charged once, so nothing is sent twice.A message or InMail that may already have gone out is never sent again on its own. Its reason says so, and Retry in Tasks asks “Send it again?” first, so check LinkedIn before you retry.Each failure is recorded for the Oneprofile team, so the cause gets fixed.
The step carries on. The extension reopens its LinkedIn tab in the background and checks LinkedIn before it presses anything again, so nothing is sent twice.The same goes for a browser or extension restart and a lost connection: the step finishes once the browser is back. The extension runs an interrupted step again in place, and a step cut off four times stops, reads Interrupted, and waits for Retry.A step where LinkedIn never answered a button, such as a laptop going to sleep right after Connect, also runs again. It checks the profile first: an invitation already pending counts as sent, and Connect still on offer is pressed again.Closing the tab yourself and a lost connection never count toward those four. A step that fails on LinkedIn is not retried this way: it stops only that contact.Closing the tab twice within ten minutes pauses steps in that browser. They wait until you click Resume in the extension’s side panel.
No. A step is skipped when there is nothing for it to do, such as a profile LinkedIn did not show, and the contact moves on to the next step. A failure stops the contact at that step instead.A connection request that can’t be sent is skipped too, but the contact takes a branch rather than the next step. Someone already connected goes down Connected, and anyone else goes down Not accepted.
Limits on the sender’s LinkedIn tab sets a daily and a weekly ceiling for each action. Leave a week empty for no weekly limit. Connection requests always keep one.Messages and InMails share one Send message limit. Daily ceilings reset at midnight in the sender’s timezone, and a weekly one counts today and the six days before it.Lower is safer: LinkedIn polices volume on its own terms and the limits exist to keep you under its radar, not ours.
Their sequence’s sending window, in the sender’s timezone. Outside it a step waits in line, and the sender’s LinkedIn tab and the extension’s side panel read “Outside sending window”.Checks of your own inbox, sent requests and new connections run at any hour, and so does a step from Try a step. See Schedule and sending window.
At least the Time between steps set under Limits on the sender’s LinkedIn tab, from 1 to 60 minutes. Steps run one at a time, and each wait runs a little longer at random, so steps never land on a steady beat.The sender’s LinkedIn tab and the extension’s side panel say why the next step waits, and until when. It reads “Next step in 47 seconds · Time between steps”, for example. A limit reads the same way: “Next step in 6 hours · Daily limit reached”.The wait belongs to the sender’s LinkedIn account, not to a sequence. Two sequences sending as the same sender share it, so a longer wait slows both.Checks of your own inbox, sent requests and new connections wait only a minute or two after a step, and never hold up the next one.
Yes. Open the step and choose its LinkedIn preview tab. It resolves the message against a real contact and sends nothing, and it costs no credits.
Yes. A Send connection request branches on its own answer, into Connected and Not accepted. It sends contacts who are already connected down Connected, so it needs no Already connected? check before it.The step picker’s Then check… group carries the other LinkedIn conditions: Has a LinkedIn URL?, Already connected? and Has an open profile?. Use them to skip a step rather than waste it. See Branch on a condition.
Connection requests today is how many of today’s connection requests that sender has sent against its cap. Profile views and messages keep their own caps on the sender’s LinkedIn tab, which is also where the account it is bound to is named.On a narrow list, such as beside the AI Assistant, Mailboxes gives way first, then Connection requests today, LinkedIn and Sent today / daily send limit. The sender’s name always shows, and a wider window brings the rest back.
It works through the session your browser already holds. There is no password or cookie to hand over, and disconnecting it stops the queue without touching your LinkedIn account.

​
Next steps

Build a sequence

Put those steps in order alongside email.

Branch on a condition

Send contacts down different steps on a reply or a fact.

Connect LinkedIn

Connect the extension and watch the steps it runs.

Tasks

Approve or reject the LinkedIn steps waiting on a person.

Senders

Set up the sender the LinkedIn account belongs to.