I’m building a workflow that creates Jira tickets from Zendesk data.
Scenario:
-
If I only set the description (pulled from Zendesk) and other basic fields, the Jira ticket is created successfully.
-
The problem occurs when I add conditional logic to set both the assignee and a custom field based on a specific Zendesk ticket field value.
-
Additionally, after creating the ticket, I want to update its status in a separate Jira node — but this also fails when conditions are applied.
Flow:
-
Zendesk Trigger → Retrieve ticket data.
-
Jira node → Create issue.
-
Check the Zendesk ticket field value.
-
If matched, set
assignee= Jira accountId and set a specific custom field value. -
If not matched, leave
assigneeand custom field unset.
-
-
Jira node (Update Issue) → Change the ticket status (e.g., from “To Do” to “In Progress”).
Expected:
-
If the condition is matched, assign the ticket, set the custom field, then update status in Jira.
-
If the condition is not matched, just create the ticket without those fields, and still update status.
Actual results:
-
Create Issue node error: ERROR: Assignee parameter’s value is invalid. This is likely because the URL entered is incorrect.
-
Update Issue node error: ERROR: Status parameter’s value is invalid. This is likely because the URL entered is incorrect.
Note:
The status update fails only in cases where the ticket creation step includes conditional assignee and custom field mapping. If those conditions are removed, Create step work fine.
Question:
-
How should I structure the Jira node output so that Jira only receives
assignee, custom field, and status update parameters when they’re valid? -
Is there a recommended way in n8n to skip empty/undefined fields before sending to Jira to avoid these validation errors?
Attached is the workflow I built where I encountered the issue.
Thanks in advance for your help!