D
Dustin Gonzalez
Hello team 👋
I share an improvement opportunity identified during the validation of a case related to Campaigns/Webhooks.
Currently, when a webhook executes a template submission and a functional error occurs during processing (for example: empty mandatory parameters), the response visible to the customer from HubSpot or from the execution of the webhook only returns:
```json
{
“message”: “Webhook task has been queued for processing”,
“status”: “queued”
}
with status code `202`.
The problem is that this return only confirms that the task was accepted in the queue, but it does not reflect the final result of the processing or the actual reason for the submission failure.
In the validated case, the template failed because the mandatory parameter `comments` was arriving empty:
```json
{
“comments”: “”
}
However, the customer had no immediate visibility of the error and could only identify it by manually logging in to:
Campaigns > Webhooks > click on “Failed”
and reviewing the detail of the return.
This creates confusion, since from the customer's perspective the webhook “seems successful” due to status 202, even if the shipment actually fails later.
Suggestion for improvement:
* State the final result of the webhook processing.
* Show functional template errors directly in the interface.
* Add greater traceability/log visible from the execution of the webhook.
* Allow you to view the exact reason for the failure without relying on the manual “Failed” report.
Example of the real error:
> “Some template parameters are empty: Comments”
Thank you 🙌
Created by Mariane Serapiao
·