Skip to main content
Question

Webhook Error Debugging

  • April 17, 2019
  • 0 replies
  • 17 views
Is there any way of actually seeing what, exactly, the RESTful payload that was sent from a given webhook is? I know you can easily build the URL in the "endpoint URL" box when creating a webhook, but I've been stuck trying to figure out what's causing a 500 Internal Server Error for about 2 hours now with no luck. I can manually put in the values that are supposed to be getting passed from the fields, and then press enter in my browser, and it gives me a success message, but any time I edit the record in QB to match the trigger condition, it always spits out a 500 error.

Short of getting on a support call, is there a mechanism for seeing what fired, and what payload was sent? that error code isn't even useful because it doesn't tell me anything about what went wrong...
This topic has been closed for replies.

Forum|alt.badge.img+17
  • EvanMartinez
  • Community Moderator
  • April 17, 2019
Hi SF,

If you are having issues resolving a webhook 500 error there are some other tools out there that can be helpful. For troubleshooting this, we recommend an app like RequestBin. RequestBin doesn't try to interpret the payloads, it just prints them to your screen as it receives them, making it easy to see what is going on. Just click the Create a Request button on their homepage and copy the provided link. For example: http://requestb.in/18e5uxn3

Now, change the webhook's Endpoint URL to the new Requestb.in URL (you must replace "http" with "https"). Then, take the steps necessary to trigger the webhook once again (usually creating a record of some type). After you do that, simply refresh your Requestb.in page and take a look. This would allow you to see the payload of the webhook minus the URL component. For help with the error messaging you can also connect with our Care team. You can contact our Care team when signed into Quick Base by clicking on the question mark icon in the upper right hand corner and selecting Manage Support Cases or directly here. 

I hope this information is helpful SF.
Terms & ConditionsAccessibility statement