Keep your Woodpecker prospects clean and deliverable
Woodpecker's Bounce Shield checks an address before it sends and marks hard-bounced prospects so it stops mailing them, but it can't reliably judge a scraped or imported address it has never contacted, and those never-verified invalids are exactly what burns a cold sending domain. Qualisend closes that gap: the native Woodpecker connector verifies your prospects in place and writes the results back, or you can verify at the point of capture with the REST API before a lead ever becomes a prospect. Here's the fastest path, plus the manual CSV loop and no-code options.
Connect Woodpecker and clean it in place
Connect Woodpecker and Qualisend verifies your prospects before they enter a sequence. Clean the lists you've already loaded, check every new lead in real time, and keep the invalid ones out — so bounces never burn the domain your outreach sends from.
Prefer to work by hand, or verify at signup through your own stack? The CSV export → verify → reimport loop below and the REST API are fully supported too.
Connect WoodpeckerWhat Woodpecker cleans for you
Woodpecker's native hygiene runs on Bounce Shield and its prospect status model. Bounce Shield verifies an address around send time and can pause or skip a prospect that looks unsafe, and once an address hard-bounces the prospect is marked BOUNCED and dropped from the remaining steps of the sequence. The company Blocklist lets you permanently exclude specific addresses or whole domains so they're never contacted again, and a blocklisted address can't be re-added by a later import. For prospects Woodpecker has actually attempted, that is genuine, automatic protection.
What it can't catch
The limit is that Bounce Shield's pre-send check works at the syntax, MX, and basic mailbox level, so it can't reliably call a catch-all domain that accepts everything then quietly discards it, a disposable domain built to expire, a role address like info@ or sales@, or a mailbox that has decayed since it was scraped. Its strongest signal, the BOUNCED status, is reactive: it needs a real send and a real bounce to fire, and by then the bounce has already counted against your sending domain. Cold lists make this the common case rather than the exception, because a scraped or imported prospect list arrives with its bounce history stripped, so an address that was already failing in another tool looks brand new to Woodpecker. Every one of those addresses sits ACTIVE in your campaign until the first send proves otherwise.
Why a clean Woodpecker list matters
On cold outreach the stakes are unforgiving, because a campaign lives or dies on its bounce rate and the reputation of the mailbox and domain it sends from. Woodpecker's plans meter the prospects you contact each month, so every message spent on a dead address is wasted send volume as well as a bounce you can't take back. One unverified import can spike your hard-bounce rate, and under Gmail and Yahoo's 2024 bulk-sender rules a domain that bounces and draws complaints past their thresholds gets throttled or filtered across the board, not just for the campaign that caused it. A cold domain is slow and costly to warm and nearly impossible to fully rebuild once it's burned, which is why verifying before the send is non-negotiable here.
Prefer CSV or the API? Here's the manual path
In cold outreach the highest-leverage move is to verify a prospect before it ever enters a sequence, so a bad address is caught before Woodpecker sends and never gets the chance to bounce against your domain.
Export your prospects from Woodpecker
Open Prospects, or a campaign's Prospects tab, filter or select the prospects you want to check, and use Export to download them as a CSV. Do this before you launch a new campaign, while the list is still freshly scraped or imported.
Verify the file in Qualisend
Upload the CSV to Qualisend bulk cleaning, up to 1,000,000 addresses per job with duplicates charged once and live progress. The free plan's 100 credits that never expire cover a first sample.
Read the results
Every address returns deliverable, risky, undeliverable, or unknown with a reason code and sub-flags (catch-all, disposable, role, full mailbox), plus the MX provider and SMTP probe detail as evidence and a 0-100 confidence score. Download the cleaned CSV.
Keep the invalids out of the sequence
Filter to undeliverable and add those addresses to Woodpecker's company Blocklist so they're never contacted and can't be re-imported, or remove them from the campaign before it sends. Blocklisting is the durable move, since a blocklisted address stays out even if the same scrape lands in your account again.
Or automate it at signup
Prefer to keep junk out from the start? Verify at the point of capture with the Qualisend REST API (scoped keys, rate limits, webhooks), or wire a Zapier, Make, or n8n flow so a lead from your scraper or CRM is checked and only added to Woodpecker as a prospect if it comes back deliverable, so a disposable or dead address never enters a campaign or spends a send.
What Qualisend flags on every address
- Never-verified invalids that would hard-bounce on your first send and push the prospect to BOUNCED
- Disposable / throwaway domains built to expire, common in scraped lists
- Role addresses (info@, sales@, support@) that draw complaints and rarely reply
- Catch-all domains, flagged so you can segment them into a throttled, low-volume campaign
- A 0-100 confidence score and machine-readable reason code for every address
The native Woodpecker connector is live — connect it in Qualisend under Integrations and clean your list without a single CSV. New contacts are verified automatically, and you can re-verify on a schedule.
What to do with each result
Every address comes back with a verdict and sub-flags. Here's the action that keeps your Woodpecker list clean without throwing away contacts you can still reach.
deliverableKeep in the campaign and send as normal.deliverable + role flagSend with care: pull info@ and sales@ into a separate low-priority campaign, or skip them, since they rarely reply and can draw complaints.risky + catch-all flagSegment into a separate campaign and throttle: send at low volume from a warmed mailbox rather than blasting.risky + disposable flagBlocklist it, the inbox was built to expire.unknownLeave it out for now and re-verify next clean; this is usually greylisting or rate-limiting, not a verdict on the mailbox.undeliverableBlocklist or remove it from the campaign before it sends; don't let Bounce Shield learn it the hard way with a live bounce.Related reading
Why verifying every address is step one of any cold campaign that reaches the inbox.
What actually keeps cold email landing: bounce rate, reputation, and clean lists.
Cleaning protects a warm domain; here's how to warm one before you send.
The 2024 bounce and complaint thresholds your Woodpecker sends have to clear.
Verify leads at the point of capture so junk never becomes a Woodpecker prospect.
Woodpecker verification FAQ
Clean your Woodpecker list in minutes
Start free with 100 credits that never expire — no card required. Connect, verify, and protect your next campaign.