Block 1 - Get row(s) in sheet
- Type / Role
- n8n-nodes-base.googleSheets - googleSheets
- Config choices
- Version 4.7
This workflow is provided as-is. Please review and test before using in production.
️ Notice: Community nodes like @custom js/n8n nodes pdf toolkit can only be installed on self hosted instances of n8n. This n8n workfl...
n8n-nodes-base.googlesheets, @custom-js/n8n-nodes-pdf-toolkit.sslchecker, n8n-nodes-base.slack, n8n-nodes-base.scheduletrigger, n8n-nodes-base.if
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by CustomJS.
Original n8n.io source> ⚠️ Notice:
> Community nodes like @custom-js/n8n-nodes-pdf-toolkit can only be installed on self-hosted instances of n8n.
This n8n workflow illustrates how to monitor and track SSL certificate expiration dates for any domain using the SSL Checker node from customJS. It automatically updates a Google Sheet with the number of days left until expiry and sends a Slack notification when certificates are about to expire.
Schedule Trigger
Google Sheets (Read Rows)
SSL Checker (CustomJS node)
expires and daysLeft.Google Sheets (Update Rows)
Check Days Left Threshold (formerly "If" node)
< 8 days).Slack Node
Example Slack alert message:
⏰ Reminder: SSL certificate of www.example.com
will expire in 7 days.
{
"output": {
"domain": "example.com",
"valid": true,
"expires": "2025-12-31T23:59:59.000Z",
"issuer": "Let's Encrypt",
"daysLeft": 5
}
}
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.
| Workflow | Monitor SSL certificate expiry dates with Google Sheets & Slack alerts |
|---|---|
| Complexity | intermediate |
| Nodes | 6 |
| Categories | SecOps |
| Author | CustomJS |
| Published | 23 Jun 2025 |
Use the JSON export at /data/workflows/5172/5172.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
️ Notice: Community nodes like @custom js/n8n nodes pdf toolkit can only be installed on self hosted instances of n8n. This n8n workfl...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.