I have setup a webhook for install event. I would like to know what will happen if my site is down. Will the webhooks get retried incase of non 200 response codes.
That's a good question! Branch does not automatically retry webhooks in the case of a non 2xx response. However, Branch does allow you to go through and see every single time they have tried to fire a webhook. In the case of a non-2xx response, you would see a red 'X' next to the record. From there you can manually re-send said webhook to your server.
If this post does not resolve your issue(s) please ask more!
Related
We are using a number of webhooks for testing purposes with the DEMO company and this means the webhook queue is full of items.
Is it possible to remove all these items that i am seeing in the webhook queue as i am getting an error about too many requests?
It isn't possible to remove items from the queue manually. That said, once they've been sent and your script has responded correctly they won't be sent again. As such you should just need to allow your script to receive everything in the queue.
Alternatively you could reset your demo company. This will also reset the webhooks and any data you have entered.
The use-case would be to trigger certain jobs, only after an MR is not in WIP anymore.
The idea what I'm exploring is to create a merge-request webhook, that would trigger a pipeline.
However in order to do this, I have to get the ref from the webhook's request body to call the trigger accordingly.
What options do I have?
Running a server just for processing the webhook and redirecting to the correct endpoint is not really an option.
Running a server just for processing the webhook and redirecting to the correct endpoint
I dont see any other way. I'm in same boat. Gonna use Heroku for just this bit. Oh well.
I'm implementing a Mail to Webhook Zapier integration. When testing the webhook during the creation process, the test is stuck and won't move on to the next step in the creation process.
When looking at my app logs, I see that the webhook is being sent over and over again, and doesn't stop, even though the app sends '200 ok' in the response.
Why does this happen? What response do I need to send to make it finish?
David here, from the Zapier Platform team.
It's hard to say for sure, but I believe the response needs to include some content. At minimum, that's {} (valid JSON), but it could also be {"ok": true} or something.
That said, an empty response is something we should handle so if you could write into partners#zapier.com with your zap id, we can take a closer look!
I've set up a ZAP so that when a subscriber is added to my aweber email list they are automatically added to a product in my membership plugin called DAP or digital access pass.
As per the instructions of the membership plugins developers, I am using a webhook in the zapier 'post' section.
It's not working. Quite simply the webhook doesn't appear to be calling anything.
Now, weird thing is that zapier logs show the webhook has been sent and has had success. But from DAP's end nothing is being received.
The support team at DAP tell me that the script isn't being called, because nothing appears in their logs.
They show me this by putting the webhook URL into a browser and calling it that way, and THEN the relevant info arrives in the DAP logs.
Zapier told me they do not trouble shoot and so advised that I post here.
Would appreciate any help. Thank you very much.
Dan
You can easily test if Zapier is making a call or not by sending the request to http://requestb.in
Steps:
Create a request bin and copy the URL.
Request bin screenshot
In Zapier, replace the webhooks post URL with the requestb.in URL.
Now, whenever the Webhook makes a post request, you should be able to visit the inspect page of your bin and check if a request was received. Just add ?inspect to the end of the URL. For example, if your Request bin URL is https://requestb.in/wbto8jwb then you should visit https://requestb.in/wbto8jwb?inspect
The inspect page will show all the requests received.
With this, you will know if Zapier is sending the requests. If the requests are being received by request bin then there is something which needs to be fixed by DAP.
Note that it could also be something in the configuration of the Webhook that is causing the request to not be recognised by DAP. It will help if you add more details to your question - what format is the DAP team expecting to receive the data in?
Below is a sample Webhook implementation in Zapier.
I have added a hook to POST data to a request bin (https://requestb.in/wbto8jwb)
Webhook POST screenshot
When I test this step, the request is received in the Request Bin Inspect page (https://requestb.in/wbto8jwb?inspect).
Request Bin Screenshot
More reading:
https://zapier.com/help/webhooks/
Update:
You can also make a direct call to the DAP API by using a tool like https://www.hurl.it/. From the drop down in destination, select POST and put the URL here. Click on Add body and paste the raw data from request bin. Now ask the DAP team to check if the request was received.
I've created a telegram bot and set a webhook as described in the docs. For testing purposes I've set it up so once you send the bot a message it replies back with the same message.
Now the issue I am having is that the updates from telegram are coming back really slowly and there are some messages I haven't received yet. Am I missing something or is the webhook method just really slow?
I had the same problem. Turns out I wasn't responding the telegram server after I got the POST request. Due to this, the server wasn't sure if I got the previous updates and was constantly sending my webhook past updates.
I have an express server and I added this bit of line after handling the POST Request.
res.sendStatus(403)
You can also confirm this by going to this url
https://api.telegram.org/<token>/getWebhookInfo
You'll see a property called pending_update_count. It should zero or close to it.