Feature Requests

Please search first before posting to help others find and vote for your idea!
n8n integration breaks and Clickup API needs adjustments
I’m experiencing a critical issue with the ClickUp Trigger node in n8n that prevents me from activating workflows reliably. Problem: The ClickUp Trigger works correctly for the first 2-3 test executions, but then consistently fails with the error: Problem running workflow Bad request - Webhook configuration already exists Steps to reproduce: 1. Create a new ClickUp Trigger node with event “task.updated” and List ID filter 2. Configure trigger with Team ID and credentials 3. Execute workflow 2-3 times successfully 4. On subsequent executions or when trying to activate the workflow, the error appears 5. The workflow cannot be activated or used anymore What I’ve tried: • ClickUp App Authentication: Created a dedicated ClickUp OAuth app and connected through the app credentials - same issue occurs • API Key Authentication: Deleted all app connections and used direct API key authentication - same issue persists • Manual webhook cleanup: Deleted all webhooks from ClickUp Settings → Integrations → Webhooks section • Node recreation: Completely deleted and recreated the ClickUp Trigger node multiple times • Workflow deactivation: Deactivated workflow, waited, cleaned webhooks, reactivated - issue returns after 2-3 executions Expected behavior: The ClickUp Trigger should create and manage webhooks reliably without duplication errors, allowing workflows to remain active indefinitely. Actual behavior: After 2-3 successful test executions, n8n attempts to register a webhook that ClickUp reports as already existing, even though: • No duplicate webhooks are visible in ClickUp UI • All webhooks have been manually deleted • Using fresh API credentials
0
Load More