Huge Issues with Discord Integration

10 Comentarios

  • Andrew Wiik

    Hi Sam, I fixed the issue last night but they stil have broken the reply though zendesk, if you wanna contact me on and of my social media or through some anonymous chatroom I would be more than willing to walk you through the fix. @andywiik on twitter or you can just join this discord and I'll DM you: https://discord.gg/eJURpV

    0
  • Andrew Wiik

    The Tl;DR for the actual integration developer's is you broke the bot automatically setting the local token and domain values from the auth response when the bot is added so they values are left at the defaults of the domain being "zendesk" and the token being "123456". also when you set the domain you only need to enter your subdomain portion not the fully qualified domain name if you're going to fix this problem manually with the /set command. You will need to use chrome network logger to grab the token from a URL param that you need to set at the token variable.

    0
  • Andrew Wiik

    You also broke the bot sending zendesk messages back by making authentication fail on the post URL but that's a diff thing. I spent way too long looking into this last night.

    0
  • Andrew Wiik

    nvm they apparently broke it even more 45 minutes ago.

    0
  • Sam

    The general experience so far has been awfully mixed. 

    0
  • Andrew Wiik

    I love how the discord bot has the role [PROD] but they have restarted it at least 3 times since I started it using it about a day ago.

    0
  • David Hall
    Zendesk Product Manager

    Hi Andrew & Sam,

    Apologies for the rough start you've both had with trying out the integration.  Please bear with us for a little longer, our developers believe they've located the cause of these intermittent failures and are working on a fix.  We expect to have that deployed shortly.

    0
  • Sam

    I've had this integeration running for a few months, but as of recent it entirely stopped working. Every customer in my Discord server trying to open a ticket would get that error, so we have now had to entirely suspend the bot and use an email support operation, which is not the preferred medium for my customers. 

    0
  • David Hall
    Zendesk Product Manager

    Hi Sam, we've made an update to the integration which we believe will fix this issue.  Could you please try the bot again, and let us know whether it's working for you now?

    0
  • Sam

    Still no luck. It's setting them to 'zendesk' and '123456'.

    I can change the domain I just have no clue how to get the token.

     

    0

Iniciar sesión para dejar un comentario.

Tecnología de Zendesk