Mallabe Websites
Actions3
- Website Actions
Overview
The "Mallabe Websites" node is a utility tool designed to interact with websites by checking their status, retrieving their icons, or generating thumbnails. Specifically, the Check Website Status operation allows users to verify if a website is alive and measure the response time. This can be useful for monitoring website uptime, validating URLs before further processing, or integrating website health checks into automated workflows.
For example, you might use this node to:
- Automatically check if a list of client websites are online before sending notifications.
- Monitor your own website's availability and response times as part of a larger monitoring system.
- Trigger alerts or downstream processes based on website responsiveness.
Properties
| Name | Meaning |
|---|---|
| Website URL | The full URL of the website to check (e.g., https://www.google.com). |
| HTTP Request Method | HTTP method to use for the request. Options: GET, POST, PUT, DELETE. Default is GET. |
| Timeout (Ms) | Timeout in milliseconds for the HTTP request. Default is 10000 (10 seconds), max is 15000. |
| Webhook URL (Optional) | Optional webhook URL where the response data will be sent instead of returning it directly. |
Output
The output JSON structure contains the response from the website status check API. It typically includes information such as whether the website is reachable ("alive") and the time taken to respond.
If the optional webhook URL is provided, the node sends the response data to that URL instead of outputting it directly.
No binary data is produced by this operation.
Example output JSON (simplified):
{
"data": {
"alive": true,
"responseTime": 123,
"statusCode": 200,
"url": "https://www.example.com"
}
}
Dependencies
- Requires an API key credential for the Mallabe Websites service to authenticate requests.
- The node makes HTTP POST requests to the Mallabe Websites API endpoints.
- No additional environment variables are needed beyond the API credential configuration in n8n.
Troubleshooting
- Timeouts: If the website takes longer than the specified timeout (default 10 seconds), the request may fail. Increase the timeout up to 15 seconds if necessary.
- Invalid URLs: Ensure the website URL is correctly formatted including the protocol (http:// or https://).
- API Errors: If the API key is missing or invalid, the node will throw authentication errors. Verify the API credential setup.
- Webhook URL Issues: If using the webhook URL option, ensure the URL is accessible and can accept POST requests; otherwise, the webhook delivery will fail silently or cause errors.
- HTTP Method Usage: Using methods other than GET may not be supported or expected by some websites, leading to unexpected results.