SSL & Security Header Monitoring n8n Workflow (Apify Alerts)

Stay ahead of SSL expiry and security header issues—without manual checks

This n8n workflow continuously monitors SSL certificate expiry and security headers for a list of websites using Apify, stores the last known results in an n8n Data Table, and sends change-based alerts (plus an optional weekly summary) to Slack, Gmail, and an HTTP webhook.

What this workflow does

• Runs on your schedule: it can execute daily, on demand, and also supports a Monday run to generate a weekly summary.
• Loads configuration: the site list and notification settings are read from the workflow’s CONFIG block.
• Tracks state per site: it creates (if needed) and reads an ssl_monitor_state n8n Data Table to remember each site’s last known grade, certificate status, and open issues.
• Audits via Apify: on daily/manual runs, it calls the Apify “Security Headers & SSL Audit” Actor to check HTTPS/certificate status, redirects, and security headers.
• Detects changes and reminders: it compares fresh results to stored state to identify new, changed, reminder-due, and resolved issues. Site unreachable alerts are only triggered after consecutive failed checks.
• Sends consolidated alerts: when changes are detected, it builds a single alert message and routes it by severity to enabled channels.
• Sends without blocking: alert delivery is attempted for each enabled destination, with retry behavior so other channels aren’t blocked.
• Weekly summary without re-auditing: weekly runs generate a summary from the stored state without calling Apify.

Use cases

• Monitor customer-facing domains for SSL expiry risk and security header regressions.
• Automate security compliance checks for SaaS operations teams.
• Get immediate visibility in Slack and Gmail when certificate status or security header grades change.
• Send alerts to internal systems via an optional HTTP webhook.

Technical details

• Apify integration: “Security Headers & SSL Audit” Actor
• Storage: n8n Data Table ( ssl_monitor_state )
• Notification channels: Slack, Gmail, and optional HTTP webhook
• Workflow nodes: if, set, code, no op (plus Slack/Gmail nodes)