MarkMate
Start free
Executable distribution template

Approval-gated webhook alert after a confirmed HTTP response regression

Check one critical URL and, after two completed probes return unhealthy HTTP results, prepare an external webhook alert. The alert never sends automatically: MarkMate pauses until a human approves the exact destination and payload. DNS, TLS, connection, and timeout errors fail the workflow before the alert node and remain visible as failed-run history signals; this template does not convert those transport failures into webhook alerts.

Updated 1 August 2026 from the executable catalog.

Open a free workspace Inspect 6 nodes
definition.nodes

The executable path

Node labels and costs come from the registry. Dependency captions come from each node's dependsOn field, including parallel starts and approval gates.

approval-gated-webhook-alert.json6 nodes / current registry
  1. Check URL statusweb_check_url_status
    Starts immediately
  2. Check conditioncondition
    After first_probe
  3. Wait 15 secondswait
    After first_failed
  4. Check URL statusweb_check_url_status
    After pause
  5. Check conditioncondition
    After confirm_probe
  6. Send webhook (POST)web_post_webhook
    Approval After first_probe + confirm_probe + confirmed_failed
Template metadata

Set it up without surprises

The following notes are shipped beside the executable definition.

Customize

Inputs to change

  1. Nodes `first_probe` and `confirm_probe`: set both URLs to the same critical production endpoint.
  2. Node `pause`: choose a retry delay from 1 to 30 seconds to reduce alerts for brief HTTP response regressions.
  3. Node `alert`: set the public incoming-webhook URL and adapt the payload to the receiving incident system.
  4. Set the recurring schedule only after confirming that failed-run history and the workspace approval inbox are actively monitored. A continuing HTTP regression can prepare a new approval on each scheduled run; this template does not deduplicate incidents, so pause the schedule after opening an incident.
Runtime

Requirements

  • Human approval is mandatory for every webhook send; the workflow pauses before changing the external incident system.
  • A public webhook destination; private and internal network addresses are refused outside development.
  • Growth plan or higher for the suggested recurring schedule.
  • Separate monitoring of failed workflow runs is required for DNS, TLS, connection, and timeout failures because no webhook approval is prepared in those cases.
Generally available operations

Operation manifest

Every operation below is present in this template's JSON and has no private rollout gate in the registry.

01
Open web

Check URL status

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_status
Cost
1 credits
Plan
Free
Approval
Not required
02
Open web

Send webhook (POST)

POST a JSON payload to an external webhook URL (Zapier, Slack/Discord incoming webhooks, your own endpoint). This CHANGES an external system, so it always pauses for human approval before sending. Reports the delivery status without failing on non-2xx responses.

web_post_webhook
Cost
1 credits
Plan
Starter
Approval
Required
Approval-gated webhook alert after a confirmed HTTP response regression

The wiring is visible. The final decision stays yours.

Start free to build workflows manually. This template's requirement panel shows what must be unlocked before execution.

Start free All templates