Monitor weekly domain health with Apify, Google Sheets, and Slack
Go to Workflow
PewterDesk
Description
Quick overview
This workflow runs every Monday to check a list of domains with Apify for DNS, SSL, RDAP registration, and website health, logs each snapshot to Google Sheets, compares it to the prior check, and sends urgent alerts plus a weekly change summary to Slack.
How it works
Runs every Monday at 7am and loads the domain list plus warning/critical day thresholds for SSL and domain renewal.
Uses the Apify “Bulk Domain Intelligence” actor to fetch DNS, TLS/SSL, RDAP registration, email-auth (SPF/DMARC), and homepage status for each domain.
Normalizes the results into a comparable “health snapshot” per domain and flags issues such as non-resolving DNS, SSL invalid/expiring, domain expiry/registry holds, missing or unsafe SPF/DMARC, and website errors.
Reads the existing “Domain health” history from Google Sheets and compares each domain’s latest snapshot against its most recent logged row to detect new problems, resolved problems, and key record changes (for example nameservers, registrar, MX, SPF, DMARC strength, SSL issuer, and redirect target).
Appends the current snapshot for every domain to Google Sheets to maintain a weekly audit trail.
Posts one Slack message per domain for urgent cases (critical new problems or critical changes like nameserver/registrar changes).
Posts a single weekly Slack report summarizing domains with changes and listing domains that still have unresolved problems.
Setup
Add an Apify credential (API token) and ensure the actor ID is set to pewterdesk~bulk-domain-intelligence.
Connect Google Sheets OAuth credentials, create a sheet tab named “Domain health”, and set the Google Sheets document URL/ID in both Google Sheets nodes.
Connect Slack credentials and set the destination channels for urgent alerts and the weekly report (for example #domain-alerts and #domain-health).
Update the domain list and the SSL/domain renewal warning and critical thresholds in the “Client domains and alert rules” step before enabling the schedule.
This workflow was created by PewterDesk and shared publicly on the n8n community template library. n8nFind indexes it for discovery — the workflow remains the property of its original creator.