Crawld and Zapier
Route scan results into whatever your team already uses.
Status: Not built yet . this connector is not built. The page describes how delivery works on Zapier given the constraints of the platform, and what verification would honestly be available. Today you can run the free scorecard against a Zapier site without granting any access at all.
How fixes would arrive
A trigger fires in Zapier and you decide where it goes: Slack, a ticket, a spreadsheet.
Zapier moves information between tools. It can carry a finding to the person who should act on it; it cannot compile anything.
There is no build to verify against on a hosted CMS, so the change is checked in preview instead. This rung is deliberately never labelled build-verified, because it is not.
What the rubric can see here
- Scan completed triggers
- New fix queued triggers
- Mapping findings into a tracker or a channel
Limits worth knowing before you plan around this
- Nothing routed through Zapier is build-verified, because nothing is built
- Rate limits are Zapier’s, and they are stricter than the API’s
Not build-verified. Zapier sits on Mode D, so a change delivered here is preview-verified: never build-verified. That badge means a build actually ran, and on this platform there is no build to run.
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 Zapier 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.