Monitor Domain expiry and Alert Slack the Moment It Breaks

On a schedule, this checks domain expiry and — only when something is actually wrong — fires a Slack alert with the details, so you hear about problems before your customers do.

difficulty Beginnersetup 20 minresult You get an immediate Slack alert whenever domain expiry fails, and silence when everything's healthy.
  1. 1

    Step 1 — Schedule the check

    Add a Schedule Trigger. Every 5 minutes for uptime; once a day is plenty for expiry checks.

  2. 2

    Step 2 — Run the check

    Add an HTTP Request node that queries WHOIS/RDAP for the domain expiry date.

  3. 3

    Step 3 — Decide if it's a problem

    Add an If node: continue only when the remaining days drop below your threshold (e.g. 21). This keeps things quiet when all is well.

  4. 4

    Step 4 — Alert Slack

    Add a Slack node. Set Resource to Message and Operation to Send. Choose the channel (e.g. #alerts) and drop what failed, the value observed, and a timestamp into the message text using expressions like {{ $json.summary }}. Connect your Slack OAuth or bot-token credential.

Frequently asked questions

How do I avoid alert storms?

Add a "seen" flag or a cooldown so a persistent outage alerts once, not every 5 minutes. n8n's static data or a small store handles this cleanly.

Can I monitor several targets?

Yes — feed a list of URLs/domains into Step 2 and loop, so one workflow covers your whole estate and still alerts Slack per failure.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.