Upsert Lection Webhook Data to Google Sheets (Deduping)

Upsert Lection webhook data into Google Sheets—without duplicates

This n8n workflow receives scheduled scrape results from Lection and writes the dataset into Google Sheets using an upsert (append or update) strategy based on a unique column, so you keep your sheet clean and deduplicated.

What this workflow does

• Receives a Lection webhook (POST) for a scheduled scrape delivery.
• Validates security by comparing the incoming x-lection-secret header to a configured shared secret; if it doesn’t match, the workflow returns 401.
• Ensures the event is correct: it checks for scheduled_scrape.completed and confirms the dataset contains at least one row—otherwise it returns a JSON response indicating nothing was written.
• Splits incoming records from body.dataset.records into individual items.
• Upserts into Google Sheets for each record using “append or update” based on your chosen matching (unique) column.
• Responds with a summary to Lection, including how many rows were written.

Use cases

• Maintain a continuously updated Google Sheet from Lection scheduled scraping jobs (e.g., product listings, listings datasets, or crawl results).
• Run periodic scrapes and safely re-import results without creating duplicate rows.
• Use a single source of truth in Google Sheets for downstream processes and reporting.

Technical details

• Webhook: n8n receives Lection events and performs x-lection-secret verification.
• if: validates event type and dataset row presence.
• Split out + aggregate: processes each body.dataset.records item and summarizes write results.
• Google Sheets: writes to a specified Spreadsheet ID and sheet name, configured with a matching (unique) column for deduping/upsert behavior.

Setup tip: Create a Google Sheet with a header row whose column names exactly match Lection’s dataset.records field names, then configure the target spreadsheet, sheet name, and the deduping matching column in the Google Sheets node.