Cannot activate duplicated nodes with preset webhook URLs - defeats the whole point of duplicating?

Describe the issue/error/question

Why is it when I duplicate nodes with webhook urls, I cannot use them in my workflow?
For example, when I duplicate (or control-c control-v) nodes from the Bitbucket trigger, Slack Trigger, Jira Trigger, and ActiveCampaign trigger - all of the values get copy pasted as intended, but the preset webhook url (which I do not and can not set myself) gets copied as well, meaning I have to remove the node from my workflow entirely or delete the previous one before I can activate my workflow?
Related is this: when click duplicate workflow the webhook duplicated with same url · Issue #2386 · n8n-io/n8n · GitHub
Although I appreciate the fine work that has gone into this application and the community behind it, this is honestly a blocker for my team and I to continue using this application, manually copying near-identical values is a huge time sink for some of these nodes, and the WHOLE POINT of duplicating nodes is to avoid this very issue. Why even have the duplicate node button present in the first place for nodes like this if they cannot be used?

Is there some way to get around this without changing values manually in the API, or copy pasting nodes into a text editor, and manually changing the autogenerated webhook URL, and pasting it back in? Is there some sort of hidden option or button to be able to refresh the webhook URL so I can actually use duplicated nodes? Is there some way to modify the premade nodes themselves without having to rebuild the entire application (be able to use the public docker image)?

What is the error message (if any)?

Workflow could not be activated:

The URL path that the "ActiveCampaign Trigger1" node uses is already taken. Please change it to something else. 

Please share the workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database you’re using (default: SQLite):
  • Running n8n with the execution process [own(default), main]:
  • Running n8n via [Docker, npm,, desktop app]:

Hi @andrewatcbs, welcome to the community :tada:

You’re not wrong, this can be annoying but as you’ve on the GitHub issue you have linked it’s currently the expected behaviour.

Perhaps you want to vote on this feature request suggesting to randomize the URLs upon request (and maybe also leave a comment suggesting to extend this feature to copies)?