Changelog

Latest developments

New features, improvements and fixes to Datablist.

Datablist updates — October 2026

Highlights

Run enrichments and sources from your own applications through the API

Work that previously needed a Datablist collection can now run inside your own application or automation workflow. The new Enrichments API works on records you already have, while the Sources API generates new lists from the settings you choose. You can submit work, follow its progress, and retrieve the results as JSON without creating a Datablist collection.

For example, send company names to Company Name to Domain API and write the returned websites back to your CRM. Or use Instagram Followers/Following Scraper through the Sources API to build a list from an Instagram profile. Both use your existing Datablist credits.

Get a Personal API Key and use it directly for your requests; Datablist handles token renewal. In the documentation, Try it lets you send a request and inspect its response before writing a script. Browse the available APIs or start with the API reference.

Improvements

Target Auto-Run enrichments with AND/OR condition groups

Auto-Run conditions used to be limited to a flat set of rules. For enrichments triggered by New items or Input changes, you can now combine AND/OR conditions and nest groups, so one rule can express the rows you want to process.

For example, run Company Enrichment only when a lead’s country is France or Germany and its website is not empty. Put the two country conditions in a Match any group inside a Match all group with the website condition. Only qualifying rows run; scheduled enrichments keep their existing condition limits.

Clone collections with their saved filters

Cloning a collection used to leave its saved filters behind, so a new campaign list needed the same conditions rebuilt by hand. The clone dialog now offers Clone saved filters, enabled by default when the source has saved filters. It also works when you copy selected rows into a new collection.

For a prospect list with saved filters such as Country is France and Email is empty, keep the option enabled to carry those filters into the copy. If a filter needs an enrichment-status column you have chosen not to copy, the dialog names the missing column before you continue. You can include the matching enrichment configuration or leave that filter out.

Clear collection filters in a click

Removing an active filter from the filtering dialog used to mean editing its conditions one by one. Clear filter now removes the active conditions and returns you to the full collection in one click.

Credit usage history separates app and API consumption

Credit usage history was built around collections, which made enrichment activity started through the API hard to review. The history now has separate App usage and API usage sections, so you can see where credits were consumed without looking for a collection that does not exist.

If you enrich a lead collection in Datablist and run a separate email-finding script, open credit usage to review each activity in its own section. Both show the enrichment or source, time and credit cost, while app rows also link to their collection. Load older usage extends the shared history; the summary totals still include both kinds of consumption.

LinkedIn People Profile Scraper adds a Skills output

LinkedIn People Profile Scraper can now return the skills listed on a profile. These names were previously omitted from the enrichment result even when the profile lookup contained them. Select the Skills output and map it to a text column alongside the person’s name, role and company.

A profile listing Python and SQL can produce Python, SQL in that column, ready for filtering or review when you build a recruiting list. The field stays empty when skills are unavailable, including in older cached profiles.

LinkedIn Company Page Scraper charges the same rate for numerical URLs

A numerical LinkedIn company URL could previously cost 75 credits when the lookup needed a fallback, compared with the standard 25-credit rate. LinkedIn Company Page Scraper now uses the same standard price for named and numerical company URLs. You can use either format directly.

For a list of 500 company pages, the standard estimate is 12,500 credits whether the URLs end in company names or numerical IDs such as linkedin.com/company/1234567890. There is no need to convert numerical URLs to named ones to avoid the former surcharge.

LinkedIn Search Scraper stops charging for unrequested email lookups

LinkedIn Search Scraper can return work emails already available with the imported profiles. Those addresses could previously trigger an email-finding fee even when no separate email search had been requested. The import now keeps the address without adding that unrequested lookup charge.

Map Known Work Email when importing a LinkedIn people search if you want to keep addresses returned with those profiles. A value in that column no longer adds an email-finding fee on its own; the normal price for your selected profile-scraping mode still applies.

Datablist updates — September 2026

Highlights

Broader LinkedIn profile coverage, even when you request pictures

The broader lookup path added to LinkedIn People Profile Scraper in August was skipped when a run requested profile or company pictures. It can now participate in those runs too, and Datablist can complete missing company details and images afterward.

