I can't create webhook for remote service

Question and Answers
1

Hi Nylas Team.

As our webhook is not being called when tried on remote server but works well in local dev setup. We even tried replicating using request catcher but got an error from NYLAS dashboard.

image
image654×371 52.8 KB

I already tested with my local port by forwarding the port as public https and it worked well.
In this case, webhook was created successfully.
But when I try to create new webhook after deployment, it was not working.

The interesting thing are below:
I checked the /GET endpoint for checking challenge - .xyz Domain Names | Join Generation XYZ, on the browser and curl.
And I got response of testnylas successfully. So I thought the service is public and working well.
But when I try to create webhook for this remote service, I got the error like the above.

Important: Our service is behind of Cloudflare, but it is public (confirmed it by checking browser and curl).

Please help me to resolve this issue.

2

Hello,

I was looking at your webhook endpoint, and when trying to make a GET call and passing a test challenge, the challenge is not returned, can you check if it’s configured correctly?

Request
GET
https://nylas-test.requestcatcher.com/test?challenge=123

Response:
request caught

Expected Response:
123

Let me know if you have any question.

Many thanks,
Samuel R.
Support Engineer, Nylas

3

Thanks for your update.
It was just sample, I will provide the real endpoint.

https://athena-backend.dev.captivat.io/nylas/webhook

Here is our webhook endpoint,
When we try to verify challenge on the browser and curl, it is working well, got the challenge like below.

https://athena-backend.dev.captivat.io/nylas/webhook?challenge=123123, then got response of 123123

But when I try to create webhook with this endpoint on nylas dashboard, it is not working.

image
image725×490 32.7 KB

Please check this and let me know how to resolve it.

Best,

John

4

Hi @Samuel.R ,

Please check my last message.

Thanks,

John

5

Hello John,

When looking at the headers that your URL is returning, I can see that is returning

“Content-Type:text/html; charset=utf-8”

Can you try returning:
“Content-Type:text/plain”

Also, we can see that Transfer-Encoding is chunked, let us know if you are able to try changing those 2 Headers in response.

Many thanks,
Samuel R.
Support Engineer, Nylas

6

Hello. Our Support team has reached out to you via email to continue this investigation. Please check your mailbox for our message.