Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

Ryan Nally's Avatar

Ryan Nally

Beigetreten 28. Dez. 2023

·

Letzte Aktivität 22. Juli 2024

Folge ich

0

Follower

0

Gesamtaktivitäten

9

Stimmen

0

Abonnements

5

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von Ryan Nally

Ryan Nally hat einen Kommentar hinterlassen

KommentarEnd users and organizations

How do I populate user fields from my BE? I'm using the users/create_or_update call and send a request body that has user_fields object but it doesn't seem to update these fields on the user profile and they come back null.  I then updated these fields on the user profile and now when I inspect that call I see that value reflected.  So it seems that the call I make reads the values from the user profile instead of populating them.  Please advise.

Kommentar anzeigen · Gepostet 22. Juli 2024 · Ryan Nally

0

Follower

0

Stimmen

0

Kommentare


Ryan Nally hat einen Kommentar hinterlassen

KommentarWeb Widget documentation

Hey Thomas, What do mean by adding that code snippet to the Help Centers's head.  How are you doing this?  Form what I'm seeing, my company has setup and managed the help center all from the zendesk UI.  It is completely separate from our application's codebase. 

Kommentar anzeigen · Gepostet 18. März 2024 · Ryan Nally

0

Follower

0

Stimmen

0

Kommentare


Ryan Nally hat einen Kommentar hinterlassen

KommentarUsing legacy AI agent functionality

In our app we've implemented a JWT using signing key and the login method outline in the sdk doc.  I can see this call returning with a 200 status. Yet in our chatbot flow the Authenticated Status is not equating to true.  Any suggestions on why this might be the case?

Kommentar anzeigen · Gepostet 05. März 2024 · Ryan Nally

0

Follower

0

Stimmen

0

Kommentare


Ryan Nally hat einen Kommentar hinterlassen

KommentarMigrating to messaging

I'm running into a caching issue when enabling Messenger. Here is the flow: Classic web widget is being used. the zendesk snippet is cached.  I enable Messenger and merge code to use the Messenger API. A user goes on to my app but the snippet is pulled from the cache and this cached version used the classic web widget not the messenger.  My console complains about trying to use functions that don't exist (ie. Messenger functions against the classic web widget).  This causes issues around authenticating end users, etc.

I've tried busting the cache by appending a timestamp as a query param to the Zendesk snippet but this doesn't work.  

For those who have made the switch from classic web-widget to Messenger how have you handled this issue?

Kommentar anzeigen · Gepostet 28. Dez. 2023 · Ryan Nally

0

Follower

0

Stimmen

0

Kommentare