Inputs to change
- Node `sitemap`: use a child sitemap listing page URLs directly.
- Node `sample`: set the bounded number of URLs to check.
- Node `report`: rename the artifact for the release or client.
Read a URL-set sitemap, guard against sitemap indexes, check a bounded set of listed URLs, and render direct HTTP status and redirect evidence without claiming full-site uptime.
Updated 1 August 2026 from the executable catalog.
Node labels and costs come from the registry. Dependency captions come from each node's dependsOn field, including parallel starts and approval gates.
web_get_sitemapconditionutil_takeweb_check_url_statusreport_renderThe following notes are shipped beside the executable definition.
Every operation below is present in this template's JSON and has no private rollout gate in the registry.
Fetch a sitemap.xml (or a site root, trying /sitemap.xml) and list the URLs it contains. Reports whether it is a sitemap INDEX whose entries are child sitemaps.
web_get_sitemapReturn the first (or last) N items of a list. Use to cap an upstream list before an expensive per-item operation.
util_takeFetch a URL and report its HTTP status, whether it redirected, and the final URL. Useful for monitoring site and landing-page health.
web_check_url_statusCompose text, KPI metrics, inline charts, and tables (typically templated from upstream operation outputs) into a branded, self-contained HTML report stored as a workspace file. Supports white-label brand name/colour/logo. Returns the file id and download path; prints cleanly to PDF.
report_renderStart free to build workflows manually. This template's requirement panel shows what must be unlocked before execution.