WOOCOMMERCE TRIGGER: The "key" argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined

Questions
1

Hi i have the same issue of this old thread. how can i fix it ?

from server log
2026-Jan-21 17:10:09
Received request for unknown webhook: The requested webhook “POST dc8a15c5-df43-4728-8635-4c2af4a519f9/webhook” is not registered.
2026-Jan-21 17:10:10
Received request for unknown webhook: The requested webhook “POST 6dc05f3b-f0fc-4205-84c2-bce7e625a1dd/webhook” is not registered.
2026-Jan-21 17:23:41
The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined
2026-Jan-21 17:23:41
Error in handling webhook request POST /webhook/e24eb1ed-d2c9-408e-b5f4-b5b009808a27/webhook: Workflow Webhook Error: Workflow could not be started!
2026-Jan-21 17:23:41
The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined
2026-Jan-21 17:23:50
The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined
2026-Jan-21 17:23:50
Error in handling webhook request POST /webhook/e24eb1ed-d2c9-408e-b5f4-b5b009808a27/webhook: Workflow Webhook Error: Workflow could not be started!

2

im stuck some one can help ? Problem in node ‘WooCommerce Trigger‘ The "key" argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined · Issue #24681 · n8n-io/n8n · GitHub

3

I am getting the same error. I have no clue how to fix it. It only happens in production

4

If this happened to me, I’d suspect that something changed on the WooCommerce side that caused n8n to trigger an error,

Instead of waiting for a fix to the built-in WooCommerce node, I’d set up a native webhook trigger and configure it to behave like WooCommerce trigger node,

IMO, This gives better control and makes debugging easier.

5

For me, the issue appeared after the last n8n update…

WooCommerce is the same.

I have tried to recreate the webhook and more but it does not solve it.

This issue appears in an old GitHub issue of n8n…

with a manual webhook return always 401

6

Any luck solving it? I have the same issue.

7

This should be resolved in 2.7 can you try updating and let me know if you still see the same issue.

8

I’m having the same issue. I just tried version 2.7.3, but I keep getting the same error.