Recipe · Outbound email
Prepare the outreach list
Takes every queued row, checks the address against your verification connector if you have one, then asks your model for the four values the messages are built from: the person's actual first name, what their company is called out loud, what a local calls their area, and one sentence about them grounded in the Signal you recorded. Moves the row to Prepared. Addresses that do not exist go to Bounced instead and no touch reads them. Run this first — touch 1 skips any row with no cold read, because that sentence is the whole first line of the message.
On this page
What it does
Each row costs one model call, and a verification check spends a credit on your own account if you have a verifier configured. Both are optional to set up; without a verifier the column simply stays empty.
Checks each queued address, then writes the four values the messages are built from — including the one sentence about that person that opens the email.
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 9 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 queued rowsLoad Outreach list into rowsloopEach personLoop forEachEach time
setVarStart this row uncheckedSet verdictverifyEmailCheck the addressCheck {{loop.item.email}} is realon failure: continuesetVarTake the verdictSet verdicton failure: continueifStop the dead onesIf {{vars.verdict}} equalsYes
saveRowsMove it to BouncedSave to Outreach liston failure: continueNo
aiPromptWrite the variablesAsk AI into cleanon failure: continuesaveRowsFile the variablesSave 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
- company_casual
- Company (casual) · text
- location
- Location · text
- location_local
- Location (local) · text
- icp
- Segment · text
- metric
- Metric · text
- signal
- Signal · longText
- cold_read
- Cold read · longText
- consent
- Consent · select · Cold — no consent | Opted in
- status
- Status · select · Queued | Prepared | Touch 1 sent | Touch 2 sent | Sequence finished | Replied | Booked | Unsubscribed | Bounced | Refused
- touch
- Touch · number
- deliverable
- Deliverable · select · Deliverable | Risky — catch-all | Undeliverable | Could not check
- last_sent_at
- Last sent at · datetime
- touch_1_day
- Touch 1 day · date
- 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.
Outreach touch 1
Pick your mailbox on the Send touch 1 step, or name a pool, and read the three copy parameters before the first run. Mail cannot be recalled.
One profile · Opens no page · The Outreach list table · 5 settings on the run
Outreach touch 2
Pick your mailbox and read the copy parameters. It will not mail a row the same day touch 1 did, but the spacing beyond that is how often you schedule the sequence.
One profile · Opens no page · The Outreach list table · 5 settings on the run