Just to understand you correctly you are saying the displayed error can not be correct? Because if you see that error, then it is what the Jira API returned to n8n and should then normally the exact reason
Yes, exactly. That is what the Webhook-Node does when a workflow gets activated. To be exact it does actually do two things:
It checks if a webhook already exists
If it does not exist yet it will create one
So theoretically each could cause this problem.
But to be honest, I have not much knowledge about how API credentials work at Jira and how fine-grained they are. It is not uncommon that APIs send very strange responses that say X but actually Y is the problem. That is why I was asking if you are sure that the reported error can not be true.
Already check with my jira admin. Confirm that I don’t have access to create webhook in jira.
After I change my credential to jira credential that has access to create webhook, Jira Trigger works perfectly.
@jan maybe the documentation about Jira Trigger credential need to add this information