Búsquedas recientes
No hay búsquedas recientes

Junsheng Wu
Incorporación 01 feb 2023
·
Última actividad 12 feb 2023
Seguimientos
0
Seguidores
0
Actividad total
9
Voto
1
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Junsheng Wu
Junsheng Wu hizo un comentario,
Thank you so much Ahmed Zaid. That works as I expect.
Ver comentario · Publicado 12 feb 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentarios
Junsheng Wu creó una publicación,
Hi Zendesk Support,
When we are calling Zendesk API to interact with our system:
- When our end-user sends comment to our system, our system call Zendesk API to create Zendesk ticket or add new comment to an existing Zendesk ticket;
- The Support representative will view the comment on Zendesk platform and add comment via UI to response.
My question is: how do we know which comment were added by end-user, which comment were added by Support representative?
I know by click `Events` on the ticket page we can see the difference; however, the `Events` are invisible by default. What is the better way to distinguish both sources?
Here is the link to view the ticket snapshot that I captured from Zendesk platform:
https://docs.google.com/document/d/1-zefsCGOgFIfr7kmW8Kx0BrUJwsq9GWgLO30_XOro6w/edit
(It seems image upload does not function when creating the post.)
Thanks,
Junsheng from Wunderkind
Editado 10 feb 2023 · Junsheng Wu
0
Seguidores
4
Votos
2
Comentarios
Junsheng Wu hizo un comentario,
Thank you Jack. Yes, you are right. It works after wrapping with "trigger" node. In the meanwhile, I found a issue when creating a trigger with this condition:
{
"field":"current_via_id",
"operator":"is",
"value":0
}
After creation, the UI shows:
It suppose to be:
But anyway, this condition works as expected just a UI issue I guess.
Junsheng
Ver comentario · Publicado 02 feb 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentarios
Junsheng Wu hizo un comentario,
Thank you for reply, but I don't think that's the reason since I tested by following json with operator in the condition, it did not work:
{"title":"Test trigger","active":true,"conditions":{"all":[{"field":"current_tags","value":"wunderkind","operator":"includes"}]},"actions":[{"field":"notification_webhook","value":["abc","123"]}]}
update_type | Omit the operator property |
"Create" or "Change" |
comment_is_public | Omit the operator property |
true, false, "not_relevant" (present), or "requester_can_see_comment" (present and requester can see comment) |
ticket_is_public | Omit the operator property |
"public", "private" |
Ver comentario · Publicado 02 feb 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentarios
Junsheng Wu hizo un comentario,
It doesn't work even if I added `any`:
Ver comentario · Publicado 02 feb 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentarios
Junsheng Wu creó una publicación,
I am following this instruction to create a trigger by calling this endpoint:
POST https://wunderkindtest.zendesk.com/api/v2/triggers
The request body:
{"title":"Test trigger","active":true,"conditions":{"all":[{"field":"comment_is_public","value":true},{"field":"update_type","value":"Change"}]},"actions":[{"field":"notification_webhook","value":["abc","123"]}]}
{"error": "RecordInvalid","description": "Record validation errors","details": {"base": [{"description": "Invalid conditions. You must select at least one condition."}]}}May I know what's wrong on my request body? How should I correct it? Thanks,Junsheng
Publicado 01 feb 2023 · Junsheng Wu
0
Seguidores
2
Votos
6
Comentarios