Inputs to change
- Node `probe`: replace the example URL with a canonical landing, pricing, or campaign URL.
- Node `report`: change the filename and title for the review cycle.
Probe one important URL, follow its final destination, read the resulting page, and save the observed redirect and content evidence for review.
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_check_url_statusweb_fetch_pagereport_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 URL and report its HTTP status, whether it redirected, and the final URL. Useful for monitoring site and landing-page health.
web_check_url_statusDownload a web page and return its title and readable text content (HTML stripped, capped). Use for reading landing pages, articles, or competitor copy.
web_fetch_pageCompose 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.