Describe the problem/error/question
Hello n8n Community,
I am creating this topic to seek a solution for a critical and persistent error with the native ClickUp Trigger node. When I try to create a new trigger for the Task Status Updated event, it consistently fails during the webhook validation phase
The Error:
The workflow fails with the following cryptographic error, indicating the secret key for validation is not being found by n8n:
{
“errorMessage”: “The "key" argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined”,
“errorDetails”: {},
“n8nDetails”: {
“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 (…/n8n-nodes-base/nodes/ClickUp/ClickUpTrigger.node.ts:332:39)”
]
}
}
Exhaustive Troubleshooting Performed:
I have performed extensive testing to isolate the cause, but the error persists in all scenarios when creating a new trigger:
- Multiple n8n Versions: This is not a regression in a single version. The error occurs on:
1.23.102.3.22.3.102.4.7(latest version tested)
-
Multiple Server Environments: This is not a configuration issue. The error persists across three different, properly configured server environments (all with
N8N_ENCRYPTION_KEYset). -
Multiple Authentication Methods: This is not a credential issue. The error occurs with both API Token and OAuth2 methods.
-
Control Tests:
- Existing Triggers Work: My older ClickUp triggers on the same n8n instance continue to run without any issues. The problem is specific to the creation/activation of new triggers.
- Make.com Works: A webhook for the exact same event on Make.com works perfectly, confirming the ClickUp API is functioning as expected.
Conclusion and Question:
All evidence points to a recurring bug within the n8n ClickUp Trigger node’s lifecycle management, where it fails to handle its own webhook secret key correctly.
My question to the community and the n8n team is:
Is there any known, reliable solution or fix for this error, other than bypassing the native trigger entirely?
The current workaround of using a generic Webhook node with ClickUp’s Automations is stable, but it defeats the purpose of the native integration. I am hoping there is a way to get the native node working again.
Thank you for your time and any help you can provide.
Please share your workflow
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”: {
“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 (…/n8n-nodes-base/nodes/ClickUp/ClickUpTrigger.node.ts:332:39)”
]
}
}
Information on your n8n setup
- n8n version: The error has been reproduced across multiple versions, including
1.23.10,2.3.2,2.3.10, and latest2.4.7. - Database (default: SQLite): SQLite
- n8n EXECUTIONS_PROCESS setting (default: own, main):
main - Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
- Operating system: Linux