Configure Wemblo Webhook Subscriptions
Subscribe an HTTPS endpoint to selected Wemblo events and review delivery attempts and responses.
STEPS
- Create an HTTPS endpoint on the receiving server.
- Open Wemblo Developer Settings and Webhooks.
- Enter a descriptive endpoint name and URL.
- Choose only required events.
- Create or copy the webhook secret.
- Save and send a test event.
- Confirm the correct workspace, event type, response, and delivery log.
- Process long-running work asynchronously and return a successful response quickly.
Who should use it
Authorized developers and technical workspace users.
Where to find it in Wemblo
Wemblo -> Developer Menu -> Webhooks
Before you begin
- Use a server-side integration environment.
- Create separate test and production credentials.
- Use HTTPS and least privilege.
- Never expose a key or webhook secret in client-side code.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Endpoint | HTTPS event receiver. |
| Event Type | Subscribed Wemblo event. |
| Signature | Request verification value. |
| Retry | Repeated delivery after failure. |
| Idempotency | Processes an event once. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| 401 Unauthorized | Missing, invalid, revoked or wrong-workspace key. |
| 403 Forbidden | Scope or resource permission. |
| 422 Validation | Required field or data format. |
| 429 Rate Limit | Backoff, volume and plan/API capacity. |
| Webhook retries | Endpoint response, signature, timeout and processing speed. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: