Docs / Troubleshooting / Webhook Not Triggering Deploy Playbook

Webhook Not Triggering Deploy Playbook

Published · Last updated: May 2026 · 3 min read

Who this is for

Users who have set up automatic deploys via webhook (push-to-deploy) but find that pushes to the repository are not triggering a deployment.

How Webhook Deploys Work

  1. CloudAIPilot generates a unique webhook URL for each site or app.
  2. You register this URL as a webhook in your git provider (GitHub, GitLab, Bitbucket).
  3. When you push a commit to the configured branch, the git provider sends an HTTP POST to the webhook URL.
  4. CloudAIPilot receives the request, verifies the token, and triggers a deployment.

Step 1 — Verify the Webhook Is Registered

  1. Open Site detail → Git tab (or App detail → Source tab).
  2. Copy the Webhook URL shown.
  3. Go to your git repository → Settings → Webhooks.
  4. Confirm the webhook URL is registered and matches what CloudAIPilot shows.

Step 2 — Check the Webhook Delivery Logs

Most git providers log every webhook delivery attempt:

GitHub: Repository → Settings → Webhooks → Click your webhook → Recent Deliveries tab.

GitLab: Repository → Settings → Webhooks → Click the webhook → View details.

Bitbucket: Workspace settings → System hooks, or Repository settings → Webhooks → View requests.

Look for:

  • HTTP status code: 200 means CloudAIPilot received and accepted it. Any other code is a problem.
  • Timing: if no delivery attempt shows, the webhook URL was not triggered (check the branch filter).

Step 3 — Check the Configured Branch

CloudAIPilot only deploys when a push is to the configured branch:

  1. Open Site/App → Git settings.
  2. Check the Branch field.
  3. Ensure you are pushing to the exact same branch (case-sensitive).

If you pushed to main but the webhook is configured for master, no deploy will fire.

Step 4 — Re-test the Webhook Manually

  1. In your git provider, find the webhook delivery log.
  2. Click Redeliver on the most recent delivery.
  3. Check CloudAIPilot's Activity Center for a new deployment job.

If redelivery triggers a deploy: the webhook is working. The issue was a missed push or branch mismatch.

If redelivery does not trigger: check CloudAIPilot's webhook secret.

Step 5 — Rotate the Webhook Secret

If CloudAIPilot is returning 401 or 403 on webhook deliveries:

  1. In Site/App → Git settings, click Rotate Webhook Token.
  2. Copy the new token.
  3. Update the webhook secret in your git provider to match the new token.

Step 6 — Check CloudAIPilot Is Reachable from the Internet

The git provider's servers must be able to reach CloudAIPilot's API at https://app.cloudaipilot.com (or your staging URL). If CloudAIPilot is behind a firewall or unreachable, webhook deliveries will fail silently.

Common Causes and Fixes

SymptomCauseFix
Git provider shows delivery 200 but no deployBranch mismatchUpdate the branch setting to match your push target
Git provider shows 401 UnauthorizedWebhook secret mismatchRotate token and update in git provider
Git provider shows 404 Not FoundWebhook URL is wrong or site was deletedRe-copy the webhook URL and re-register
No delivery attempts at allWebhook not registeredRegister the webhook URL in the git repository settings
Deploy triggered but failsDeployment issue, not webhookSee KB-12-01: Deployment Failed Playbook

Related Articles