Step 2: Connect Google Sheets for Status and Data Operations

Configure the Google Sheets nodes that update status and write research data.

1. In Mark Status Running, set Operation to update, map Client to {{ $json.Client }}, and set Status to Running.
2. In Flag Missing Data, set Operation to update, map Client to {{ $json.Client }}, and set Status to Missing data.
3. In Append Research Rows, set Operation to append and map: City to {{ $('Assign Search Inputs').item.json.city }}, State to {{ $('Assign Search Inputs').item.json.state }}, Client to {{ $json.client }}, Company to {{ $json.company }}, and website to {{ $json.Website }}.
4. In Lookup Existing Emails, set the filter to lookup Company with {{ $json.company }}.
5. In Update Email Records, set Operation to update and map emails to {{ $json.emails ? $json.emails + ", " + $('Extract Email Addresses').item.json.email : $('Extract Email Addresses').item.json.email }}, and Company to {{ $('Extract Email Addresses').item.json.company }}.
6. In Mark Status Finished, set Operation to update, map Client to {{ $('Generate Site Variants').item.json.client }}, and set Status to Finished.

Credential Required: Connect your googleSheetsOAuth2Api credentials to Mark Status Running and Flag Missing Data.

⚠️ Common Pitfall: The other Google Sheets nodes (Append Research Rows, Lookup Existing Emails, Update Email Records, Mark Status Finished) also require Google Sheets credentials, but none are configured. Add the same googleSheetsOAuth2Api credentials to each of them.

Step 3: Set Up Validation and Search Input Preparation

Validate incoming rows and build search inputs for the Serper query.

1. In Input Validation, ensure the three conditions check for non-empty values: {{ $json.Client }}, {{ $json.City }}, and {{ $json.State }}.
2. Confirm Input Validation routes valid rows to Mark Status Running and invalid rows to Flag Missing Data.
3. In Assign Search Inputs, enable Keep Only Set and set fields: state to {{ $('Sheets Row Trigger').item.json.State }}, city to {{ $('Sheets Row Trigger').item.json.City }}, client to {{ $('Sheets Row Trigger').item.json.Client }}, business_type to {{ $node["Sheets Row Trigger"].json["Business Type"] }}, country to Argentina, country_code to AR, language to es-419, and result_count to 10.

Step 4: Configure Search and Link Parsing

Query Serper and filter the organic results into company candidates.

1. In Serper Search Request, set URL to https://google.serper.dev/search and Request Method to POST.
2. Enable JSON Parameters and set Body Parameters JSON to { "q": "{{ $json.business_type }} in {{ $json.city }}, {{ $json.state }}, {{ $json.country }}", "num": {{ $json.result_count }}, "gl": "{{ $json.country_code }}", "hl": "{{ $json.language }}" }.
3. Credential Required: Connect your httpHeaderAuth credentials for the Serper API.
4. Keep Parse Company Links as-is to filter out blacklisted results and map company, Website, client, state, and city values.

Step 5: Generate URL Variants and Batch Processing

Create multiple contact/support URL variants and iterate through them for scraping.

1. Keep Append Research Rows connected after Parse Company Links to log candidate companies before scraping.
2. In Generate Site Variants, keep the JavaScript that builds multiple URL paths for each website.
3. In Batch Iterator, leave the default batching options unless you need to control throughput.
4. Confirm the flow: Append Research Rows → Generate Site Variants → Batch Iterator → Validate Page URLs.

⚠️ Common Pitfall: If your input sheet uses different column names (e.g., “website” vs “Website”), adjust the mapping in Append Research Rows and Generate Site Variants accordingly.

Step 6: Configure Scraping, Parsing, and Email Updates

Validate pages, scrape HTML, extract emails, and update existing records.

1. In Validate Page URLs, set URL to {{ $('Generate Site Variants').item.json.Website }}.
2. In Scrape Result Check, keep the condition that checks {{ $json.error.message }} is empty before continuing to scrape.
3. In ScrapingBee Request, set URL to https://app.scrapingbee.com/api/v1/?api_key=[CONFIGURE_YOUR_API_KEY]={{ $('Generate Site Variants').item.json.Website }}&render_js=true and replace [CONFIGURE_YOUR_API_KEY] with your ScrapingBee key.
4. In Scrape Success Check, keep the condition that checks {{ $json.error.message }} is empty before extracting emails.
5. In Extract Email Addresses, keep the JavaScript that extracts and deduplicates emails from the HTML data field.
6. In Email Presence Check, use the not-empty condition on {{ $('Extract Email Addresses').item.json.email }} to decide whether to update.
7. Confirm the update flow: Email Presence Check → Lookup Existing Emails → Update Email Records → Delay Pause → Batch Iterator.

⚠️ Common Pitfall: The ScrapingBee URL includes a placeholder API key. If you leave [CONFIGURE_YOUR_API_KEY] unchanged, scraping will fail and the workflow will loop back via Batch Iterator.

Step 7: Test and Activate Your Workflow

Verify the full enrichment pipeline and then turn it on for production updates.

1. Manually run the workflow with a test row update in the input sheet and ensure Sheets Row Trigger fires.
2. Check that Mark Status Running updates the input sheet status to Running or Flag Missing Data updates it to Missing data when fields are empty.
3. Verify Append Research Rows appends results to the data sheet and Update Email Records writes email values.
4. Confirm Mark Status Finished sets the final status to Finished after batch processing.
5. Activate the workflow by toggling the Active switch in n8n.