Trigger + Webhook: Send multi-select custom ticket field to a different ticket (multiple values issue) | Community
Skip to main content

Trigger + Webhook: Send multi-select custom ticket field to a different ticket (multiple values issue)

  • February 9, 2026
  • 3 replies
  • 0 views

Arda

Hi everyone,

 

I’m trying to send the selected values of a multi-select custom ticket field from one ticket to a different ticket using Zendesk triggers and webhooks.

 

Setup:

  • Trigger: fires when the source ticket is updated
  • Action: Notify active webhook
  • The webhook updates the target ticket using the Zendesk Tickets API
  • Webhook is created and tested successfully.

This is the JSON.

 

{
 "ticket": {
   "custom_fields": [
     {
       "id": 33766991659677,
       "value": ["{{ticket.ticket_field_33766991659677}}"]
     }
   ]
 }
}

 

Problem:

When only one value is selected in the multi-select field on the source ticket, everything works correctly and the target ticket receives the value.

However, when multiple values are selected in the multi-select field, the trigger runs but the multi-select field on the target ticket becomes empty, instead of being updated with all selected values.

 

I couldn’t get this to work as expected when multiple values are selected.

  • Is there any Zendesk-native way (Triggers + Webhooks only) to send all selected values of a multi-select field to another ticket?
  • Or is there a known limitation / recommended workaround for this scenario?

Thanks in advance.

3 replies

Jacob20
  • February 10, 2026

Hey @arda 👋

 

I remember having been in the same situation as you, and I'm not sure I was able to resolve it at that time. 

 

I believe the issue is that the placeholder for a multiselect value is not outputting something JSON-valid - you should be able to see in the Webhook activity log what the output looks like.

Perhaps some liquid markup can clean up the placeholder and insert commas in the right places.


Arda
  • Author
  • February 11, 2026

Hi Jacob,

Thank you for your time and for your reply.

 

While my post was under review, I was able to find the solution and got it working as expected. 

The issue was indeed caused by a JSON parsing error. Multi-select values need to be sent using Liquid markup. After a few attempts, I found the correct format for my case.

Thanks again for your support.


Jacob20
  • February 13, 2026

That's awesome, well done @arda !
Would you mind sharing your solution? Future me might need that 😁