Webhooks by Pabbly Hook trigger step generate a unique Pabbly Hook URL for each connections. These Pabbly Hook URLs listen to any incoming data and capture it instantly.
Upon successfully capturing the data, Pabbly Hook webhook URL will return a 200 (OK) HTTP Status code to the source application sending data to the webhook URL.
If a user disables the connection, Pabbly Hook will return a 403 (Forbidden ) HTTP Status code to the source application sending data to the webhook URL.
If a user deletes the connection permanently, Pabbly Hook will return the 404 (Not Found) HTTP Status code to the source application sending data to the webhook URL.
The maximum webhook size that Pabbly Hook currently supports is 1mb for triggers. Any payloads that exceed this limit will receive a 413 (Entity too large) HTTP Status code.
The Source applications that are sending webhook data to Pabbly Hook can use the above HTTP Status codes to handle data sending appropriately.
Upon successfully capturing the data, Pabbly Hook webhook URL will return a 200 (OK) HTTP Status code to the source application sending data to the webhook URL. If a user disables the connection, Pabbly Hook will return a 403 (Forbidden ) HTTP Status code to the source application sending data to the webhook URL. If a user deletes the connection permanently, Pabbly Hook will return the 404 (Not Found) HTTP Status code to the source application sending data to the webhook URL.The maximum webhook size that Pabbly Hook currently supports is 1mb for triggers. Any payloads that exceed this limit will receive a 413 (Entity too large) HTTP Status code.
The Source applications that are sending webhook data to Pabbly Hook can use the above HTTP Status codes to handle data sending appropriately.
Last edited:
