When I publish my clickUp Trigger node(when status is changed) it spams The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined. But for some reason it works when I just want to test it by clicking to listen trigger button.
What is the error message (if any)?
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
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste
the workflow.)
Share the output returned by the last node
The “key” argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received undefined
This looks like a known ClickUp Trigger issue.
What people have reported (especially on n8n Cloud) is: the ClickUp Trigger works fine when you “Listen for test event”, but once the workflow is active/published, real ClickUp webhooks start hittting the trigger and you get an error like:
“The ‘key’ argument must be of type string … Received undefined”
That usually points to the trigger node receiving unexpected / malformed webhook payload data from ClickUp, and the node doesnt handle it properly in production executions.
Do this:
Update n8n Cloud to the latest available version as This has been treated as a bug on certain versions, and fixes have been rolling out in newer releases.
Delete the existing ClickUp Trigger node, Add it again and reconfigure it
Make sure the token/OAuth connection has access to the workspace/list and the events you’re subscribing to.
If it’s firing constantly, temporarily deactivate the workflow or route failures into an Error Workflow so you can log it cleanly without filling your execution history.
If it still happens then it’s worth contacting n8n Cloud support with your workflow ID, the exact error message, confirmation that it only happens when the workflow is active (not test mode), so they can check if you’re hitting the same ClickUp Trigger bug and advise the best workaround.
Yeah the ClickUp webhook signature verification is what’s failing here, that “key” error means n8n is trying to verify the incoming webhook signature but the secret key it needs isn’t there or isn’t being passed correctly. When you test with “Listen for test event” it bypasses some of that validation which is why it works in test mode but breaks in production.
Since you’re on n8n Cloud you can’t really dig into the server logs to see exactly what’s happening, but I’d try recreating the ClickUp credentials from scratch in n8n and then setting up the trigger again so it registers a fresh webhook on ClickUp’s side. Sometimes the webhook gets into a weird state where the signature secret isn’t synced properly between ClickUp and n8n. Also worth checking in your ClickUp settings under Integrations > Webhooks to see if there are any stale webhooks registered that might be conflicting, you can delete the old ones and let n8n create a new one when you activate the workflow.
If that doesn’t fix it I’d reach out to [email protected] since this seems like it could be a bug with how the ClickUp node handles webhook signatures on Cloud specifically, they can look at the actual error logs on their end.