How to Test Help Scout Webhooks
Help Scout webhook events cover conversation activity, customer changes, and satisfaction ratings so you can sync support data into your CRM, BI tools, or ops dashboards.
Help Scout Official Webhook Docs1. Help Scout Webhook Events
Help Scout can send the following webhook events to your endpoint:
convo.createdconvo.assignedconvo.statusconvo.tagsconvo.note.createdconvo.deletedcustomer.createdsatisfaction.ratings2. Set Up a Test Endpoint with HookRay
Follow these steps to start receiving Help Scout webhooks for testing:
- Go to HookRay and click "Start Testing — Free" to get your unique webhook URL.
- Copy the URL (e.g.,
https://h.hookray.com/abc123). - In your Help Scout dashboard, navigate to the webhook settings and paste the HookRay URL as your endpoint.
- Select the events you want to receive (see list above).
- Trigger a test event — HookRay will show the incoming webhook in real-time.
3. Sample Help Scout Webhook Payload
Here's an example of what a Help Scout webhook payload looks like:
{
"id": 12345678,
"number": 4242,
"threads": [
{
"id": 87654321,
"type": "customer",
"createdBy": {
"type": "customer"
},
"body": "Has anyone solved Stripe webhook signature timeouts?"
}
],
"status": "active",
"subject": "Stripe webhook signature timeouts",
"mailbox": {
"id": 999,
"name": "Support"
},
"assignee": null
}4. Frequently Asked Questions
How do I test Help Scout webhooks without deploying?
Use HookRay to get an instant public webhook URL. Paste it into your Help Scout dashboard's webhook configuration, trigger an event, and watch the payload arrive in real time. No code, no ngrok, no deployment. The free tier captures 100 requests per month and works for all Help Scout event types.
Why aren't my Help Scout webhooks arriving?
Four common causes: (1) the endpoint URL isn't publicly accessible — Help Scout can't reach localhost; (2) the wrong events are subscribed in your dashboard; (3) signature verification is rejecting the request before your handler runs; (4) a firewall, expired SSL certificate, or DNS misconfiguration is blocking Help Scout's requests. Use HookRay's URL to isolate which of these four is failing.
Why am I getting 400 or 500 errors from my Help Scout webhook?
Help Scout reports the status code your endpoint returned. HookRay accepts any payload and returns 200 OK by default, so if you see 400/500 while pointing at HookRay, the issue is in Help Scout's configuration. If you point at your own endpoint and get 400/500, capture the request with HookRay, replay it locally, and debug from the captured payload.
How do I verify Help Scout webhook signatures?
Help Scout signs each request with a shared secret. Capture the raw headers and body using HookRay, then verify the signature in your application using Help Scout's SDK or a standard HMAC library. Once verification works against HookRay-captured data, you can safely deploy.
Can I replay a captured Help Scout webhook?
Yes — HookRay's replay feature re-sends any captured webhook with one click. This is the fastest way to fix a buggy handler: capture the payload once, fix your code, replay until it works. No need to re-trigger events in Help Scout.
5. Next Steps
- Use HookRay's webhook replay feature to re-send captured webhooks while building your handler
- Enable smart parsing (Pro plan) to see Help Scout-specific fields highlighted automatically
- Check the Help Scout webhook documentation for the complete event reference
Ready to test Help Scout webhooks?
Get a free webhook URL in 5 seconds. No signup required.
Start Testing Help Scout Webhooks — FreeFree PDF: Webhook Testing Cheat Sheet 2026
One-page reference for 50+ APIs — canonical events, signing methods, sample payloads. Print it, pin it, share it.
📄 Download the cheat sheet (PDF, 180KB)