Map Extract
Automation and profiles

Lead generation workflow automation with saved sources and profiles

Connect source steps into a saved workflow, start supported discovery modules from one place and keep each browser account in its own profile. Workflow Builder defines the process, Run Centre controls connected runs and Browser Profiles keep identities apart.

  • 3 modules on this page
  • Windows desktop app
  • Included in every licence

At a glance

The short versionSet it up once, then repeat and control it.

What it is

Tools that save your search recipes, control running jobs and keep each browser account separate.

What it does

  • Saves which sources to use and in what order
  • Starts, pauses and stops runs from one screen
  • Keeps a separate browser profile per account

How it helps your business

Repeat the work that went well without setting it up again, and keep accounts and long runs under control.

Good for

  • Repeating a search for new towns
  • Pausing and resuming long runs
  • Managing several accounts

Suitable for

  • Sales teams
  • Lead generation agencies
  • Marketing agencies
  • Data and research teams
Plain English: what the terms mean (2 terms)
Workflow
A saved recipe of steps and sources the software follows.
Browser profile
A separate saved browser with its own logins and cookies, so accounts do not mix.

See it in action

Save the order of your sources once and reuse it.

Illustrative recipe. Which sources are on is your choice. Motion is reduced, so the finished scene is shown.

Step by step

  1. Nine sources are available: Google, Bing and Apple Maps, Google and Bing search, Trustpilot, Facebook, Instagram and website crawl.
  2. Search, Facebook, Instagram and website crawl start off. You switch two of them on.
  3. You put the sources in the order you want them to run.
  4. Save the recipe, for example “Joiners, North West”, to reuse it.
  5. On a run, sources work side by side, each in its own browser, taking turns.
Modules

Choose the module for the job.

Build scraping workflows, control connected discovery runs and reuse browser accounts.

How they connect

One project, passed from step to step.

Records are kept in one local project on your Windows PC, so each module picks up where the last one finished.

  1. Build the workflow

    Choose supported source steps and review their settings.

    Scraping Workflow Builder
  2. Choose the identity

    Check the saved browser account the module needs.

    Browser Profiles
  3. Run supported modules

    Start connected discovery tools and inspect their results.

    Run Centre
Use cases

Where it fits.

  • Repeat a lead generation process

    Save a source workflow for a search you run every month.

  • Separate client identities

    Keep authorised browser accounts apart and confirm the active account before an action.

  • Coordinate discovery

    Start supported social discovery modules from one control point in Run Centre.

Questions

Frequently asked questions

Does Workflow Builder automate every module?

No. It prepares supported source steps. Publishing, outreach and specialist tools keep their own controls.

What does Run Centre start?

It coordinates connected social discovery modules. Its controls show which modules are available.

Why use separate profiles?

Each profile keeps its own account session, so you choose the authorised identity for each task.

Does switching profile get around restrictions?

No. Never use profiles or account rotation to evade restrictions or objections.

Where are results stored?

In the relevant local project and module storage. A shared launcher does not merge every database.

Can I work offline?

You can prepare local settings offline. Online discovery and account actions need a connection.

Keep going

Works well with

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top