n8n Workflow: Domain Expiry & WHOIS Change Email Alerts

Never miss a risky domain expiration or a WHOIS change again

This n8n workflow checks your domain list every Monday, monitors expiry risk and WHOIS/RDAP changes via the Apify Domain Expiry & WHOIS Monitor actor, and sends a plaintext email alert through SMTP only when a domain needs attention.

What this workflow does

• Runs on a schedule: executes every Monday at 9:00.
• Reads workflow inputs: a comma-separated domain list, an alert email address, and an expiryWarningDays threshold.
• Calls Apify for monitoring: triggers the Apify actor with change tracking enabled and returns only domains that are expired, expiring soon, unregistered, lookup-failed, or have changed WHOIS/RDAP details.
• Builds a single summary email: compiles one subject and a plaintext body listing all alert-worthy domains (expired/expiring soon/unregistered/lookup-failed/changed).
• Sends alerts only when needed: if there are no results, the workflow stops without sending an email.
• Delivers via SMTP: sends the summary to the configured recipient using an SMTP credential.

Use cases

• SaaS operators monitoring critical domains used for product sign-up, API endpoints, or marketing campaigns.
• Domain portfolio management to detect expiration risk and unexpected WHOIS/RDAP changes early.
• Automation engineers setting up reliable, scheduled n8n alerts for domain oversight across multiple accounts.

Technical details

• Schedule Trigger: runs Mondays at 9:00.
• HTTP Request: calls the Apify API using an HTTP Header Auth credential with Authorization: Bearer <YOUR_APIFY_TOKEN>.
• Email Send: sends a plaintext email via SMTP.
• Workflow logic: uses nodes like set, code, and supporting notes/states to compile and conditionally send alerts.

Setup

• Create an Apify API token and configure the HTTP Header Auth credential.
• Configure an SMTP credential for the sending email account.
• Update domain list, recipient email address, and expiryWarningDays; adjust the schedule time if needed.