I’ve set up a self-hosted instance of n8n and created a webhook endpoint, which is working correctly with various other services. However, when I try to register the same webhook with Raekdata, it consistently fails.
To isolate the issue, I tested the same Raekdata integration using a Zapier webhook, and it registered and worked seamlessly. This leads me to believe there may be something in the way Raekdata interacts with n8n’s webhook that’s causing the problem.
Could you please look into this or advise if there are any known limitations or configurations needed for compatibility with Raekdata?
I’d be happy to provide additional technical details or logs if needed.
Hey @Saad_Jawaid hope all is well. Would you like to expand on what is the problem exactly? How does it fail? How is it configured in n8n? How is it configured on the other side - with Raekdata? Some outputs, screenshots?
Thanks for sharing. Since the webhook works with other services but not Raekdata, it’s likely an issue with how Raekdata expects the response.
Try adding an HTTP Response node right after the webhook that returns a 200 OK with a simple JSON body. Also make sure your webhook URL is served over HTTPS with a valid SSL.
If Raekdata provides logs or error details, feel free to share — happy to help debug further.
