Push to Your Sequencer
Outcome: the finished list live in your sending tool, every personalization variable populated, and reply and bounce data flowing back into the table.
- Surface
- App
- Level
- Intermediate
- Uses
- Outreach integrations · export
- Credits
- 0
- Prerequisite
- Lessons 06, 08 and 09
Create the fields first
Most sequencers accept an import with unmapped columns and silently discard them. So the order is:
- Create every custom field in the destination —
opening_line,evidence,fit_score, whatever your copy uses. - Then map.
- Then export five rows.
- Then export the rest.
Skipping step 1 produces a campaign where every personalization variable renders as an empty space, and nothing in the export reports a problem.
Reference: Outreach integrations, Export.
The mapping
| Table column | Destination | Note |
|---|---|---|
first_name | First name | Cleaned, properly cased |
email | Verified valid only | |
company_name | Company | Cleaned for use mid-sentence |
title | Title | The verbatim original |
opening_line | Custom field | Must exist before export |
evidence | Custom field | Useful for reps reading the record |
domain | Website | The match key |
fit_score | Custom field | Lets reps prioritize manually |
Every variable your email template references must be populated on every row in the batch. One blank {{opening_line}} produces an email that starts mid-sentence, and most sequencers will send it rather than hold it. Add a formula column that checks all required variables are non-empty, and filter on it.
Campaign or list?
| Push to a campaign when | Push to a list when |
|---|---|
| The sequence is written and ready | Copy still needs review |
| Volume is within your daily sending limit | You are batching for later |
| The batch is homogeneous — one message fits all | Segments need different sequences |
| You want it sending today | A human should approve first |
The safer default for a first run is a list, reviewed, then moved into a campaign. Pushing straight to an active campaign means a mistake sends before anyone sees it.
The five-row test
Non-negotiable, every export.
Export five rows
To the real destination, not a test account nobody looks at.
Open them in the destination
Read every field on all five.
Preview the actual email
Most sequencers can render a preview with variables filled. Read it as a recipient would.
Check for empty variables
The failure this test exists to catch.
Then export the rest
And confirm the destination count matches what you sent.
Sending mechanics that affect your list
Two things worth knowing before the batch goes live:
- Daily limits. A warmed domain sends a limited volume per day. Exporting 2,000 contacts into a campaign that can send 50 a day means the last contacts are reached in six weeks — by which time your evidence has expired. Size the batch to the sending capacity and the evidence window together.
- Ramp. A new sending domain needs warming. Pushing a large cold batch through a fresh domain produces exactly the reputation problem lesson 06 was about.
Close the loop
Data flowing only one way wastes what you learn.
| Coming back | Write to |
|---|---|
| Bounces | Mark invalid, suppress permanently, flag for re-enrichment |
| Unsubscribes | Permanent suppression, all lists |
| Replies | Mark contacted, remove from other campaigns |
| Positive replies | CRM, and flag the account as engaged |
| Opens and clicks | Optional — useful for a phone follow-up trigger |
Without this loop, the same dead address returns from another source next quarter, and the same person gets sequenced twice.
Do this now
Create the custom fields
In the destination, before anything else.
Build the “all variables populated” check
A formula column, filtered on.
Map the fields
Export five rows and preview the email
Fix anything blank
Size the batch
To daily sending capacity and evidence window.
Export the rest, into a list first
Wire the return path
Bounces, unsubscribes, replies.
Check your work
- Custom fields exist in the destination before export
- Every required variable is populated on every row
- You previewed a rendered email, not just field values
- Batch size fits daily sending capacity
- Bounce, unsubscribe and reply data flows back
Where this breaks
Silent field dropping is the failure that ships. The export reports success, the campaign launches, and every opening line renders as blank — a message that starts mid-sentence, sent to a list you spent real money building. The five-row preview takes two minutes and it is the only check that catches this before the send.
Further automation
Once the mapping is stable, schedule it: rows that newly qualify get exported automatically as they cross the gate, rather than in batches someone remembers to run. Add a Slack alert per batch so the people receiving the leads know they arrived.
Next lesson
11 — Community intent signals, a source of people describing your problem in public.
Reference for this lesson: Outreach integrations, Instantly, Export, Webhooks.