For example, selecting Full Name, Current Company, Profile Picture, and Company Logo no longer reduces profile coverage just because image outputs are present. The scraper can first find the person through the broader path, then complete the requested picture fields when available.

Improvements

Easier-to-scan templates and a new customer-review workflow

Ready-to-use templates previously relied mostly on their titles and shared fallback icon. Key workflows now have their own visual identity, and Founders Finder, Employee & Talent Finder, and Trustpilot Reviews Scraper appear first in the source-template catalog.

The release also adds Analyze customer reviews, a ready-made OpenAI/ChatGPT template that turns a review and rating into a concise summary, sentiment, main topic, issue type, urgency, recommended action, and a Needs Review flag. For example, a mixed three-star review can be routed to manual review instead of being forced into a misleading positive or negative label.

No duplicate rows when Instagram scraping resumes

Long Instagram Followers/Following Scraper runs can span many pages and may need to retry or resume. When two pages overlap, the same Instagram user could previously be added more than once. Datablist now remembers the user IDs already accepted for that source run and filters repeats across pages and resumes.

If a 5,000-follower import stops at page 30 and you resume it later, followers already collected are not appended again. Duplicate-only pages still advance to the next page, the limit counts unique profiles, and usage for profile rows is based on the unique records returned.

One difficult company name no longer stops a domain search batch

Find Company domains from Company names now isolates invalid inputs and temporary search failures to the affected rows. Previously, a punctuation-only company name or one failed candidate query could interrupt useful work elsewhere in the same batch.

For example, a list containing Acme, ., and !? now marks the punctuation-only rows as empty input at no cost and continues processing Acme. If one country-specific candidate search fails, other country groups still run; a row with no verified domain returns a normal no-result outcome instead of crashing the batch.

See our guide to finding company websites from names for preparing company-name inputs.

Datablist updates — August 2026

Highlights

Turn cross-collection matches into usable result files

Cross-collection matching previously offered one detailed group download, which was useful for inspection but awkward for the next business step. The new Result files workspace creates a CSV for the exact outcome you need: Matched records, Needs-review records, Unmatched records, a Match crosswalk, or Detailed match groups.

For example, compare an event-attendee list with your CRM, select the attendee list as the source, download Unmatched records for net-new leads, then use the crosswalk to retain every attendee-to-CRM relationship. Row-based files keep the strongest candidate and include confidence and match reasons.

Improvements

Broader coverage in LinkedIn People Profile Scraper

LinkedIn People Profile Scraper now has an additional lookup path for profiles that do not require freshly fetched pictures. That gives cached and less commonly indexed profiles another chance to return structured data before the enrichment falls back or reports no result.

A LinkedIn URL that previously returned nothing may now produce the same mapped fields—such as full name, headline, location, current company, experience, education, and languages—without changing your configuration. Picture-dependent runs kept their existing lookup path at this stage.

Import jobs from Indeed search URLs

Indeed Jobs Scraper used to require rebuilding a search from keywords, locations, and country inside Datablist. You can now paste one or more public Indeed Job Search URLs and import the listings from searches you already refined on Indeed. Keyword-and-location searches remain available as an alternative.

Before launching, Datablist shows the estimated credit requirement from the number of URLs—or the number of keyword × location combinations—and the result limit. For example, two keywords across two cities create four searches, so you can see and adjust the maximum cost before the run starts.

Safer matches in Find Company domains from Company names

Find Company domains from Company names now compares normalized company identities across more candidate data while applying stricter website ownership rules. It rejects a hosted page when the domain belongs to the platform rather than the company and can use a row's country to separate businesses with the same name.

For example, a vacation rental listed on airbnb.com/rooms/... is no longer accepted as if Airbnb were the rental company's own website. For an ambiguous name such as Notion, adding the country helps prioritize the matching local company, and unreachable candidates no longer displace a verified live site.

Waterfall Email Finder waits for slow lookups without getting stuck

Some email lookups finish asynchronously. Waterfall Email Finder and Waterfall Personal Email Finder now keep polling those searches until they reach a final result, while using clear time limits and fallback behavior when a search takes too long.

