Pull live hiring signals from job boards straight into your profiles. Lead scraping runs inside each Ideal Client Profile (and Reverse Market Profile) via the Job Board Monitoring slide-out — no separate scraping page to manage.
Supported sources
SEEK — Australia and NZ job listings. Runs on a schedule.
Indeed — AU, UK, US, NZ, CA, SG job listings. Runs on a schedule.
LinkedIn — AU, UK, US, NZ, CA, SG job listings. Runs automatically on a schedule, or trigger it with Refresh now.
Reed — UK job listings. Runs on a schedule.
SEEK, Indeed, LinkedIn, and Reed all run automatically on a schedule. You can also trigger any source with Refresh now when you want it.
Real-time progress shows new vs skipped leads with title clustering. Leads are automatically ranked by recency — HOT (≤7 days), WARM (≤14 days), MONITOR (≤30 days), then LOW for older roles — so the freshest hiring signals surface first.
Job board monitoring
A monitoring refresh runs across multiple sources — LinkedIn, SEEK, and Indeed — in one action, pulling live hiring signals straight into your profiles. Search keywords are inline-editable, so you can tune what each refresh looks for without rebuilding a config. Fresh roles flow into each profile's Pipeline Matches tab (companies already mapped) and New Leads tab (quality roles at companies not yet mapped).
Multi-source refresh — one refresh covers LinkedIn, SEEK, and Indeed together.
Inline-editable keywords — edit the search keywords in place to retune what the monitor surfaces.
LinkedIn runs on a schedule — automatically pulls fresh roles, and you can also Refresh now on demand.
Search Configs
Search Configs are reusable search templates that define what jobs to look for. A profile's Job Board Monitoring uses these configs to know which roles to pull. Save one per search you run regularly and the monitor picks it up.
Name — a label for your reference (e.g. "IT Managers in Sydney")
Sector and Discipline — industry and function categories
Keywords — terms to include (must match) and exclude (filter out). Keywords are inline-editable from the Job Board Monitoring slide-out, so you can retune a config in place between monitoring refreshes. Auto-suggested excludes help remove irrelevant job titles with one click.
Locations — city or region to target
SEEK Classification — select an industry classification code to narrow SEEK results (25 categories, auto-mapped from your sector)
Active toggle — enable or disable a config without deleting it
The AI Config Generator can create 2–5 configs from a plain English description — just tell it what you're looking for.
Smart filtering
AI Relevance Filtering — off-topic leads are filtered out by sector and keyword relevance, removing noise automatically
Smart Title Filtering — shared keyword matching across all scrapers ensures only relevant job titles are imported
SEEK Exact Phrase Matching — keywords are sent as exact phrases to keep results tightly on-topic
Diminishing Returns Cutoff — SEEK scraping automatically stops when no new leads are found, saving your scrape allowance
Scraping is free within your monthly allowance. For current plan limits, see the Credits and Plans page.
Where your data goes
Each scrape creates two records per lead:
Job listing — the role itself (title, company, location, salary, description)
Contact — the hiring contact (name, title, company — email found later via enrichment)
Both are automatically linked to a Company record, matched by company name.
Source-by-source tips
SEEK — AU/NZ only. Best for volume. Uses SEEK Classification codes for precision. Up to 20 pages per keyword. Auto-stops when no new leads are found. Runs on a schedule.
Indeed — AU, UK, US, NZ, CA, SG. Page 1 per location only (anti-bot limits). Good for broad geographic coverage. Runs on a schedule.
LinkedIn — AU, UK, US, NZ, CA, SG. Cards-only (title, company, location, date). Best for professional or executive roles. Runs on a schedule, or Refresh now on demand.
Reed — UK only. Free REST API. Joins keywords with OR. Good coverage for UK roles. Runs on a schedule.
Looking to import contacts from a spreadsheet? Use People → Import CSV instead.