Webhooks

Webhooks are how your Git provider notifies Nebion when repository events happen. Without a webhook, Nebion has no way to know when you create, update, or close a pull request — or when code is pushed to a branch.

How It Works

When you set up a webhook, your Git provider sends an HTTP request to Nebion every time a relevant event occurs. Nebion validates the request using a shared secret, then triggers the appropriate action:

Event	Action
PR created or opened	Deploy a new environment
PR updated (new commits)	Redeploy the existing environment
PR merged or closed	Remove the environment
Push to branch	Redeploy manual environments with auto-deploy enabled

Each webhook uses a unique URL and secret generated when you create a project. You add these to your Git provider's settings along with a deploy key so Nebion can clone your code.

Supported Providers

Follow the setup guide for your provider:

• Bitbucket — Bitbucket Cloud
• GitHub — GitHub.com or GitHub Enterprise
• GitLab — GitLab.com or self-hosted GitLab
• Gitea — Gitea or Forgejo (self-hosted)

All providers follow the same pattern: add a deploy key, create a webhook, and test with a pull request.