Webhooks

Webhooks let WeekendBuilder automatically redeploy your project every time you push to the configured branch. You push — it builds and deploys.

How it works

When you create a project from a GitHub repo, WeekendBuilder registers a push webhook on that repo. GitHub calls the webhook URL on every push. WeekendBuilder verifies the signature, checks if the push is to the correct branch, and queues a build.

Quick Start (template) projects also have webhooks registered automatically on the GitHub repo that was created for them.

Finding your webhook URL

The webhook URL is:

https://api.weekendbuilder.io/projects/{project-id}/webhook

You can find the project ID in the dashboard URL when you open a project, or by checking the GitHub repo’s webhook settings under Settings → Webhooks.

Webhook security

Every webhook has a secret that WeekendBuilder and GitHub share. GitHub signs each payload with HMAC-SHA256. WeekendBuilder rejects any request where the signature doesn’t match, so only pushes from your actual GitHub repo trigger builds.

Manual redeploy

If you need to redeploy without pushing a new commit — for example after updating environment variables — click the Redeploy button on the project card. This queues a fresh build from the same commit.

Troubleshooting

Pushes aren’t triggering builds

• Check the webhook is active in GitHub under Settings → Webhooks. Look for a green tick next to recent deliveries.
• If deliveries show a red ×, click the entry to see the response. A 401 means the signature check failed — the webhook secret may have been regenerated. Delete and recreate the project to reset it.
• Make sure you’re pushing to the branch configured for the project (default: main).

Build triggered but not deploying

• Check the build logs on the project card for errors
• If the project is stuck in creating, check the FAQ for common causes