A target of type Webhook transfers no files. It calls a URL and thereby asks a provider to build the site itself — Netlify, Cloudflare Pages, Vercel, a CI system.
What that changes
There is no file list here. No diff, no count of uploaded files, no progress over files — the build runs there, not here. QuartzControl says so on the card itself.
The confirmation question is correspondingly short:
Trigger the webhook “…”?
No files are transferred. The provider is only asked to build on its own.
Where the URL comes from
From the provider. It lives on the connection, not on the target, because it is a credential: whoever has it can trigger builds. It therefore lives in the keychain like a password.
If no URL is stored on the connection, the target says so — “no URL stored” — instead of failing on the click.
What the provider needs
For the build to find anything there, the provider has to reach the sources — usually through the repository. So the usual sequence is: first git sync, then trigger the webhook.