n8n Workflow: Monitor Lindo Incidents & Email HTTP Digest

Keep Lindo site health in sync—automatically email incident updates and scheduled portfolio digests

This n8n workflow monitors your Lindo inventory by probing each public website via HTTPS, detecting new incidents and recoveries, and emailing a reviewer only when there’s something worth reporting—or sending a periodic HTTP digest.

What this workflow does

• Runs on a schedule (and can be started manually for testing) to load your email and digest settings.
• Validates configuration by checking the fromEmail, reviewerEmail, and digestDays values.
• Pulls your Lindo workspace inventory using the Lindo API, then normalizes each entry into a valid public HTTPS URL.
• Probes each site twice with unauthenticated HTTPS HEAD requests:
  • First probe → wait 30 seconds → second confirmation probe
• Classifies results:
  • Healthy
  • Incident (two failures)
  • Transient (only the confirmation fails)
• Builds a report including both samples (the two HEAD checks) and compares it to the last stored monitoring baseline using n8n static data to detect:
  • new incidents
  • recoveries
  • whether a digest is due
• Sends email via SMTP only when needed, then saves the updated portfolio state for the next run.

Use cases

• Maintain proactive monitoring for SaaS operators managing a portfolio of public websites.
• Alert a reviewer immediately when Lindo-documented sites go down (and when they recover).
• Get an automated weekly/monthly “portfolio digest” without flooding your inbox.

Technical details

• Lindo API integration using an HTTP Header Auth setup:
  • Header name: Authorization
  • Value: Bearer YOUR_LINDO_API_KEY
  • Applied only to the Lindo inventory node; website probes remain unauthenticated.
• Nodes used: if, set, code, wait, email send, and sticky note.
• Scheduling and persistence: n8n schedule + n8n static data for incident/recovery detection.