Converting HTTP targets to webhooks

Return to top

99 Comments

  • Andrew Schreiner

    Are stored usernames and passwords carried over in the migration? 

    0
  • Acenerate

    Hi @... -

    Any word yet on the progress of including the webhooks in app requirements?  We are in a real bind here, as this is an important piece to making some apps work.  There is a big difference from a security standpoint (not to mention coding effort) to create the webhooks programmatically as opposed to including them in the app requirements, and we simply can't continue with the existing "targets" knowing that they are being deprecated.  

    Thank you for your continued support!

    0
  • Chris Sos
    Zendesk Product Manager

    Hi @...,

    Thanks for the message. We totally understand how this uncertainty can affect your app development underway.

    We are making progress and it's being worked on as I type this. I don't have an ETA I can share at this time, but I hope I'll be able to update on this very soon!

    Chris

    0
  • Acenerate

    Thank you @...!

    0
  • Peter Hochstrasser

    Just FYI to all followers of this thread:

    Apparently, the parameterizable URLs have been added to Zendesk; I just converted all my targets which used URL parameters to webhooks.

    All worked without a hitch, and without the need to change anything manually.

    Thanks, Zendesk!

    1
  • Jacob Kjeldahl

    Hi @...

    Any news regarding webhooks in app requirements?

    /Jacob

    0
  • Khajik Khajadourian

    Any update on allowing placeholders/URLs in webhooks so we can finish our conversion? 

    0
  • Chris Sos
    Zendesk Product Manager

    Hi @...

    Placeholders in URLs are now supported. You should be able to proceed with the conversion without issue :)

    Hi @...,

    This work is still continuing. I don't have any specific news yet on this front.

    Chris

    0
  • Kevin Lewis

     So, the only targets I have are Salesforce Integrations. When I navigate to the web hooks area, nothing shows up for the "Get Started" area. Does this mean my targets cannot be converted?

    0
  • Jacquelyn Brewer

    Kevin Lewis this migration and deprecation only applies to HTTP targets. Targets created from Zendesk Integrations aren't being migrated or deprecated at this time. For more information, see the announcement.

    0
  • Rich Lorenzo | priclor | Ricardo Navarete

    I converted my targets to webhooks today. The process went smoothly and everything looks to be setup correctly and functioning normally.

    However, I've noticed in the ticket events log it no longer shows me the name and link to the trigger where the webhook was called but rather says WebhookEvent (not implemented) for that event instead.

    I don't think I saw any comments about this above and no mention in the article. What's going on with this? Is this telling me that the functionality to tell me which trigger called the Webhook is not yet implemented?

    Edit: I've tried this out on a completely second Zendesk instance with the same result so I can only assume that this is happening across the board. Here is a screenshot to better illustrate:

    5
  • David Chiu

    After clicking on "Convert Targets", I get an error saying "Internal Server Error. Something is wrong". Has anyone seen this and know how to fix it? Thank you!

    0
  • Mark Leci

    We have only 1 active target that I think needs to be converted, it's a URL target not associated with any app. I wasn't able to convert it before, I assumed because it uses placeholders. When I start the conversion process, I get the message 'You have 0 active targets ready to convert now or later.' Why can I still not convert this target? 

    0
  • Jacquelyn Brewer

    Mark Leci The migration is currently only for HTTP targets. URL targets aren't being deprecated or migrated at this time.

    0
  • Virginia Goggins

    Do we have an update on converting HTTP targets that use placeholders?  I've been watching for an announcement but haven't seen one yet. 

    0
  • Chris Sos
    Zendesk Product Manager

    Virginia Goggins placeholders are now supported. We have removed reference to placeholders from the documentation around reasons that conversion may be skipped. These targets will no longer be skipped for conversion.

    0
  • Colin Sheppard

    Under the section "Preparing HTTP targets to be converted" it mentions "Find the target in the list and click Edit.". I cannot find the edit button for my Slack Integration.
    I understand that targets created via apps requirements, like Zendesk's Slack integration, are not yet eligible for migration. I am surprised that an app as popular as Slack cannot yet be migrated. When will Zendesk's Slack app be eligible for migration? 

    0
  • Peter Hochstrasser

    I converted my HTTP targets with URL parameters a while ago - all worked well.

    If it wouldn‘t work, it would tell you so and leave all in place - so why not just try?

    0
  • Julio Hernandez
    Zendesk Customer Care
    Hi Kevin,

    As mentioned from the announcement post About converting targets to webhooks Targets created from Zendesk integrations (e.g Slack and Jira) will be converted at a later date: 

    What about targets created from Zendesk integrations? 
      
    At this time, only HTTP targets are being deprecated and converted to webhooks. Targets created from Zendesk integrations will be converted at a later date. Right now they are excluded from the conversion process. 
    ---------

    In regard to Placeholders in the URLs, please see this comment: Placeholders in URLs are now supported 

    I hope this information helps!

    Julio H | Technical Support Specialist | Zendesk EMEA

    Enjoy Free Zendesk Training

    0
  • Colin Sheppard

    HI Julio Hernandez

    I believe I fall into the category that you described in your previous comment. As you can see I have one Slack integration, which I am unable to convert.

     

    So I am confused as to why I received this email:

    Was that email sent in error? or do I need to convert my Slack integration?

    0
  • Colin Sheppard

    Hi Chris Sos, or maybe Julio Hernandez,

    Any update on my question above?

    This Zendesk/Slack integration is integral to my day to day work, any help on this would be greatly appreciated.

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Colin Sheppard,

    For integrations such as Zendesk's Slack integration no action is required on your part and you will not lose access to this integration. We are working with our integrations partners on this, but rest assured we will not cut of any access to existing integrations as part of this work.

    We are tweaking who will receive future communications to avoid confusion over this since there is no action required.

    Hope this helps.

    Chris

    1
  • Tanawat Oonwattana

    I am seeing the same logs in ticket events as Rich Lorenzo | priclor | Ricardo Navarete >> WebhookEvent (not implemented).

    Not sure if anyone finds the same behavior?

    1
  • Walter

    Tanawat Oonwattana

    I see it too, but it does not seem to prevent our webhooks from executing.

    Everything seems to be working fine for us.

    0
  • Tanawat Oonwattana

    Walter, same here.

    I am just wondering if this log behavior is not considered as high priority to be fixed cause only admins can see it or what.

    1
  • Rich Lorenzo | priclor | Ricardo Navarete

    Tanawat Oonwattana @ walter_

    This was never acknowledged as a bug or still in development here but this appears to be resolved on my Zendesk instance.

    Conversation events on tickets very recently (I think maybe on Friday?) started showing the link to the Trigger where the webhook was called. Maybe this is a phased roll out? Not sure because Zendesk hasn't commented on it here but I'm just glad it seems to be sorted for me. Good luck!

     

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Tanawat Oonwattana, Walter Rich Lorenzo | priclor | Ricardo Navarete,

    This is a bug that we are actively working on a fix for. For non Agent Workspace accounts this fix is out and the "Not Implemented" message has been replaced with the same message that appeared for Targets.

    For Agent Workspace accounts (where there is currently nothing shown), a fix is coming very soon here.

    Hope this helps clear this up!

    Chris

    0
  • Drago Markov

    Hello, 
    Could you please confirm if URL targets and HTTPS targets will be affected by this change? 
    Thanks in advance!

    0
  • Jacquelyn Brewer

    Drago Markov The migration is currently only for HTTP targets. URL targets aren't being deprecated or migrated at this time, though you can manually recreate your URL targets as webhooks if you'd like.

    0
  • Emilie Duveau

    Hello,
    I have the same error David Chiu had: after clicking on "Convert Targets" or while testing the creation of a new webhoook, I get the error "Internal Server Error. Something is wrong".
    I use the same data as our current HTTP targets, that are not in error.
    Does anyone know what I am missing?
    Thank you.

    0

Please sign in to leave a comment.

Powered by Zendesk