For example, if a work-email lookup is still processing, Datablist waits for its final found/not-found answer instead of treating the intermediate state as the result. A timed-out path does not hold the whole run indefinitely; the waterfall can continue and avoids repeating the same lookup unnecessarily.

Follow our guide to scraping Indeed jobs for lead generation to build a job-based prospecting workflow.

Datablist updates — July 2026

Highlights

One run history for browser and cloud work

Runs started in the browser used to be visible mainly through the active task panel, while cloud runs had their own history. Enrichment and data-source runs now report into the same collection history with their progress, outcome, and execution origin.

Start a 5,000-row enrichment, close the task panel, and return to the collection later: the history still shows how many rows were processed, skipped, or failed. A browser icon identifies runs that need the originating tab to remain open; cloud runs continue independently.

Improvements

A clearer path from duplicate matches to the right cleanup action

Duplicates Finder used to make every cleanup look like a variation of merge settings. The results workspace now starts with the outcome you want: Remove duplicates, Merge and preserve data, or Custom with AI. It also keeps a bounded set of scored matches, so you can adjust the similarity threshold without rerunning detection.

For example, if two company records share a domain but contain different phone numbers, Remove duplicates warns that data would be lost and offers a switch to Merge and preserve data. Lower-confidence groups stay in Needs review, while safe groups remain ready for batch processing.

Auto-Run only when enrichment inputs change

Auto-Run could already process new rows or follow a schedule, but editing an enrichment input on an existing row still required a manual rerun. The new Run when inputs change mode watches the columns actually mapped into the enrichment—including variables used in prompts—and reruns only the affected row.

For example, if Company Name and Website feed Company Enrichment, correcting either value can refresh that company's outputs without rerunning the rest of the collection. You can also choose whether existing output values are skipped, only empty outputs are filled, or all outputs are overwritten.

Better fallback coverage in Company Enrichment

Company Enrichment now continues through more fallback paths when the first lookup cannot return a complete company record. The workflow is unchanged whether you start with a company domain or a LinkedIn company URL, but difficult records have another chance to return useful data.

For example, a domain that does not immediately produce a company size or location can continue to another matching path instead of ending the row early. Successful rows still return the familiar name, website, LinkedIn URL, industry, location, employee range, and founded year fields.

Dates stay correctly sorted after import and cloud sync

Datetime columns could behave differently depending on whether their values came from a local import or were downloaded from the cloud. Datablist now normalizes valid dates in the browser, so sorting, filtering, and processing use the same date values in both cases.

For example, sorting a Last contacted at column from newest to oldest now gives the same order after a CSV import, a page reload, or a cloud synchronization. Existing cached collections are corrected as they are read; invalid source values are preserved rather than silently discarded.

Delete several columns in one operation

Removing several unwanted columns used to trigger a separate collection update for each one. Datablist now deletes the selected columns as one operation, which is faster and gives the action one consistent success or failure outcome.

After an enrichment test, for example, you can select five temporary output columns and remove them together instead of waiting for the table to update five times.

Duplicates Finder recognizes common versions of the same email

Smart email matching used to miss contacts when one import contained a plain address and another contained an email link or display-name format. It now extracts addresses from values such as mailto:jane@example.com and Jane Doe <jane@example.com>, while keeping the stored cells unchanged.

It also treats jane.doe@gmail.com, janedoe@gmail.com, and janedoe+event@googlemail.com as the same Gmail mailbox. Those dot and domain-alias rules are not applied to business domains, where dots may identify genuinely different mailboxes.

Email waterfalls now recover from temporary rate limits

A temporary rate limit during Waterfall Email Finder or Waterfall Advanced Email Address Verification used to make that lookup step fail immediately. Each waterfall step can now retry short-lived throttling before moving on, while an overall time limit prevents a row from waiting indefinitely.

On a large lead list, a busy verification service can pause and retry instead of turning a potentially valid address into an avoidable missing result. If it still cannot answer, the waterfall continues to the next configured check and preserves a clear row-level outcome.

Enrichment search puts title matches first

Search used to treat a word in an enrichment title much like the same word buried in a description or output label. Datablist now gives title matches priority while keeping favorites, plan availability, and catalog ranking as tie-breakers.

