Pesquisas recentes
Sem pesquisas recentes

Lachlan Kidson
Entrou em 04 de jun. de 2024
·
Última atividade em 01 de jul. de 2024
Seguindo
0
Seguidores
0
Atividade total
8
Votos
2
Assinatura
1
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 Lachlan Kidson
Lachlan Kidson comentou,
Hey Erica, no worries at all!
A demo would be appreciated if you have the time, thanks.
Exibir comentário · Publicado 01 de jul. de 2024 · Lachlan Kidson
0
Seguidores
0
Votos
0
Comentários
Lachlan Kidson comentou,
Thanks Erica, do you know if there are any examples of this anywhere? Our attempts resulted in getting a 500 error back from the server. It's not too clear how to express that the payload is multipart/form-data when using request()
Exibir comentário · Publicado 28 de jun. de 2024 · Lachlan Kidson
0
Seguidores
0
Votos
0
Comentários
Lachlan Kidson comentou,
Having looked at this a bit further it seems like the expected approach is to upload an attachment via
https://developer.zendesk.com/api-reference/ticketing/side_conversation/side_conversation_attachment/, retrieve the UUID from the response - and then use this in the payload for creating the side conversation.
Is it possible to perform the upload via ZAFClient's request method?
Exibir comentário · Publicado 20 de jun. de 2024 · Lachlan Kidson
0
Seguidores
0
Votos
0
Comentários
Lachlan Kidson comentou,
On a similar note, it doesn't look like the CC or BCC fields are available via this API either, whilst they are available via the UI.
Exibir comentário · Publicado 11 de jun. de 2024 · Lachlan Kidson
0
Seguidores
0
Votos
0
Comentários
Lachlan Kidson criou uma publicação,
I am part of a team developing an application installed to the ticket_sidebar
location. As part of this we want to be able to programatically create side conversations for our users.
We've had success doing by calling the side conversations API via ZAFClient
:
Our code is essentially this, which works:
const { 'ticket.id': id } = (await client.get(
'ticket.id',
));
const message = {
"message": {
"subject": "My printer is on fire!",
"body": "The smoke is very colorful.",
"to": [
{ "email": "someone@example.com" }
],
}
};
await client.request({
contentType: 'application/json',
url: `/api/v2/tickets/${id}/side_conversations`,
type: 'POST',
data: JSON.stringify(message),
dataType: 'json',
})
We would also like the ability to add attachments. This is where we run into issues.
The example code from the documentation would suggest this is possible:
{
"message": {
"subject": "My printer is on fire!",
"body": "The smoke is very colorful.",
"to": [
{ "email": "someone@example.com" }
],
"attachment_ids": ["0123456789"]
},
However the attachment_ids
field is not documented on the associated Message
object, and in testing always results in an error that the attachment was not found.
Our expectation was that we could get a list of attachments by first making a request to /api/v2/tickets/${id}/comments.json
, then use the attachment IDs from that as part of the message payload. (We've also confirmed work with the api/v2/attachments/
endpoint). Inspecting the GraphQL network requests that are made when creating a side conversation via the UI also results in the same attachment IDs being used - so it is unclear why these attachments aren't being found.
TL;DR - is the attachment_ids
field actually supported in the side conversations API, and if so what do we need to do to get this to work?
Publicado 10 de jun. de 2024 · Lachlan Kidson
1
Seguidor
5
Votos
8
Comentários