Webhooks & APIIntegrations
Bitbucket Cloud
Trigger Wexio flows from Bitbucket Cloud events
Bitbucket Cloud signs webhook bodies with HMAC-SHA256 (when you opt into the secret feature) in X-Hub-Signature-256, matching GitHub's format.
Provider docs: Setting up webhooks in Bitbucket Cloud
Setup
1. Wexio connection
New connection → Inbound → Bitbucket Cloud preset. Prefills auth mode (GENERIC_HMAC_SHA256), header name (X-Hub-Signature-256), encoding (Hex), prefix (sha256=).
2. Bitbucket webhook
Repository → Settings → Webhooks → Add webhook.
| Field | Value |
|---|---|
| URL | The Wexio endpoint URL |
| Secret | A strong secret you pick — paste the same value into Wexio |
| Triggers | Pick the events you want |
3. Contact resolution
Like GitHub, Bitbucket events are typically ops-oriented. Use a static-contact pattern or resolve by author email when available.
4. Capture schema, bind a flow
Standard setup — trigger a test webhook, capture the schema, attach a Webhook Received trigger.
Troubleshooting
| Symptom | Fix |
|---|---|
| Signature mismatch | Make sure the secret is identical in Bitbucket and Wexio |
No X-Hub-Signature-256 header | The webhook was created without a Secret — edit it and add one |