Recipe · Outbound email
Outreach touch 1
Sends the opening message to every cold row that is queued, one at a time from your own mailbox, through its proxy and inside its daily cap. Writes the outcome back to the row and moves it to Touch 1 sent.
On this page
What it does
Pick your mailbox on the Send touch 1 step and rewrite the body before the first run. Mail cannot be recalled.
Sends the opening message to every cold row that is queued — one at a time, from your own mailbox, through its proxy and inside its daily cap.
It runs against one profile, through that profile's own proxy and with its own cookies — so the pages load the way that account's owner would see them. It opens no page at all, which means it can be run against a profile whose session you would rather not disturb.
The 7 steps
The real tree, read out of the pack the launcher ships. Indentation is nesting: the steps under a loop run once per row, and the ones under a branch run only when the condition above them holds. Every {{…}} is a value filled in at run time — from the row being walked, from a setting on the run, or from the profile itself.
loadRowsLoad the rows ready for touch 1Load Outreach list into rowsevaluateStamp the runRun scriptloopEach personLoop forEachEach time
setVarStart this row with no outcomeSet outcomesendEmailSend touch 1Send "{{loop.item.company}} — quick question" to {{loop.item.email}}on failure: continuesetVarRecord what happenedSet outcomeon failure: continuesaveRowsAdvance the rowSave to Outreach liston failure: continueEach of those is one of the step types on the automation reference, with the same fields the editor shows and the same fields an agent is handed over the local API.
The tables it uses
These load with the recipe. A dataset is a typed table your workspace owns — the columns are named and typed up front so the steps can address them, and every one of them is yours to rename, extend or fill from a file afterwards.
Outreach list
readswritesOne row per person: their address, what you know about them, whether they opted in, and which touch of the sequence they are on.
- Email · email
- first_name
- First name · text
- company
- Company · text
- signal
- Signal · longText
- consent
- Consent · select · Cold — no consent | Opted in
- status
- Status · select · Queued | Touch 1 sent | Touch 2 sent | Sequence finished | Replied | Unsubscribed | Bounced | Refused
- touch
- Touch · number
- deliverable
- Deliverable · select · Deliverable | Risky — catch-all | Undeliverable | Could not check
- last_sent_at
- Last sent at · datetime
- outcome
- Outcome · longText
Re-running updates the row it already wrote rather than adding a second one. That is what the match column in the save step is for, and it is the difference between a status check and a table that doubles in size every pass.
Loading it
In the launcher, open Automations, choose Load a starter pack, and pick Outbound email. Untick anything you do not want. The tables land first, then the workflows, then a project called Outbound that links them together.
What arrives is an ordinary automation row. Open it in the editor, change a step, rename it, delete it — nothing in the app treats it as special afterwards, and loading the pack a second time makes a fresh copy rather than overwriting the one you edited. Tables are the opposite: an existing table of the same name is reused and keeps its rows.
The rest of the outbound email pack
They load together, share the tables above, and land in one Outbound project.
Verify the list
Each check spends a credit on your own verification account. Needs a verification connector — without one the pack still works, unverified.
One profile · Opens no page · The Outreach list table
Outreach touch 2
Pick your mailbox and rewrite the body. Schedule it days after touch 1 — three messages in one morning is not a sequence.
One profile · Opens no page · The Outreach list table
Outreach touch 3
Pick your mailbox and rewrite the body before the first run.
One profile · Opens no page · The Outreach list table
Opt-in broadcast
Opted-in rows only. Pointing an email service provider at a scraped list closes the account — that is their policy, not a setting.
One profile · Opens no page · The Outreach list table