Skip to main content

Webhooks & Auto-deploy

Webhooks let you trigger a QuickStack deployment via an HTTP POST request — typically from a Git hosting platform or CI pipeline on every push.

How it works​

QuickStack generates a unique, secret-bearing webhook URL per app. When your Git provider or CI system sends an HTTP POST to this URL, QuickStack triggers a new deployment of that app — identical to clicking Deploy manually.

Configuring a webhook​

  1. Open the app in QuickStack.
  2. Go to the Overview tab.
  3. Click Enable Webhook Deployments.
Enable Webhook Deployments

  1. Copy the generated webhook URL. It looks like:

    https://your-quickstack-domain/api/v1/webhook/deploy?id=YOUR_WEBHOOK_ID

  2. Add this URL as a webhook in your Git repository or CI system (see examples below).

GitHub​

  1. In your repository, go to Settings → Webhooks.
  2. Click Add webhook.
  3. Payload URL: paste the QuickStack webhook URL.
  4. Content type: application/json.
  5. Which events: choose Just the push event.
  6. Click Add webhook.
GitHub Webhook Configuration

GitLab​

  1. In your repository, go to Settings → Webhooks.
  2. URL: paste the QuickStack webhook URL.
  3. Trigger: select Push events.
  4. Click Add webhook.
GitLab Webhook Configuration

Testing​

Push a commit to GitLab/GitHub. A new deployment should appear in the app's Overview tab within seconds.

Troubleshooting​

SymptomFix
Webhook not triggeringVerify the URL is correct; check Git provider's webhook delivery logs
Wrong branch deployedWebhook triggers whatever branch is configured in app settings
Deploy triggered but app unchangedConfirm the configured branch has the new commit

Reference​

Webhook URL pattern: https://<quickstack-domain>/api/v1/webhook/deploy?id=<webhook-id> — see Ports & Endpoints for more.