Skip to main content

SSL/TLS certificate expiry monitor with Slack alert

Workflow preview

Workflow preview
100%
SSL/TLS certificate expiry monitor with Slack alert preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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...

Best for

  • SecOps automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Marth.

Original n8n.io source

1.1 Workflow description

Title
SSL/TLS certificate expiry monitor with Slack alert
Workflow name
SSL/TLS certificate expiry monitor with Slack alert

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 morning, ensuring certificate checks are automated and consistent.

  2. List Domains to Monitor (Code Node): This node acts as a static database, storing a list of all the domains you need to track.

  3. Check Certificate Expiry (HTTP Request Node): For each domain in your list, this node makes a request to a certificate checking API. The API returns details about the certificate, including its expiry date.

  4. Is Certificate Expiring? (If Node): This is the core logic. It compares the expiry date from the API response with the current date. If the certificate is set to expire within a critical timeframe (e.g., less than 30 days), the workflow proceeds to the next step.

  5. Send Alert (Slack Node): If the If node determines a certificate is expiring, this node sends a high-priority alert to your team's Slack channel. The message includes the domain name and the exact expiry date, providing all the necessary information for a quick response.


How to Set Up

Here's a step-by-step guide to get this workflow running in your n8n instance.

  1. Prepare Your Credentials & API:

    • Certificate Expiry API: You need an API to check certificate expiry. The workflow uses a sample API, so you may need to adjust the URL and parameters. For production use, you might use a service like Certspotter or a similar tool.
    • Slack Credential: Set up a Slack credential in n8n and get the Channel ID of your security alert channel (e.g., #security-alerts).
  2. Import the Workflow JSON:

    • Create a new workflow in n8n and choose "Import from JSON."
    • Paste the JSON code for the "SSL/TLS Certificate Expiry Monitor" workflow.
  3. Configure the Nodes:

    • Scheduled Check (Cron): Set the schedule according to your preference (e.g., every Monday at 8:00 AM).
    • List Domains to Monitor (Code): Edit the domainsToMonitor array in the code and add all the domains you want to check.
    • Check Certificate Expiry (HTTP Request): Update the URL to match the certificate checking API you are using.
    • Is Certificate Expiring? (If): The logic is set to check for expiry within 30 days. You can adjust the 30 in the expression new Date(Date.now() + 30 * 24 * 60 * 60 * 1000) to change the warning period.
    • Send Alert (Slack): Select your Slack credential and enter the correct Channel ID.
  4. Test and Activate:

    • Manual Test: Run the workflow manually to confirm it fetches certificate data and processes it correctly. You can test with a domain that you know is expiring soon to ensure the alert is triggered.
    • Verify Output: Check your Slack channel to confirm that alerts are formatted and sent correctly.
    • Activate: Once you're confident everything works, activate the workflow. n8n will now automatically monitor your domain certificates on the schedule you set.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 2 - List Domains to Monitor

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Check Certificate Expiry

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 4 - Is Certificate Expiring?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 5 - YOUR_SECURITY_ALERT_CHANNEL_ID

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 6 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow SSL/TLS certificate expiry monitor with Slack alert
Complexity intermediate
Nodes 7
Categories SecOps
Author Marth
Published 04 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6957/6957.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does SSL/TLS certificate expiry monitor with Slack alert do?

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...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your SecOps use case.