ClickUp trigger (task CRUD) error in production: 'key' argument

[curzey]

Describe the problem/error/question

Running a simple workflow catching CRUD-events from ClickUp tasks using the default ClickUp trigger node works fine while testing.

However, as soon as I publish the workflow, the real executions throws errors. And even through “Retry on fail” is off, it seems like it keeps throwing many errors just from one event.

What is the error message (if any)?

Problem in node ‘ClickUp Trigger‘
The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined

Please share your workflow

removed

Share the output returned by the last node

{
“errorMessage”: “The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined”,
“errorDetails”: {},
“n8nDetails”: {
“n8nVersion”: “2.4.4 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: \[
“TypeError: The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined”,
" at prepareSecretKey (node:internal/crypto/keys:684:11)“,
" at new Hmac (node:internal/crypto/hash:166:9)”,
" at createHmac (node:crypto:163:10)“,
" at WebhookContext.webhook (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base\_@[email protected]_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/ClickUp/ClickUpTrigger.node.ts:332:39)”,
" at WebhookService.runWebhook (/usr/local/lib/node_modules/n8n/src/webhooks/webhook.service.ts:386:31)“,
" at Object.executeWebhook (/usr/local/lib/node_modules/n8n/src/webhooks/webhook-helpers.ts:474:60)”,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)"
\]
}
}

Information on your n8n setup

n8n version: 2.4.4
Database (default: SQLite): SQLite
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
Operating system: macOS Tahoe 26.0

[achamm]

This is a known issue with the ClickUp trigger node where it receives malformed webhook data from ClickUp that causes the “key” argument error. The problem typically occurs when ClickUp sends webhook payloads with undefined or null values that the node can’t process properly.

Here are a few solutions to try:

• **Update n8n**: Make sure you’re running the latest version as this bug has been addressed in recent releases

• **Recreate the webhook**: Delete and recreate your ClickUp trigger node, which will register a fresh webhook with ClickUp

• **Check ClickUp API permissions**: Ensure your ClickUp API token has the correct permissions for the workspace and events you’re trying to monitor

• **Add error handling**: Use an “Error Trigger” node or “Continue on Fail” setting to catch and handle these webhook errors gracefully

If the issue persists, you might need to use the HTTP Request node with ClickUp’s webhook API directly as a workaround until the trigger node is fully stable.

[curzey]

Thanks for the reply.

I figured since I found some old threads around, but generally seems like it should have been fixed. But I’ve tried both the latest stable and also latest beta.

Also tried recreating the webhook node - changes nothing unfortunately.

Used ‘Continue on Fail’ but seems like the next node just recieves an empty array in those cases. So not much to work with.

Thanks anyways. Will stick the the HTTP Request node for now

[achamm]

Your Welcome!