Webhooks move Buaze events into external systems automatically. Low ratings can create CRM tasks, support tickets or team notifications.
Webhooks are not for emitting every event; they are for routing the right events to the right destination. Design is choice, not instinct.
Which events should be sent?
A practical first event is low rating. Later, add new feedback, reply creation or campaign status events.
Secure endpoint
- Use HTTPS.
- Plan signature verification.
- Use idempotency for duplicate deliveries.
- Retry failed requests through a queue.
Operational examples
Common workflows include Slack notifications for 1-3 star feedback, CRM task creation or branch manager email alerts.
Kontrol listesi / Checklist
- Webhook URL uses HTTPS.
- Event types are defined.
- Retry behavior is planned.
- Payload examples were tested.
- Low ratings reach the correct team.
SSS / FAQ
What if the webhook endpoint is slow?
Accept the request quickly and process in the background. Use a queue to reduce timeout risk.
Can the same event arrive twice?
Yes, retries can cause duplicates. Design idempotent processing with event IDs.