Outbound email
Email sequencer wired to the table that built the list
The list and the cadence stop being two products. You enroll rows straight out of the table that built them, and every send carries the run that authorized it.
Most sequencers begin where your data ends. You export a CSV, upload it somewhere else, and the campaign starts drifting from the table you actually maintain. Here the cadence reads the same rows the enrichment wrote, so enrolling is a filter, and a row you disqualify later stops the enrollment it is sitting in.
A sequence is a versioned program of ordered steps with its own senders, daily caps, and sending windows. A step can be email, a LinkedIn touch, a WhatsApp message once that sequence carries its cold-initiate opt-in, or a task in HubSpot, with further CRMs landing on the same adapter contract. Suppression and reply-stop run before a step fires, never as cleanup afterwards.
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.
Cadence from a sourced table
enroll every qualified row in my series A table into a four step email cadence
Enrollment resolves each row's channel, checks suppression first, and reports which rows were skipped and why.
Draft with your own positioning
write a three step cold sequence for fintech ops leads using our offers and proof points
Drafting reads the workspace wiki for voice and campaign learnings, and records which revisions grounded the copy.
Stop on the first reply
pause anyone who replies and tell me which step they replied to
Reply-stop exits the enrollment, cancels the steps still queued, and drops the thread into the shared inbox.
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.
From sourced rows to a live cadence
A table of qualified accounts becomes an enrolled sequence with no export step in between.
- 1Filter the table to rows with a verified address and a reason to write.
- 2Create the sequence from a steps file, attach senders, and read the preview before starting.
oxygen sequences createLet the workspace write the draft
Opening steps carry your positioning and the objections earlier replies already surfaced.
- 1Fill the offers, voice, and positioning pages once so drafting has something real to read.
- 2Draft the sequence, then edit the steps by hand before any sender is attached.
oxygen sequences draftLet the funnel choose the variant
Two variants run against the same list and the numbers say which one earned replies.
- 1Add a deterministic variant on the one step you actually want to test.
- 2Read per-step sends, replies, and deferrals once the window is wide enough to mean anything.
oxygen sequences analytics
Capabilities
What you get
Enrollment instead of export
Rows move into a cadence in place and keep their provenance. The filter that qualified an account is the filter that enrolled it, so there is no second list to maintain.
Senders that own their limits
Daily caps, sending windows, and per-account spacing belong to the sender, not to a prompt. A mailbox that starts bouncing is paused before it drags the pool down.
One person across channels
A sender profile ties a mailbox, a LinkedIn seat, and a WhatsApp number to a single identity, so a multichannel cadence does not read like four strangers.
Free to build, paid to send
Writing steps, previewing, and enrolling are unmetered. AI drafting spends model inference like any other AI step, and it is a paid plan plus a connected mailbox that turns a finished sequence into a dispatched one.
Boundaries
What Sequences does not own
Sequences decides and sends. It does not hold the conversation: bodies, threads, and replies live in Messages, which the shared inbox reads. Broadcast content belongs to Posts and is delivered by Publishing.
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.

Instantly
Sending accounts and campaigns on an Instantly workspace you already pay for, driven from here instead of rebuilt.

Smartlead
Keeps an existing Smartlead campaign running while the list, the enrichment, and the reporting move over first.

Salesforge
Sending infrastructure on the Forge stack, for teams whose mailboxes already live there.

Lemlist
Delegated dispatch for a workspace with Lemlist sequences and copy worth keeping through the move.

HubSpot
Task steps resolve and write into a connected HubSpot CRM; other CRMs implement the same adapter contract as they register.
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
- Delegated sending means the other platform still owns its warmup and limits. Oxygen mirrors status, provider ids, and errors back, but cannot repair a reputation problem inside an account it does not run.
FAQ
Questions people ask first
Do I have to export a CSV to enroll?
What happens the moment someone replies?
Can I keep the sequencer I already pay for?
Is multichannel one sequence or several?
What does sending actually cost?
Can I build the whole thing before paying?
Run email sequencer wired to the table that built the list 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.