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.

try
Start freeRead the docs

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

Each example is a request in plain words, with what it returns underneath.

  • 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.

    1. Tables
    2. Sequences
    3. Messages
    1. 1Filter the table to rows with a verified address and a reason to write.
    2. 2Create the sequence from a steps file, attach senders, and read the preview before starting.
    oxygen sequences create

  • Let the workspace write the draft

    Opening steps carry your positioning and the objections earlier replies already surfaced.

    1. Knowledge Graph
    2. Sequences
    3. Messages
    1. 1Fill the offers, voice, and positioning pages once so drafting has something real to read.
    2. 2Draft the sequence, then edit the steps by hand before any sender is attached.
    oxygen sequences draft

  • Let the funnel choose the variant

    Two variants run against the same list and the numbers say which one earned replies.

    1. Sequences
    2. Messages
    3. Dashboards
    1. 1Add a deterministic variant on the one step you actually want to test.
    2. 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 account, and a WhatsApp number to a single identity, so a multichannel cadence reads as one person, not several.

  • Free steps, metered AI drafts

    Writing steps, previewing, and enrolling are unmetered. AI drafting spends model inference like any other AI step. Connecting a sending mailbox, which needs a paid plan, is what 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

Data sources and CRM connections

  • 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.

Use managed credits where available, or connect a supported provider key on an eligible paid plan. Your provider bills its calls; OXYGEN adds a per-call platform fee. Signed-in CRM connections such as HubSpot have no per-call fee. Connected sending accounts reserve monthly credits. See pricing and supported integrations.

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?
No. Enrollment reads the table directly, so the filter that qualified a row is the filter that contacts it. Each enrollment links back to its row, which is how a later disqualification stops the cadence.
What happens the moment someone replies?
The enrollment exits, queued steps are cancelled, and the thread lands in the shared inbox with its sequence and step attached. The reply also emits a signal other automation can subscribe to.
Can I keep the sequencer I already pay for?
Yes. Dispatch runs through that connected account while the list, the enrichment, and the funnel view move here first. Status, provider ids, and errors are mirrored back, so one question needs one dashboard.
Is multichannel one sequence or several?
One. Steps of different channels sit in the same ordered program and the channel resolves per enrollment, so nobody is keeping parallel campaigns aligned by hand.
What does sending actually cost?
Email sends draw no per-message credits. The recurring cost is your plan plus the monthly connection fee each sending mailbox carries, listed on the pricing page.
Can I build the whole thing before paying?
Yes. Steps, previews, and enrollment are unmetered, and a new workspace starts with a one-time grant of 250 credits, no card, and no clock. AI drafting is the exception: it spends model inference like any other AI step. The wall is connecting a sending mailbox, which needs a paid plan.

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.

Start freeSee pricing