Web Server Monitor.
Configured with Gmail, Google Sheets, HTTP Request, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Data store
- Web / API
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Server-Monitor | Data store | Google Sheets | See node parameters |
| HTTP Request | Web / API | HTTP Request | See node parameters |
| Server_Status_Alive | Data store | Google Sheets | append |
| Gmail | Messaging | Gmail | See node parameters |
| Server_Status_Down | Data store | Google Sheets | append |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
gmailOAuth2googleSheetsOAuth2Api
Workflow notes
Sticky Note
📘 Node Descriptions for Your Web Server Monitor Workflow
⏰ 1. Schedule Trigger
Triggers the workflow every minute to initiate regular checks on server availability.
📄 2. Web Servers List (Google Sheets)
Fetches a list of server hostnames or IP addresses from a Google Sheet.
Each row is treated as one server. This makes server management easy — no need to edit the workflow to add/remove servers.
🌐 3. Server Alive Check (HTTP)
Sends an HTTP GET request to each server (e.g., http://your-server.com).
If the request fails, the error path is triggered.
📝 4. Web Server Alive Log (Google Sheets)
Logs successful server checks into a separate Sheet with a timestamp.
This log helps track uptime history, verify server health, and generate availability reports.
🚨📧 5. Server Down Notification (Gmail)
Sends an alert email if a server does not respond or returns an error.
Includes the server address and the timestamp of failure.
📝 6. Web Server Down Log (Google Sheets)
Logs the failed server checks into another Sheet with a timestamp.
Useful for uptime reporting, debugging, and audit tracking.
Web Server Monitor.
Web Server Monitor.
Purpose and structure
This folder contains the Web Server Monitor. workflow. Its executable nodes use gmail, googleSheets, httpRequest, scheduleTrigger. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Schedule/1952_Schedule_HTTP_Monitor_Webhook.json MIT; preserve source notices.