Templates: find emails for a Google Sheets list of websites

Ready-to-import templates that send a column of company websites to the Website Contact Details Scraper in one call and write the email and status back to each row, matched on domain (the response order differs from the input order). Cost: $0.002 per site where an email is found, nothing otherwise; every template sets a hard spend cap.

You need your own Apify API token (Console, Settings, Integrations). Never paste it into a shared sheet; each template says where to put it.

• n8n workflow (n8n-sheets-domains-to-emails.json)
  Import via Workflows, Import from file. Google Sheets read, one Apify call for the whole list, merge on domain, Sheets write-back. Step-by-step: guide.
• n8n workflow: Google Maps leads (n8n-maps-leads-to-sheet.json)
  Needs the n8n-nodes-datagleaner community node. Google Maps search, contact details per website, Sheets write-back. Imported and run in n8n 2.45 with the community node on 11-01 (3 places, contact step and field mapping checked; the Google Sheets node itself needs your own Google credential). Step-by-step: guide.
• n8n workflow: Google Maps leads, one contact run (n8n-maps-leads-to-sheet-batch.json)
  Same as above, but a Code node gathers all websites so Get Contact Details runs once for the whole search instead of once per place, then a second Code node matches results back to places by website host. Same Apify charge, about half the wall time on a 3-place test. Skips Facebook, Instagram and other social URLs listed as a place's website. Step-by-step: guide.
• Make scenario blueprint (make-sheets-domains-to-emails.blueprint.json)
  Scenarios, Create new, three dots, Import Blueprint. Search Rows, aggregate, HTTP, iterate, find row by domain, update row. Step-by-step: guide.
• Google Sheets Apps Script (sheets-apps-script.gs)
  Paste into Extensions, Apps Script. Adds a Keencrest menu; websites in column A, email/status/reason written to B, C, D. Step-by-step: guide.

What was tested

The Apps Script was run through a harness against the live Actor and wrote the right email and status for each row. The HTTP request in all three was run against the live Actor. The n8n file was structure-checked against n8n's workflow import; the Make blueprint follows Make's export format but was not imported inside Make, so module field names may need a re-pick of the spreadsheet after import.

Alerts & monitoring: new news about your brand

The same free pattern for a different job: the GDELT News Monitor in watch mode returns only articles it has not returned before, and a template posts them to a chat channel or logs them in a sheet. Cost: $0.002 per article returned, nothing in a quiet hour. Each file has your own Apify token and webhook as placeholders. Source data: The GDELT Project.

• n8n: alert to Slack (n8n-gdelt-brand-alert-slack.json)
  Hourly schedule, Apify watch mode, one Slack message. Step-by-step: guide.
• n8n: alert to Discord (n8n-gdelt-brand-alert-discord.json)
  Same workflow, Discord webhook, message cut at 1,900 characters. Step-by-step: guide.
• n8n: alert to Microsoft Teams (n8n-gdelt-brand-alert-teams.json)
  Same workflow, Teams Workflows webhook with an Adaptive Card. Step-by-step: guide.
• Make blueprint: alert to Slack (make-gdelt-brand-alert-slack.blueprint.json)
  HTTP, iterator, text aggregator, Slack webhook. Step-by-step: guide.
• Google Sheets Apps Script: news mentions log (sheets-gdelt-mentions.gs)
  Hourly trigger appends new articles to a Mentions tab. Step-by-step: guide.

These were structure-checked and their formatting code run on sample data; none has been imported into the target tool or posted to a live channel yet, and each guide says so.

For vendor incidents rather than news: SaaS outage alerts, with an "is it down" page for 70 vendors showing each official status page and its RSS feed. Free, no Apify: n8n RSS to Slack and RSS to Discord (guide).