For example, searching LinkedIn surfaces enrichments and data sources with LinkedIn in their public name before tools that only mention a LinkedIn URL as one possible input.

Export rows in the order you are reviewing them

A sorted Datablist view could previously become a differently ordered CSV or Excel file after export. The export dialog can now preserve the active sort, including for large exports prepared in the background.

If a lead list is sorted by Lead score from highest to lowest, check Order By Lead score and the downloaded file keeps that priority order. You can also add enrichment status and credit-cost columns to an export when you need to audit which rows ran successfully.

Ignore URL paths in Duplicates Finder

Duplicates Finder previously treated each URL path as a different value, even when the goal was to identify records that belong to the same website. The URL processor can now ignore paths and compare the host instead.

Enable Ignore paths to match values such as www.datablist.com, https://datablist.com/fr, and datablist.com/pricing. Leave it disabled when individual pages—such as product or profile URLs—must remain distinct.

Save an enrichment without starting a run

Configuring a new enrichment previously led directly into its first execution. A separate Save action now stores the settings, input mappings, and output mappings without processing any rows.

You can prepare Company Enrichment on Friday, have a teammate review the selected outputs, then launch it manually or enable Auto-Run later. Continue with Instant Run remains available when you do want to configure and execute in one session.

Select and delete several sidebar collections at once

Cleaning up a workspace used to mean deleting collections and folders one by one. The Data sidebar now has a bulk-selection mode where you can select several entries, review what will be deleted, and confirm once.

For example, after a campaign you can select its three import collections and their folder in one pass. The confirmation distinguishes data that remains recoverable from permanent deletion, so the time-saving action does not hide its consequences.

The export documentation explains the available formats and export options.

Datablist updates — June 2026

Highlights

Keep enrichments running automatically

Before Auto-Run, keeping an enriched collection up to date meant reopening the enrichment and starting another run by hand. Saved enrichments can now process new rows as they arrive or run on a daily, weekly, or monthly schedule in the timezone you choose.

For example, a lead collection can enrich every newly imported company automatically, while a weekly refresh can be limited to records that match a filter. Run Conditions and a maximum-row limit keep each automation focused. Auto-Run is available on the Growth plan.

Improvements

Add guidance directly to collection columns

A column name is not always enough to explain what should go into it. You can now add a description to any collection column and read it from the table header without taking up permanent space in the grid.

For example, a Lead status column can explain the allowed values, while an enrichment-created Confidence column can keep the action's original definition. Descriptions can include a simple documentation link and stay with the column across local and cloud workspaces.

Another verification path for Waterfall Advanced Email Address Verification

Waterfall Advanced Email Address Verification can now use an additional verification path when earlier checks cannot decide whether an address is valid. This is especially useful for catch-all domains, where a single check often returns unknown instead of a usable answer.

In the built-in waterfall, Datablist continues automatically until it finds a conclusive result. Teams using Custom Waterfall can also add the new option to their own sequence and still receive the familiar Email Status, Reason, Suggested Email, domain, and role-account outputs.

Create all enrichment output columns in one step

Enrichments with many outputs previously created and attached their new columns one at a time. Datablist now prepares every selected output column together, so the full output mapping appears in one operation.

For example, when a profile enrichment returns a name, headline, location, company, and profile URL, you can create all five destination columns at once instead of waiting for five separate table updates.

Drag collections exactly where you want them

Reorganizing a busy workspace used to make it hard to tell whether a collection would land above, below, or inside a folder. The Data sidebar now shows the destination while you drag and supports all three placements reliably.

You can move a Prospects collection into a Sales folder, place it between two existing collections, or drag it back to the workspace root. The sidebar saves the new order and folder structure immediately.

Safer reruns in Translate with OpenAI/ChatGPT

Translate with OpenAI/ChatGPT now marks each row as processed, skips blank inputs without charging credits, and reports an invalid API key or exhausted quota as a clear run-stopping error. Previously, these cases could leave a translation run with less useful row-level feedback.

If you translate a product catalog and rerun it after fixing one description, completed rows can be skipped, empty descriptions cost nothing, and a credential problem is surfaced immediately instead of producing a string of unexplained failures.

See the enrichment run documentation for configuring inputs, outputs, and execution.