Skip to Content
SyncGTM PlatformCore FeaturesLead sourcing

Lead sourcing

Lead sourcing actions are different ways to find and import leads from the table. You can find and import leads in many different and creative ways inside the Sync GTM table.

Examples:

  • Scrape Hacker News, Product Hunt, SubReddit, directories, marketplace, Google News, etc to find high intent leads
  • Find companies using signals like recent funding, technology stack, and more
  • Find people based on signals like job changes, LinkedIn post reactions, and more
  • Import contacts from CRMs like HubSpot, SalesForce, PipeDrive for CRM Enrichment
  • Auto fill rows by sending data via WebHooks or run HTTP Requests

plus more..

All this is possible without leaving the table.

All lead sourcing actions

You can find all available lead sourcing actions on our Import Actions page .

Step by step guide to run a lead sourcing action

You can either run a lead sourcing action from the dashboard or from inside the table.

Importing from the dashboard

  1. Select one of the Import Templates from the dashboard
  2. Set the input fields and run the Action
  3. Select Create New Table
  4. Map Output headers to create new Coloumn headers
  5. Click Save

Creating A New Table vs Adding to Existing Table

When running a lead sourcing action from the dashboard, you can either select it to Create New Table or Add To Existing Table.

Create a new Table fills the output in a blank new table. Columns will be automatically created based on how our team has setup for that action.

Add to existing Table will append new rows with new data in an existing table. You can map new column headers to the existing column headers manually, so it doesn’t mess up the flow.

Or you can also create a new column for the newly imported data.

Importing from Dashboard Video guide

Importing from inside the Table

  1. Click on the Table button on the top right and select Import
  2. Select the lead sourcing action to run
  3. Set the input fields and run the Action
  4. Select whether to Overwrite Table or Add To New Rows
  5. Map output JSON key values to existing columns
  6. Click Create New Rows

Video Guide

Adding New Rows vs Overwriting Table

When running a lead sourcing action from inside the Table, you can either select it to Overwrite Table or Add New Rows.

Adding New Rows will append. You can map new column headers to the existing column headers manually, so it doesn’t mess up the flow.

Add to existing Table will append new rows with new data in an existing table. You can map new column headers to the existing column headers manually, so it doesn’t mess up the flow.

Or you can also create a new column for the newly imported data.

Lead sourcing column structure

When you run any lead sourcing action from the dashboard, it will automatically create a new coloumn based on we have setup.

First column will always be the raw output from the scraper. For rest of the columns,

You can always create a new column and pass the values of a specific JSON by clicking the “Create New Column” inside the JSON output.

Example of scraping Restaurants using Google Maps Scraper:

  • First column consists JSON outputs for each Restaurant
  • Column 2 (Place Name) are the names of the Restaurant
  • Column 3 (Maps URL) are the URLs to Google Maps address

Mapping Column Headers

You can manually map output Headers with the existing column headers - so you can maintain the structure and the flow.

Common use cases

  • Build a list from a directory, marketplace or launch site — Product Hunt, Hacker News, a subreddit
  • Find companies by signal — recently funded, using a given technology, hiring for a role
  • Find people by signal — job changes, LinkedIn post reactions and comments
  • Pull contacts back out of HubSpot, Salesforce or Pipedrive to enrich and re-sync them
  • Let rows arrive on their own from a webhook or an HTTP request

Best practices

  • Import a small batch first and check the column mapping before pulling thousands of rows
  • Map output fields onto existing column headers instead of creating a second column for the same data
  • Use Add New Rows unless you intend to lose what is already there — Overwrite Table replaces it
  • Dedupe the table right after an import, before you spend a single credit enriching it
  • Keep the raw JSON column and create new columns from the fields you need
  • Run several narrow imports (one city, one category, one keyword) rather than one broad one

Suggest a lead sourcing action

Have ideas for new ways to source leads? Submit your request here 

Upcoming features for lead sourcing

  • Scheduled runs for lead sourcing actions based on frequency, time. Example: Run Hacker News scraper every day at 7:00am.
EnrichmentsWeb Scrapers