Overview

This template eliminates manual URL monitoring by sending HTTP GET requests to each target URL, collecting status codes, and flagging those not responding with a 200 OK. It compiles results into a single array for streamlined alerting or integration, saving time and reducing oversight risk.

The Impact

  • Automate URL Monitoring. Replace manual checks with scheduled HTTP GET requests for reliable uptime tracking.
  • Flag Unhealthy Endpoints. Instantly identify URLs returning non-200 status codes to prioritize fixes.
  • Aggregate Results. Consolidate health data into a structured list for easy downstream processing or alerts.
  • Reduce Overhead. Cut manual inspection costs and human error by automating status collection.

Who This Is For

  • Site Reliability Engineers conducting daily availability audits on critical service endpoints.
  • Developers running health regressions post-deployment or rollback to verify interface availability.
  • Product and Operations Teams monitoring third-party APIs for SLA compliance and dependency stability.
  • QA Engineers performing automated endpoint responsiveness checks during testing cycles.

How It Works

1
  1. Input URL List
  2. Start node receives an array of full URLs to check.
2
  1. Iterate and Ping
  2. Loop Each URL sends HTTP GET requests with a 60-second timeout for each URL.
3
  1. Build Status Record
  2. For each response, construct a result object with URL, status code, and a healthy flag if status code equals 200.
4
  1. Aggregate Results
  2. Collect all individual URL health results into a comprehensive Results array.
5
  1. Output Summary
  2. End node outputs a Success boolean and full Results list for alerts or storage.

What You'll Need

Before using this template, make sure you have:

  • A list of fully qualified URLs (including http:// or https://) to monitor.
  • Network access allowing outbound HTTP GET requests to target URLs.
  • No special credentials or authentication are required since it performs simple HTTP GET requests.

How to Use

  1. Step 1. Prepare URL List
  2. Create an array of complete URLs you want to monitor, including protocol prefixes.

  3. Step 2. Input URLs
  4. Pass this URL array into the "Urls" parameter of the Start node.

  5. Step 3. Execute Workflow
  6. Run the workflow to initiate sequential HTTP GET requests to each URL.

  7. Step 4. Collect Results
  8. Let the workflow compile each URL's health status, including HTTP status code and healthy flag.

  9. Step 5. Verify Outputs
  10. Check the Success boolean and review the aggregated Results array to confirm all URLs were checked and their status recorded.

FAQs

What determines if a URL is healthy?
A URL is considered healthy only if the HTTP GET request returns a status code of 200.
Can I check URLs that require authentication?
This workflow performs simple GET requests without authentication; URLs requiring credentials are not supported out of the box.
What happens if a URL does not respond within 60 seconds?
The HTTP request times out after 60 seconds and the result for that URL will reflect a failure or no status code.
How are the results outputted?
All URL health results are aggregated into a Results array, alongside a Success boolean indicating if the process completed without error.
Can this be integrated with alerting systems?
Yes, the aggregated Results array can be used to trigger alerts or feed into downstream monitoring tools.
Was This Page Helpful?

More Workflows for Inspiration

🔧
Scheduled Deletion of Database Records by Product Code
Automate deletion of product-specific database records to reduce manual cleanup and maintain data integrity.
Learn more >
⚙️
Deep Web Scraper and Logger
Automate discovery and scraping of keyword-linked subpages, logging results to Google Sheets and Drive.
Learn more >
🔍
Briefing Automator
Automatically scrape, summarize, and archive web articles while notifying your team instantly.
Learn more >