BUILD

Crawld and Webhooks

Get told when a scan finishes or a fix is ready.

Status: Not built yet . this connector is not built. The page describes how delivery works on Webhooks given the constraints of the platform, and what verification would honestly be available. Today you can run the free scorecard against a Webhooks site without granting any access at all.

How fixes would arrive

An HTTP POST to an endpoint you control, when something happens worth reacting to.

Webhooks carry notifications, not changes. They are how you hang your own automation off the loop.

Delivery mode Mode A · Repo write
Verification Build-verified

The strongest rung. Because we hold the repository, the change can be built before you ever see it, and the pull request carries the result of that build. Nothing merges without your click.

What the rubric can see here

  • Scan completed, with the score and coverage
  • A fix entered the queue and is waiting on your approval
  • A delivery was made, or failed

Limits worth knowing before you plan around this

  • Delivery is at-least-once, so your handler has to tolerate a repeat
  • A webhook never carries the findings themselves, only the fact that they exist

Where this sits on the ladder

Mode What we get How changes arrive Verification Status
A · Repo write A connected repository we can push a branch to Opens a pull request. You review the diff and merge it. Build-verified Not built yet
B · Read-only repo Read access, plus somewhere to push Pushes to a fork or a branch you own. Build-verified Not built yet
C · Cloud mirror A one-time snapshot or export Works on a clone in our cloud, returns a patch or a PR. Build-verified (mirror) Not built yet
D · CMS drafts OAuth into a hosted CMS Writes unpublished drafts. You publish them. Preview-verified Not built yet
E · URL only Nothing: a public URL A scorecard and a patch you apply yourself. Advisory only Available now

Build-verified means a build actually ran. It applies to modes A, B and C and to nothing else. A hosted CMS has no build to run, so mode D is preview-verified and mode E is advisory. Those labels are never blurred, because the honesty of the verification is the product.

What you can do today

Scan the site. The free scorecard needs no access to Webhooks at all. It reads the published HTML the way a search or answer engine does, runs the full 129-check rubric against it, and reports what it could not measure rather than counting it as a pass.

Everything it finds is actionable by hand regardless of whether a connector ever exists, because the finding names the page and the change rather than a button to press.

Scan your Webhooks site All integrations