Bitbucket Cloud
Trigger Wexio flows from Bitbucket Cloud events
Bitbucket Cloud signs webhook bodies with HMAC-SHA256 in X-Hub-Signature when you add a secret, hex-encoded and prefixed with sha256=. You connect it with the Bitbucket preset, which uses Generic HMAC SHA-256.
Provider docs: Setting up webhooks in Bitbucket Cloud
Setup
1. Connect It in Wexio
Go to New connection → Inbound. Under Provider presets, click the Bitbucket chip in HMAC presets. It sets Authentication mode to Generic HMAC SHA-256 and fills in these fields. Check that they match.
| Field | Value |
|---|---|
| Signature header name | X-Hub-Signature |
| Encoding | Hex |
| Header prefix (optional) | sha256= |
Copy the Wexio endpoint URL. You paste the secret into Signing secret after the next step.
2. Set Up the Provider
In your repository, go to Settings → Webhooks → Add webhook and fill in these fields.
| Field | Value |
|---|---|
| URL | The Wexio endpoint URL |
| Secret | A strong secret you pick. Paste the same value into Wexio |
| Triggers | The events you want |
3. Resolve Contacts
Like GitHub, Bitbucket events are usually about operations, not customers. Send them through a proxy that adds the chat ID of a team contact, or resolve by author email when the payload has one and that person is a contact in Wexio.
4. Capture the Schema and Bind a Flow
Trigger a test webhook, capture the schema, then attach a Webhook Received trigger.
Troubleshooting
| Symptom | Fix |
|---|---|
| Signature mismatch | Make sure the secret is identical in Bitbucket and Wexio |
No X-Hub-Signature header | The webhook was created without a Secret. Edit it and add one |
Related
- Inbound Webhooks - auth modes, contact resolution and response codes
- Custom HMAC - how Generic HMAC SHA-256 verifies a request
- Webhook Received - the trigger that starts your flow
- Webhook History - check why a request failed