Pesquisas recentes
Sem pesquisas recentes

Junsheng Wu
Entrou em 01 de fev. de 2023
·
Última atividade em 12 de fev. de 2023
Seguindo
0
Seguidores
0
Atividade total
9
Votos
1
Assinaturas
2
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Junsheng Wu
Junsheng Wu comentou,
Thank you so much Ahmed Zaid. That works as I expect.
Exibir comentário · Publicado 12 de fev. de 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentários
Junsheng Wu criou uma publicação,
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 de fev. de 2023 · Junsheng Wu
0
Seguidores
4
Votos
2
Comentários
Junsheng Wu comentou,
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
Exibir comentário · Publicado 02 de fev. de 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentários
Junsheng Wu comentou,
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" |
Exibir comentário · Publicado 02 de fev. de 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentários
Junsheng Wu comentou,
It doesn't work even if I added `any`:
Exibir comentário · Publicado 02 de fev. de 2023 · Junsheng Wu
0
Seguidores
0
Votos
0
Comentários
Junsheng Wu criou uma publicação,
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 de fev. de 2023 · Junsheng Wu
0
Seguidores
2
Votos
6
Comentários