최근 검색


최근 검색 없음

Jonathan Farache's Avatar

Jonathan Farache

가입한 날짜: 2022년 1월 03일

·

마지막 활동: 2023년 3월 21일

팔로잉

0

팔로워

0

총 활동 수

8

투표 수

0

플랜 수

3

활동 개요

님의 최근 활동 Jonathan Farache

Jonathan Farache님이 에 댓글을 입력함

댓글Getting started with messaging

Anne Ronalter is there a resource that goes over migration between the different API clients?

With live chat we had the zE object to show/hide the chat widget as well as listen/respond to certain events. What's the equivalent in zendesk messaging? What's the best practice for migrating from one to the other?

댓글 보기 · 2023년 3월 21일에 게시됨 · Jonathan Farache

0

팔로워

0

투표 수

0

댓글


Jonathan Farache님이 에 댓글을 입력함

댓글Live chat agent guide

can we see an example of how this works with the `zE("...")` API? 

unclear from the docs here how to send structured messages with zE

댓글 보기 · 2022년 8월 16일에 게시됨 · Jonathan Farache

0

팔로워

0

투표 수

0

댓글


Jonathan Farache님이 에 댓글을 입력함

커뮤니티 댓글 Developer - Zendesk APIs

Thanks for the reply Eric Nelson

I should have clarified: we already have a webhook setup. It sends data to an AWS SQS, and from there our app grabs each message as it comes in. The problem is that sometimes AWS goes down, and then we lose some data until it's back up. In those instances, I need to re-sync my data.

You might say "well why don't you connect the webhook directly to the app" - that's not possible for both security reasons, but also the fact that the app itself might go down and then we're in the same issue - hence the need to occasionally re-sync.

댓글 보기 · 2022년 1월 05일에 편집됨 · Jonathan Farache

0

팔로워

0

투표 수

0

댓글


Jonathan Farache님이 에 댓글을 입력함

커뮤니티 댓글 Developer - Zendesk APIs

yes Eric Nelson, i was thinking of implementing a process that runs every 5 minutes and validates the the tickets in my DB from the last hour are synced with tickets in ZD. That would easily be hundreds of tickets every 5 minutes

but with this amount of network traffic it seams unfeasible

댓글 보기 · 2022년 1월 04일에 게시됨 · Jonathan Farache

0

팔로워

0

투표 수

0

댓글


Jonathan Farache님이 에 게시물을 만듦

게시물 Developer - Zendesk APIs

Currently when you make a request for ticket data, you get all the data for that ticket back. So if I asked for data about 100 tickets, I could potentially get 100,000 lines of JSON because it includes all the custom_fields (which can be a lot per ticket) - this is a huge amount of data to return (i.e. useless network traffic) for 100 tickets when all I want is the ticket status and priority for each ticket.

 

I was advised by customer support that such a feature does not exist - could we make this happen?

2022년 1월 03일에 게시됨 · Jonathan Farache

1

팔로워

4

투표 수

7

댓글