Clean up your contact list before the next import. Spot formatting issues and possible duplicates, compare suggested changes, and keep the originals while you decide.
Customer-facing changes and compatibility notes. See the README for current pricing, supported file sizes and recovery guidance. A saved task may use an older build; preserve original files before changing an established workflow.
October 9, 2026 — approved-change handoff in the 4.3 family
A separate file containing only the changes you approve. Use a decision template to select changes, then prepare an original-column copy with those edits. The change record identifies the exact cells changed; the reversal plan relates only to that generated copy. Stale or conflicting approvals withhold the copy rather than applying a partial selection. Ordinary review, duplicate findings and accepted-row pricing remain unchanged. No CRM import or automatic merge is performed.
Each run is a new review at the normal accepted-row price, including a valid review whose import copy is withheld. Extra handoff files and cell changes add no separate charge. Whitespace-only CSV records retain their original literal cells in the complete prepared copy. Existing deadline, uncertain-commit and no-replay handling remains in effect.
October 9, 2026 — bounded result writes
Clearer handling when saving results takes too long. A stalled result write now stops waiting within the review's time budget. If the platform may already have received it, the run keeps that uncertainty visible rather than sending the same records again. Check the existing run before starting another review. Inputs, review rules and prices are unchanged.
October 8, 2026 — maintenance update in the 4.3 family
A clearer starting guide puts the first review and its price before advanced settings. Invalid or zero spending-cap settings are rejected earlier, before unnecessary source preparation. Existing valid inputs, contact suggestions, returned-file review and prices are unchanged. This does not add contact verification or automatic CRM updates.
4.3.0 — October 4, 2026
Check a returned file against the changes you approved. Compare your original records, a returned file and an independent approval list. See missing corrections, unexpected edits, missing rows and additions in the readable review and detailed result.
The check uses exact row keys and before-revision/value declarations. It does not approve a supplier, merge contacts or update a CRM. Findings and after-only rows add no separate charge; billing still uses accepted original review rows. The two supported narrow/wide file profiles remain separate.
4.2.0 — October 2, 2026
Clearer handling of interrupted reviews. A checkpoint helps prevent the same interrupted run from submitting billable rows again. A stopped worker is no longer described as a completed review. Inspect saved output and charge information before starting another run; missing acknowledgement is not proof that nothing happened.
The application package was reduced and import guidance clarified. This is not a measured cloud-speed improvement. The review page remains read-only: make approved edits in your own copy of the full file.
4.1.0 and 4.0.0 — September 23, 2026
Review displays now distinguish no possible matches from matches omitted by a display limit.
Existing API inputs: rename the inactive dedupeKeyMode setting to legacyMatchMode when moving to the current schema. Values and its lack of effect on cleanup, matching and charging are unchanged. Older build availability is not guaranteed indefinitely.
3.2.0 and 3.1.0 — September 2026
Clearer first-file preparation, original-versus-suggestion guidance, complete-file links, price examples and safe support instructions. Possible duplicates remain a human decision, not an automatic merge. Separately tested file sizes must not be combined into a larger capacity claim.
3.0.0 — September 16, 2026
Protection for stored inline input. Both inline contact arrays use Apify secret protection. Submit original JSON rather than copying stored ciphertext into a new run. This does not encrypt uploaded files or results, or retroactively protect older plaintext inputs. Those retain their own access and retention settings.
2.2.0 and 2.1.0 — September 2026
Added an explicit example-or-file starting choice, a read-only Contact review page, clearer preparation errors and current-run price checks. Extra source fields remain with the records. Review files are prepared before billable Dataset publication; uncertain publication is not blindly retried.
2.0.0 — July 27, 2026, with August input improvements
Introduced the whole-file review workflow and optional protected inline input. The Dataset is a review projection, not the complete import file: use the full CSV/JSON files and keep review-required records visible. Later releases added protection to both inline arrays and the input-name change described above.
