Static sites need a rebuild before a piece is visible, so Oat calls the hook when content lands and follows the build.
Oat reads and writes only what is listed here.
Oat reads.
- Deployment state after each hook call
- Your site URL, to confirm reachability
Oat writes.
- One POST to your Deploy Hook per publish
The permission is narrow and yours to revoke.
A hook URL only, with no Vercel account access.
Connecting takes three steps.
- Create a Deploy Hook in your Vercel project.
- Paste the hook and your site URL.
- Add GitHub if your content lives there.
The decision stays yours.
The hook fires only after an approved revision lands, and Live confirmed waits for the build.
Creators ask this first.
- Does Oat need my Vercel login?
- No. The hook URL is the whole connection and the least privilege possible.