Google Industry Contact Finder is a reusable BrowserAct template for collecting structured records from public Google pages. Configure the run inputs, start the Bot, and receive consistent output for research, monitoring, enrichment, or downstream automation without writing selectors or scraper code.
What Does BrowserAct Google Industry Contact Finder Do?
The Bot starts from your configured inputs, opens the relevant public Google page, loads the requested records, extracts the visible fields, and returns structured results. The default example uses browser automation for Industry, but the input can be changed before each run.
Key Features of Google Industry Contact Finder
- Configurable public-page inputs without rebuilding the Bot.
- Structured records returned in a consistent
resultsarray. - Public, non-login extraction path.
- Reusable runs for new keywords, URLs, locations, or limits.
- Output ready for review, export, API use, or automation.
What Data Can I Extract from Google?
| Field | Description |
|---|---|
name |
Publicly visible name value for the record, when available. |
job_title |
Publicly visible job title value for the record, when available. |
company |
Publicly visible company value for the record, when available. |
introduction_or_snippet |
Publicly visible introduction or snippet value for the record, when available. |
profile_url |
Direct public profile URL. |
target_site |
Publicly visible target site value for the record, when available. |
result_position |
Publicly visible result position value for the record, when available. |
source_search_url |
Publicly visible source search url value for the record, when available. |
How to Use Google Industry Contact Finder
Quick Start Guide
- Click Run task.
- Keep the default inputs for a first test or enter your own public-page values.
- Click
Run. - Review the structured records after the run completes.
- Download the result or connect it to another workflow.
Input Parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
Industry |
Yes | browser automation |
Controls the industry used for this run. |
Job Title |
Yes | founder |
Controls the job title used for this run. |
Target Site |
Yes | facebook.com |
Controls the target site used for this run. |
Count |
Yes | 5 |
Controls the count used for this run. |
Example Output
{
"results": [
{
"name": "Example value",
"job_title": "Example value",
"company": "Example value",
"introduction_or_snippet": "Example value",
"profile_url": "https://example.com/public-record",
"target_site": "Example value",
"result_position": "Example value",
"source_search_url": "https://example.com/public-record"
}
]
}
How Does it Work?
- Construct a site-restricted Google query from industry, job title, and target site.
- Open the public results page, clear supported verification when required, and load matching result pages.
- Read profile or company names, visible role and company context, snippets, profile URLs, and result positions.
- Return normalized public contact-discovery records up to Count.
How to Build a New Scraper Bot with Agent Built
Step 1: Describe the data you need
Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Describe the public website, records, inputs, fields, and result limit.

Step 2: Let BrowserAct build and test the Bot
BrowserAct explores the live website, determines the navigation and extraction path, and validates the result. Reply in the same build conversation if the Agent requests a missing public URL, field, or expected output.

Step 3: Run the Bot and review the result
Run the completed Bot with default inputs. Check record count, source URLs, and required fields before reusing it with new inputs.


Why Use Google Industry Contact Finder?
- Replace repetitive copying from public Google pages.
- Keep the same output structure across repeated runs.
- Send public records into research, reporting, enrichment, or monitoring workflows.
Who Can Use Google Industry Contact Finder?
- Researchers and analysts collecting public web data.
- Marketing, sales, and operations teams preparing structured datasets.
- Automation builders connecting BrowserAct output to other tools.
- Developers who need reusable browser-collected JSON records.
Automation and Export

BrowserAct returns structured records first. You can then use that output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual spreadsheet export.
Need Help?
Contact us at
Discord: Discord Community
E-mail: service@browseract.com

