Monitor Lindo website incidents with HTTPS HEAD checks and email digests
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 15 nodes and runs on a schedule (every 30 minutes) (plus 1 other trigger). It uses only n8n's built-in nodes. It also calls api.lindo.ai over HTTP.
How it runs
Trigger: On a schedule (every 30 minutes) (plus 1 other trigger).
- Configure monitoring (Edit Fields (Set)): sets 3 fields: fromEmail, reviewerEmail, digestDays
- Validate report settings (Code): runs custom JavaScript code
- Lindo - list the website inventory (HTTP Request): calls api.lindo.ai (GET)
- Validate inventory and public URLs (Code): runs custom JavaScript code
- Check public website availability (HTTP Request): calls an HTTP API (HEAD)
- Keep first check evidence (Code): runs custom JavaScript code
- Wait: waits 30 seconds
- Confirm public website availability (HTTP Request): calls an HTTP API (HEAD)
- Summarize every website check (Code): runs custom JavaScript code
- Detect new incidents and recoveries (Code): runs custom JavaScript code
…plus 3 more steps. See the full node list below.
HTTP calls to: api.lindo.ai
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 (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Send Email
n8n-nodes-base.emailSend - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if
From the author
Quick overview This workflow runs on a schedule to pull your website inventory from Lindo, probe each public URL twice via HTTPS HEAD requests, and email a reviewer only when there are new incidents, recoveries, or a periodic portfolio digest. How it works 1.…