Setup
Get Webhooks running
Three steps, no migration. Point it at your project and the first keys land in the dashboard.
- InstallAdd the package or the config block. Nothing else in your build changes.
- Connect your projectUse the org/project identifier from your dashboard. Keys and languages come from there, not from a local file you have to keep in sync.
- ShipPublish once and every locale is a static file on the edge. Copy changes go live without a new deploy.
Where it fits
How Webhooks works inside Better
Detect
Pull source strings from your codebase or connect your Webhooks repository. Keys arrive in Better with structure and context intact.
Review
Run AI translation, assign human reviewers, and gate approval before any change reaches production. Everything auditable in one place.
Ship
Publish to the CDN edge or push translations back to Webhooks. Copy changes go live without triggering a new app deploy.
Built for modern stacks
Works with the tools your team already uses — fits naturally into CI, review, and edge delivery pipelines without heavy process overhead.
Less operational drift
Centralize translation updates, review sign-off, and delivery in one workflow instead of spreading work across separate tools and scripts.
Controlled rollout
Decouple translation publishing from code releases. Ship copy changes on your schedule without waiting for the next deploy window.
Questions
Before you connect it
Next
Connect Webhooks today
Free to start. Add the integration, publish once, and see the copy change without a release.