Web state control
Automatically checks the status of websites, detects common errors, and sends notifications to maintain the availability and operation of the service.
📄 Web State Control Workflow
🧩 Overview
The Web State Control workflow automatically monitors the health of a list of websites, determines the nature of any HTTP response, and notifies the relevant stakeholders via Gmail. By reading URLs from a Google Sheets file, performing HTTP requests, and routing the results through a switch that classifies responses into 3xx, 4xx, or 5xx, the workflow constructs customized email subjects and bodies before sending notifications. This end‑to‑end process saves manual effort and provides real‑time alerts for common web‑service issues.
⚙️ Main Features
- Batch input from Google Sheets – Retrieves a list of site names and URLs in parallel.
- Dynamic HTTP requests – Executes GET requests for each URL, capturing status codes.
- Conditional routing – Directs data to separate branches based on status‑code ranges (3xx, 4xx, 5xx).
- Template‑based messaging – Generates email subject and body with site‑specific variables.
- Automated email dispatch – Sends notifications through Gmail using the appropriate template for each error type.
🔄 Workflow Steps
| Component Name | Role in the Workflow | Key Inputs | Key Outputs |
|---|---|---|---|
| Google Sheets Cell | Reads the spreadsheet containing site names and URLs | Spreadsheet file, range, operation | Table of site data |
| API Request | Performs an HTTP GET request for each URL | URL, method, headers, timeout | Raw HTTP response (status code) |
| Create Data | Builds a record with the site name and status code | Status code, site name | Structured data record |
| Switch | Routes the record to a branch based on the status code | Status code (key) | Record forwarded to the matching branch |
| Prompt – Subject (3xx) | Builds the email subject for 3xx responses | Site name | Subject text |
| Prompt – Body (3xx) | Builds the email body for 3xx responses | Site name, status code | Body text |
| Gmail Message – 3xx | Sends the email for 3xx responses | Recipient, subject, body | Confirmation of sent message |
| Prompt – Subject (4xx) | Builds the email subject for 4xx responses | Site name | Subject text |
| Prompt – Body (4xx) | Builds the email body for 4xx responses | Site name, status code | Body text |
| Gmail Message – 4xx | Sends the email for 4xx responses | Recipient, subject, body | Confirmation of sent message |
| Prompt – Subject (5xx) | Builds the email subject for 5xx responses | Site name | Subject text |
| Prompt – Body (5xx) | Builds the email body for 5xx responses | Site name, status code | Body text |
| Gmail Message – 5xx | Sends the email for 5xx responses | Recipient, subject, body | Confirmation of sent message |
The switch component contains five cases, but only the third (3xx), fourth (4xx), and fifth (5xx) branches are actively used. The other cases are reserved for future extensions.
🧠 Notes
- The workflow is configured to operate in batch mode with up to five parallel executions, ensuring efficient handling of many sites.
- The Google Sheets cell component must have the correct sheet and column headers; otherwise, the data mapping will fail.
- The HTTP request component uses a timeout of five seconds; if a site does not respond within this period, the status code will be recorded as an error, triggering the 5xx branch.
- Each prompt template automatically detects variables from the input record, eliminating the need for manual field mapping.
- Gmail message components rely on the same Google Mail credentials for all notifications; credentials must be kept secure and refreshed as required.
- The workflow assumes that the recipient email address is fixed; to send notifications to different recipients, the prompt templates must be updated accordingly.
- No component ID or internal reference is included in the documentation to preserve clarity and focus on functionality.