Reference
Webhooks
Configure automatic deployments triggered by Git push events.
How webhooks work
LoomDeploy exposes a public webhook endpoint per project. When your Git host sends a push event to that URL, a new deployment is triggered automatically.
Getting your webhook URL
- Go to Project → Settings.
- Copy the Webhook URL — it looks like:
https://dashboard.yourdomain.com/api/webhooks/abc123secrettoken
Setting up on GitHub
- Go to your repository on GitHub.
- Open Settings → Webhooks → Add webhook.
- Paste your webhook URL into Payload URL.
- Set Content type to
application/json. - Select Just the push event.
- Click Add webhook.
Regenerating the secret
If your webhook URL is compromised, go to Project → Settings and click Regenerate Webhook. The old URL will stop working immediately.
Supported Git hosts
Any Git host that supports webhooks with JSON payloads works with LoomDeploy:
- GitHub ✅
- GitLab ✅ (push event)
- Gitea ✅
- Bitbucket — planned
Webhook payload
LoomDeploy only checks that the request hits the correct secret URL — it does not validate the payload signature. Any POST request to the webhook URL triggers a deployment.
Keep your webhook URL secret. Anyone who knows it can trigger a deployment.
