Email Verification Recheck Planner — Reuse Fresh Results

Send only the emails that need a new verification

Turn a new email list and your previous verification results into a fresh TO_VERIFY queue. Reuse recent results, remove repeated requests within the batch, and route uncertain or expired results back for checking.

This is a provider-independent pre-processing step. It does not connect to mailboxes, send email or claim to verify deliverability. Place it before a paid verification Actor or service; it returns the addresses that still need that service.

Why use a verification recheck planner?

Recurring lead exports overlap. A generic deduplicator can remove identical rows, but it does not decide whether yesterday's verification is reusable or whether a newer uncertain result invalidated it. This Actor uses the latest timestamped result for each address and your freshness window.

The output explains every decision. Reused records include the prior status, timestamp, provider and age. Conflicting results at the same timestamp are sent for rechecking. Future timestamps, timestamps without time zones and malformed history rows are not trusted.

How to use it

1. Paste the email addresses you are about to verify.
2. Paste previous results with email, status and verifiedAt. The optional provider field is preserved.
3. Choose a freshness window. The default is seven days.
4. Run and send the TO_VERIFY JSON array to your chosen verifier.

Use the Apify API to integrate this step with n8n, Make or your own pipeline. Scheduling is available through saved Apify tasks. No external API key is required.

Input

{
  "emails": ["sales@example.com", "sales@example.com", "new@example.com"],
  "previousResults": [
    {"email": "sales@example.com", "status": "valid", "verifiedAt": "2026-09-30T00:00:00Z", "provider": "your-verifier"}
  ],
  "maxAgeDays": 7,
  "reusableStatuses": ["valid", "invalid"]
}

verifiedAt must be an ISO timestamp with a time zone. Map your provider's corresponding fields to these names before submitting. You control which statuses can be reused; adapt reusableStatuses if your provider uses names such as deliverable or undeliverable. Unknown and catch-all statuses are rechecked by default.

Output

Field	Meaning
action	reuse, verify, duplicate, or review
reason	The precise decision rule
duplicateOf	Original input row index for a repeated address
priorStatus, verifiedAt, ageDays	Evidence from the previous result
provider	Source label supplied with that result

The TO_VERIFY key-value record contains a unique array of addresses needing verification. The dataset preserves one decision per input row. Download JSON, CSV or Excel, or use the dataset API. OUTPUT contains all decisions, the queue and summary counts.

Pricing

$0.03 per delivered plan, for up to 50,000 input emails and 100,000 previous results, within a 15 MB input limit. Platform usage is included in the published pay-per-event model. Invalid top-level input does not generate the billing event.

The planner can reduce subsequent verification requests. It does not refund upstream scraping charges, call a verifier automatically, or promise a particular saving. At $0.60 per 1,000 downstream checks, avoiding more than 50 checks would exceed the planner's $0.03 fee, before any other workflow costs.

Matching and limitations

Domains are case-normalized and converted to IDNA. Local-part case, dots and plus tags are preserved to avoid merging potentially different mailboxes. Syntax screening is intentionally conservative, not a full RFC mailbox validator; unusual addresses are marked for review.

A reused historical result is not a fresh deliverability check. Addresses can stop working within the configured window. Choose the window and reusable statuses appropriate for your workflow. Only user-supplied data is processed; nothing is sent to an email service. Report issues or requested provider-field mappings in the Issues tab.

Use existing Apify datasets

Select Emails dataset and/or Verification history dataset to reuse completed runs directly. Each selected dataset replaces its corresponding pasted array. Set the field paths if your source uses different names: for example, data.email, result.status, or checkedAt. The history timestamp must be the time the address was actually verified, not the time it was exported or copied. This Actor never invents a freshness timestamp. Missing or invalid history records are counted in the summary and do not establish verification.

Dataset reads are paginated and request READ access only to the selected resources. The emails dataset supports 50,000 rows and the history dataset 100,000 rows, each within 7 MB of the selected fields. A dataset that changes during the read, returns incomplete pages, or exceeds these limits fails clearly. No verification provider is called, and no email is sent.