Thie workflow showcases how you can build a simple website monitoring service using Scheduled Triggers and the HTTP Requests node.
Configured with Gmail, Google Sheets, HTTP Request, Schedule Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- Data store
- Messaging
- Web / API
- Routing
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 |
| Calculate Status | Transform | Edit Fields | See node parameters |
| Get Sites | Data store | Google Sheets | See node parameters |
| Send Chat Alert | Messaging | Slack | See node parameters |
| Send Email Alert | Messaging | Gmail | See node parameters |
| Log Uptime Event | Data store | Google Sheets | append |
| Update Site Status | Data store | Google Sheets | appendOrUpdate |
| Perform Site Test | Web / API | HTTP Request | See node parameters |
| For Each Site... | Routing | Loop Over Items | See node parameters |
| Status Router | Routing | Switch | See node parameters |
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
gmailOAuth2googleSheetsOAuth2ApislackApi
Workflow notes
1. Setting a Schedule
1. Setting a Schedule
Read more about Scheduling Workflows
Since we expect downtime to be a rare occurance, our monitor should only check infrequently during the day. We'll use a schedule trigger for this purpose.
Once the schdule activates, we'll pull a list of sites to check from our google sheet.
2. Perform Site Checks
2. Perform Site Checks
Read more about using HTTP requests
n8n makes it easy to communicate with external websites by offering a powerful HTTP request node which can handle GET and POST requests as well as pagination.
Here, we're only interested in the status code of our requests.
3. Sending Alerts and Logging Results
3. Sending Alerts and Logging Results
Read more about using Switch for powerful control flow
The switch node is powerful control flow tool that makes your workflows smart. Here, we're able to use Switch to trigger alert notifications whenever we have DOWN status or whenever we get a status change.
We store the event in our Sites Google Sheet and update the site's status which will be used to calculate our state on the next scheduled run.
Try It Out!
🚨Google Sheet Required!
🚨Google Sheet Required!
You'll need the following columns:
- Property - the website address to monitor
- Status - either one of "UP" or "DOWN"
Thie workflow showcases how you can build a simple website monitoring service using Scheduled Triggers and the HTTP Requests node.
Thie workflow showcases how you can build a simple website monitoring service using Scheduled Triggers and the HTTP Requests node.
Purpose and structure
This folder contains the Thie workflow showcases how you can build a simple website monitoring service using Scheduled Triggers and the HTTP Requests node. workflow. Its executable nodes use gmail, googleSheets, httpRequest, scheduleTrigger, set, slack, splitInBatches, switch. 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/0529_Schedule_Slack_Update_Webhook.json MIT; preserve source notices.