OXYGENOXYGEN

LinkedIn outreach

LinkedIn outreach on a seat, not a per-action meter

A connected LinkedIn account is a $30 monthly seat and every action on it is free at use. Invites, messages, visits, follows, and comments run on the engine that already drives your email.

try

Per-action pricing turns a LinkedIn motion into an accounting exercise. You ration invites against a meter instead of against what the account can safely do this week. Oxygen prices the account itself: one sending seat a month, with no charge for an invite, a message, an InMail, a profile visit, a follow, or a comment.

A step can visit a profile, send an invite, wait for the acceptance, then send a DM, and the sender's daily caps and human-like schedule decide when each one fires. Scope is explicit too: a newly connected account admits only conversations this workspace started, so personal threads stay private.

Example searches

Ask for it the way you'd say it

Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.

  • Warm invites from your own post

    invite everyone who reacted to my launch post and reference the post in the note

    Engagers land in a table before anything is queued, so the list is still free to cut down.

  • Wait for the accept, then write

    message people two days after they accept my connection request, never before

    The connection wait is its own step, so the DM fires only for enrollments that actually cleared it.

  • Slow down a fresh account

    cap this account at a handful of invites a day until it has been running two weeks

    Limits and ramp are configuration on the sender, so no sequence can talk the account into exceeding them.

Plays

Three motions you can run this week

Each one is a chain of Oxygen primitives — the same hosted objects your workspace already has, composed.

  • Post engagers into a capped sequence

    People who engaged with your content get a warm invite instead of an unexplained cold one.

    1. 1Harvest the reactors and commenters on an owned post into a workspace table.
    2. 2Drop anyone already in a live conversation, then enroll what is left under the daily cap.
    oxygen engagement harvest
  • Invite, wait, then a real message

    A three touch program that never messages somebody who has not accepted the request yet.

    1. 1Order the steps as visit, invite with a note, connection wait, then DM.
    2. 2Preview against a handful of enrollments before you start the whole list.
    oxygen sequences start
  • One identity, two channels

    The email follow-up arrives from the same person whose invite the lead already accepted.

    1. 1Create a sender profile binding one mailbox and one LinkedIn seat to a single person.
    2. 2Attach that profile so a channel switch does not switch the human behind it.
    oxygen senders profiles create

Capabilities

What you get

  • A seat, not a meter

    Thirty dollars a month per connected account covers invites, messages, InMail, visits, follows, and comments. Volume planning becomes a question of account safety, not budget.

  • Limits that live on the account

    Caps, spacing, working hours, and a ramp for a new account are sender configuration. The sequence asks for a step; the sender decides whether today is the day it goes out.

  • Provenance-scoped conversations

    A restricted sender surfaces only threads Oxygen opened, proven by the chat it created or the invite it sent. Widening that scope is a deliberate setting, never a default.

  • Checkpoints you can see

    When LinkedIn asks an account to solve a checkpoint, the sender shows it and the queue holds. Nothing keeps hammering a restricted account while the campaign looks healthy.

Boundaries

What Sequences does not own

This is Sequences running net-new outreach. Answering inside a thread that already exists is Messages and happens in the shared inbox. Publishing owns anything broadcast to your own feed, and the durable person behind an enrollment is a Records object.

Data sources

What the data actually comes from

Every value lands with its provider and cost recorded on the cell.

  • LinkedIn

    Your own connected account. The monthly seat is the price, and invites, messages, and visits carry no per-action charge.

  • HeyReach

    Dispatch through an existing HeyReach workspace for a team with campaigns there it does not want to rebuild.

  • GetSales

    A second delegated path for sending and inbox sync on accounts already wired into GetSales.

  • LinkedIn Scraper

    Public profile and post reads without connecting an account, which is how engager lists get built before an invite is queued.

Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.

Limits

Where this stops

  • LinkedIn decides what an account may do. Caps, ramps, and spacing reduce the risk of a restriction; nothing removes it. Treat a freshly connected account as a slow account for its first few weeks.

FAQ

Questions people ask first

How is LinkedIn priced here?
As a sending seat: $30 a month per connected account, billed in dollars alongside your plan. Actions on that account are free at use, so an invite, a DM, a visit, and a comment all cost nothing extra.
Will this get my account restricted?
Any automation carries that risk, and anyone promising otherwise is selling. What the product does is bound it with per-account caps, spacing, working-hour windows, a ramp, and a queue that holds on a checkpoint.
Can I run LinkedIn and email in one program?
Yes, and it is the normal shape. Steps of both channels sit in one ordered sequence, and a sender profile keeps the same human behind the invite and the email that follows it.
What shows up in my inbox after connecting?
Only conversations this workspace started, evidenced by a chat Oxygen created or an invite it sent that the person answered. Threads predating the connection stay hidden until you widen the sender scope.
Do I need a Sales Navigator subscription?
Not for the core motion. Invites, messages, visits, follows, and comments run on an ordinary connected account. InMail draws on whatever credits your own LinkedIn subscription provides.
What happens to invites nobody accepts?
They stay pending and keep counting against the weekly allowance LinkedIn gives the account, which is why the invitation list is inspectable and withdrawable. Clearing old requests is the cheapest way to get capacity back.

Run linkedin outreach on a seat, not a per-action meter on your own workspace

Sign up, get a working workspace with a one-time credit grant, and run the first play from the web app, the CLI, or your AI assistant over MCP.