Skip to main content

Blocking rules for invalid Webhook's URLs

Help Center
  • Updated

Index:

  1. How data is sent through Webhook?
  2. Dealing with non-working URLs
  3. Data send blocking rule

 

Data can be sent from your chatbots to a defined Webhook using Blip settings.

With this setting active, any Messages, Event Tracking or Contacts generated by your chatbot will be sent to your Webhook. 

 

But, there are some policies controlling the sent content to the configured Webhooks.

mceclip0.png

How data is sent through Webhook?

During bot’s flow, Blip sends Messages, Event Tracks and Contacts to URLs previously configured in “Integrations -> Webhook”. The configured URLs must be prepared and working to receive and process them.

 

The services in the configured URLs to receive Webhook data can stop to work because of flow increase, some code problem or even server problems. So, the configured URLs can refuse the information sent from Blip. 

 

Is the same situation when you send a package to an address that doesn't exist. When the postman arrives to deliver your package he’ll not find the adss and the package won’t be delivered.

dre

mceclip1.png

Dealing with non-working URLs

If the described scenario happens, all that data sent to the Webhook will not be received by the configured URL. 

 

As long as Blip continues to send data, the other side will not receive it until the root problem is fixed, the failing URL should be removed or updated to another one that is working properly.

 

To deal with that non expected situation, Blip can identify if the informed URL is healthy and send data if it is working.  If the URL is not working properly, the specific Webhook will be blocked and a message will be displayed below of the configured URL that can be accessed in: “Integrations -> Webhook”. In addition, the data will not be sent in accordance with the rule described below.


mceclip2.png

Data send blocking rule

The rule is based on the number of identified errors and will be active during time intervals.

 

Exemple:

The configured URL returned an error for 1000 CONSECUTIVE times it will be blocked and will not receive data from Blip for 4 hours. After 4 hours the URL is released and the number of errors continues to be observed.

If it fails again for 1000 CONSECUTIVE times, it will be blocked again for 4 hours and so on.

 

To solve the data sending problem to your Webhook, check the registered URL and make the necessary changes. Our device will rescan after the lockout period stated above.

 

Important: The blocking rule works separately for each item type. 

 

In other words, as we have 3 types of items sent to registered Webhooks (Message, Event Registration and Contacts), the Webhook can fail to receive Messages, but it can still receive Events and Contacts data. So, if the number of failures for sending message data is greater than the established limit (1000 consecutive failures), the sending of message data will be blocked, but the sending of event and contact log data will continue normally.

 

See below a diagram that exemplifies how the validations are made when sending data to Webhook.

 

unnamed.png

 

 

Ready! Now you know about invalid URL blocking rule in Webhook.😀

 

 

For more information, visit the discussion on the subject in our community or the videos on our channel. 😃

Related articles

Powered by Zendesk