Local leads across cities, n8n, UI and API
Twenty-city deduplication, an importable scheduled n8n HTTP template, and an evidence-based alternative to maintaining scraping scripts.
OwnerClue · Updated
The same business category across 20 cities
Use one multi-city campaign, preview its expanded locations and maximum volume, then run it with a clear cap. Campaign deduplication uses business identifiers, with name plus address as a fallback. It does not collapse separate branches just because they share a domain. Keep the full CSV business_id for later comparisons.
Deduplication inside a campaign is different from being new to your CRM. Use the list workbench to compare a completed export with your cumulative previous list. Matching supports business_id, Place ID, CID, location map URLs and name/address aliases. Rows lacking those identifiers remain in the result and are reported for review.
n8n: create, poll, retrieve and export
OwnerClue exposes the same account-scoped search/results/export services to its UI and customer API. Use a stored API credential with read/write scopes, a real location code, and one idempotency key per unchanged task. Poll at least five seconds apart, stop on a failed/stopped outcome, and export only after completion. API results use pagination; keep limit and filters unchanged while passing nextCursor until null.
Download the manual HTTP polling template or the new weekly Schedule Trigger template. Both import inactive, contain no credentials, and require your real city code and n8n HTTP credential before use. The weekly version adds a Monday trigger; it does not silently send emails or push contacts into a CRM. Review the expected paid search usage before publishing it.
The template's downloaded CSV is the handoff. Compare it with a prior export in the workbench, or connect your own persistent CRM/Data Table deduplication step before outreach. n8n's documentation explains why workflow static data is not a reliable manual-test history store; use a persistent table for a cumulative production history. No native OwnerClue scheduling or completion webhook is promised.
Replacing an Apify workflow without moving all the maintenance
OwnerClue is a candidate for this bounded task: search supported local-business locations, review website evidence, filter and export. A teammate can use the UI while automation uses the API. It is not a general replacement for arbitrary Actors, custom websites, session/cookie scraping or a proxy platform.
Outscraper documents asynchronous tasks, while Apify's Maps actor API provides another comparison route. Evaluate request schemas, pagination, failure recovery and the fields you actually need. An API label alone does not show how much ongoing maintenance is removed.
Verification and remaining boundaries
The weekly template's structure and Code-node guards are checked locally. It has not been activated in your n8n account. Existing OwnerClue production acceptance evidence covers one three-record search and CSV export; it does not establish a twenty-city coverage benchmark or an n8n end-to-end run. See the evidence example, API limits and n8n setup before production use.