SSL/TLS certificate expiry monitor with Slack alert
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 5 nodes and runs on a schedule (every day). Along the way it connects Slack.
How it runs
Trigger: On a schedule (every day).
- List Domains to Monitor (Code): runs custom JavaScript code
- Check Certificate Expiry (HTTP Request): calls an HTTP API
- Is Certificate Expiring? (If): checks a condition and branches into true / false
- YOUR_SECURITY_ALERT_CHANNEL_ID (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (5)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack
From the author
How It Works: The 5-Node Certificate Management Flow 🗓️ This workflow efficiently monitors your domains for certificate expiry. 1. Scheduled Check (Cron Node): This is the workflow's trigger. It's configured to run on a regular schedule, such as every Monday…