I use this template to sync Zendesk tickets to Jira issues. It works for “create Jira issue” flow. For “update with new comments on existing Jira issue” flow, it returns an error message “The resource you are requesting could not be found. Issue does not exist or you do not have permission to see it.” as below image.
Hope to receive help from the community!
It looks like your topic is missing some important information. Could you provide the following if applicable.
Hi @Tien_Nguyen
Thanks for posting here and welcome to the community! 
I tried to replicate your issue but it is working fine for me.
Can you share your workflow and also which version of n8n you are using?
It could be that you are referencing the wrong key in the Jira node.
See my setup:
My current plan does not allow to share workflow. The version I am using is 1.50.1
The key is match with Jira ticket need to sync comment from Zendesk but it does not work.
Hey @Tien_Nguyen,
Any n8n user can share a worklfow by exporting or copying / pasting, The sharing feature is for sharing a worklfow with a user in the instance of n8n.
Here is my workflow
Hi @ria , above is the my attached workflow for your reference. Hope to receive your support for the “update with new comments on existing Jira issue” flow.
Hey @Tien_Nguyen,
In the workflow you have shared the Create comment to existing issue node is not using an expression although from your screenshot you was using it.
Looking at the error Jira is saying that the issue either doesn’t exist or the account you are using doesn’t have access to it. Have you made sure that your user does have access to it?
Does the path to create a new issue work?
Hi @Jon I haven’t noticed any differences in the configuration of my shared workflow compared to the attached email in the previous comments on this topic. For your reference, I’ve reattached the below image of configuration for my current workflow for the “Create Comment to Existing Issue” node.
As you can see in my shared workflow, I use the “IF” node to check whether the Jira issue exists. If it doesn’t exist, the “Create New Jira Ticket” node will execute; otherwise, the “Create Comment to Existing Issue” node will run.
As I mentioned in my first comment, the “Create New Jira Ticket” node is still functioning normally. Therefore, I believe the issue may be related to the configuration of the “Create Comment to Existing Issue” node.
Hi @Tien_Nguyen
I could not recreate the issue either. This might be related to your code node.
Can you try to reference the issue directly from the If node instead of from the Code node?
So instead of {{$node["Determine"].json["Jira issue key"]}} for your Issue Key → {{ $json["Jira issue key"]}}
Hi @ria, it’s working now! The issue wasn’t with the node code, but rather with the configuration of my Zendesk trigger.
I do have a quick question: the comment is currently added with the template shown in the image below. Is there any way we can configure it to remove the “--------------” line and the space that follows, only display the “comment”?
Hi @Tien_Nguyen
happy to hear you figured it out! 
This also seems to be coming from your Zendesk Ticket - You can fix that using the builtin replaceAll() method in your Comment field in the Jira Node:
{{ $node["On updated Zendesk ticket"].json["body"]["comment"].replaceAll("-","") }}
Hope that works! 
Thanks @ria.
I have one final question regarding this workflow. I set up a trigger in Zendesk to run the above workflow every time a Zendesk ticket is updated (not created). When a Zendesk ticket is created, the agent responds with a private or public comment, then the workflow will run to create a Jira ticket. However, the comment added in Zendesk is not added to the newly created Jira ticket. Is there a way to create a Jira ticket and add the corresponding comment at the same time, rather than having to add the comment after the Jira ticket is created?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.