# Check for error on webhook submission and return message

**URL:** <https://community.gravityforms.com/t/check-for-error-on-webhook-submission-and-return-message/18259>\
**Category:** Get Help\
**Tags:** webhooks, gform\_is\_feed\_asynchronous\
**Created:** [September 25, 2024, 6:55pm UTC](https://community.gravityforms.com/t/check-for-error-on-webhook-submission-and-return-message/18259 "2024-09-25T18:55:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![user5a21b0238cbd02.7](https://sea2.discourse-cdn.com/flex020/user_avatar/community.gravityforms.com/user5a21b0238cbd02.7/32/93_2.png) [@user5a21b0238cbd02.7](https://community.gravityforms.com/u/user5a21b0238cbd02.7)\
**Post date:** [September 25, 2024, 6:55pm UTC](https://community.gravityforms.com/t/check-for-error-on-webhook-submission-and-return-message/18259/1 "2024-09-25T18:55:17Z")

</div>

Hi,

I’m using the Gravity Form webhook addon to send a submission to an API endpoint. I want to be able to display a message to a user if the submission encounters an error. Would the best way to accomplish this be with using [gform\_webhooks\_post\_request - Gravity Forms Documentation](https://docs.gravityforms.com/gform_webhooks_post_request)? Check the request and then display the error? Does this happen before the confirmation notice is displayed?

Ideally form is submitted, webook is fired, if API returns error display error message to user “Unfortunately an error occurred with your submission.” Otherwise display GF normal notification message.

Thank you for your help.

Best,

Tom

---

<div class="post-metadata">

**Author:** ![uamv](https://sea2.discourse-cdn.com/flex020/user_avatar/community.gravityforms.com/uamv/32/1412_2.png) [@uamv](https://community.gravityforms.com/u/uamv)\
**Post date:** [September 25, 2024, 9:12pm UTC](https://community.gravityforms.com/t/check-for-error-on-webhook-submission-and-return-message/18259/2 "2024-09-25T21:12:35Z")

</div>

Most add-ons process feeds asynchronously so that they are executed after submission has already completed. Reference [Add-On Support for Background Feed Processing](https://docs.gravityforms.com/support-background-feed/). If you’d like to handle form submission or confirmation based on the webhook request, you would first need to use [gform\_is\_feed\_asynchronous](https://docs.gravityforms.com/gform_is_feed_asynchronous/) in order to disable this default behavior for the feed. Depending on your result, you could then hook to [gform\_confirmation](https://docs.gravityforms.com/gform_confirmation/) to filter the confirmation.

---

<div class="post-metadata">

**Author:** ![user5a21b0238cbd02.7](https://sea2.discourse-cdn.com/flex020/user_avatar/community.gravityforms.com/user5a21b0238cbd02.7/32/93_2.png) [@user5a21b0238cbd02.7](https://community.gravityforms.com/u/user5a21b0238cbd02.7)\
**Post date:** [September 26, 2024, 1:21am UTC](https://community.gravityforms.com/t/check-for-error-on-webhook-submission-and-return-message/18259/3 "2024-09-26T01:21:57Z")

</div>

Hi Joshua,

Thank you for the response. Just so I’m clear on this you recommend:

1. Since the webhook addon fires asynchronously I should first disable this using gform\_is\_feed\_asynchronous. Are there any downsides to doing this?

2. Once this is disabled will the confirmation message displayed to a user be displayed after the webhook is fully complete (including the response being returned)? If so, I can then fetch the response and display a message depending on the status code using gform\_confirmation filter?

Thank you for the clarification

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/gravityforms1/original/2X/f/fef63f0599c45e0218c30d9f5d7ca8bff9b00189.png) [@system](https://community.gravityforms.com/u/system)\
**Post date:** [October 26, 2024, 1:22am UTC](https://community.gravityforms.com/t/check-for-error-on-webhook-submission-and-return-message/18259/4 "2024-10-26T01:22:05Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
