# Webhook setup issue

**URL:** <https://connective.celigo.com/t/webhook-setup-issue/6094>\
**Category:** Integrator.io\
**Created:** [February 25, 2026, 9:55am UTC](https://connective.celigo.com/t/webhook-setup-issue/6094 "2026-02-25T09:55:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samson\_Vincent](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@Samson\_Vincent](https://connective.celigo.com/u/Samson_Vincent)\
**Post date:** [February 25, 2026, 9:55am UTC](https://connective.celigo.com/t/webhook-setup-issue/6094/1 "2026-02-25T09:55:02Z")

</div>

I am creating a custom flow to sync Sales Orders from an external application to NetSuite using a Webhook Listener as the source. When I tested the public URL using Postman with the HTTP method set to **POST** , the flow triggered correctly and the data synced to NetSuite without any issues.

However, when the client triggers the same public URL from their application, the webhook is getting invoked but the flow does **not** run. In the Celigo debug logs, the incoming request is shown with the HTTP method as **GET** , which prevents the flow from executing.

This flow is currently working correctly in the client's Boomi integration setup. To validate whether the issue is on the client side or within the Celigo integration, the client temporarily switched the webhook URL from Celigo to Boomi without making any other configuration changes. After updating only the URL, the sales order synced successfully into NetSuite through Boomi with no failures.

When we reviewed the Boomi logs, it was clear that the client’s system is sending the request using the **POST** HTTP method. However, when the same request is sent to the Celigo webhook listener, Celigo is receiving it as a **GET** request, which prevents the flow from executing.

Additionally, the client is sending the data in **cXML** format. Since Celigo does not have a direct cXML option, we configured the webhook listener’s data format as **XML** , which should still accept and parse the incoming payload. This configuration works correctly when tested via Postman using **POST** , but not when the client sends it.

This raises the question: if the client is definitely sending **POST** , why is Celigo receiving it as **GET**?

 ![image](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/b/b99dd53053411a10c93f3665c68bdf7823723eee.png)

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [March 4, 2026, 5:47am UTC](https://connective.celigo.com/t/webhook-setup-issue/6094/2 "2026-03-04T05:47:49Z")

</div>

I've never seen this. I'd make a support ticket and see if support/eng can review internal logs.