ClickUp Trigger Not Working in n8n

Questions
1

Describe the problem/error/question

Hello, I’m facing an issue with the ClickUp trigger in n8n. I have n8n running self-hosted in a Docker Swarm environment in queue mode, with editor, webhook, and worker instances configured and managed through stacks in Portainer.

In my workflow, I added a ClickUp trigger to pull newly created tasks. However, when I test the trigger, it does not return the new tasks created in ClickUp. I have already validated the credentials, and they do not seem to be the problem, as I can use n8n to create tasks in ClickUp. The issue seems to occur only when n8n tries to listen to updates in ClickUp through the trigger.

It’s important to mention that this issue occurs only with the ClickUp trigger; other workflows are functioning correctly. Has anyone experienced this situation or knows how I can resolve this issue?

If you need more information, I’m happy to provide it. Thanks in advance for your help!

Information on your n8n setup

  • n8n version: 1.58.2
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker Swarm
  • Operating system: Debian 12
2

Hey @raylsonsantos,

Welcome to the community :tada:

Clickup looks to be a webhook based node so Clickup gets configured to post data to n8n as the events happen.

Once your workflow is active do you see the webhook url registered in Clickup at all? If you are using webhook workers it could be that your load balancer has not been configured correclty any /webhook-test/ URL needs to go to the editor instance and anything with /webhook/ needs to go to the webhook workers.

3

Hello Jon,

Thank you for your response and the warm welcome!

I have already set up ClickUp to post data to n8n, and the webhook URLs are correctly registered in ClickUp. I’ve also ensured that the load balancer is configured according to the guidelines: /webhook-test/ is directed to the editor instance, and /webhook/ is going to the webhook workers.

Despite this setup, the ClickUp trigger is still not pulling new tasks as expected. Other triggers and workflows in n8n are functioning correctly, so the issue seems isolated to this ClickUp trigger.

Would you have any additional recommendations on what else I could check or configure to resolve this issue?

Thanks again for your help!

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.