Announcing the deprecation of HTTP targets and conversion to webhooks

Return to top

32 Comments

  • Alan Byrne

    This specifically talks about the deprecation of HTTP targets.  Are URL targets going to be similarly affected?  I know it says only HTTP targets will be affected bu I just wanted to be sure.

    4
  • HENDRICKX, STEVE

    Are there any plans to allow us to customize the static "retry" logic?   With Targets it would never retry,  and it seems now with Webhooks is it will Retry Unconditionally up to 4 times.  

    This change in default behavior will require us to rework dozens of integrations we have currently built out.

    4
  • HENDRICKX, STEVE

    Webhook requests that time out are retried up to five times. Consecutive failed requests won't deactivate the webhook.

    We cant control these as we dont control the response.

    For me its specifically this,  since Zendesk only waits a second or two for a successful response,  we have some integrations that occasionally take slightly longer than that to complete.    Today we are okay with the current logic,  even though ZD receives a Timeout Response,  our system handles that request accordingly and finishes running.  

    With being forced over to your new Webhooks,  this would cause duplicate jobs being sent and ran until we are able to refactor our integrations to be 100% async or have an effective method to filter out duplicate requests.

    We would prefer to never have a timeout retry, or perhaps Zendesk could include something specific in the Headers that would indicate when a retry attempt is being made.

    2
  • Alex Soto

    And my team too...retry logic has me concerned. 

    2
  • Kyle Pinkley

    ^ This is going to be an issue for us as well. 

    2
  • Chris Sos
    Zendesk Product Manager

    Hi Arnaud Héritier,

    URL targets are out of scope for now. This may change in future as URL targets are also legacy and can be superceded by webhooks for nearly all use-cases.

    A converter is not possible due to the intricacies of URL targets (specifically the "attribute" naming and usage). We would highly recommend investigating moving off URL targets in favour of webhooks for any customer.

    Chris

    1
  • Peter Hochstrasser

    Hey @...

    Will webhooks eventually support parameterized URLs as in https://xxx.zendesk.com/api/v2/tickets/{{ticket.id}}.json?

    IOW, will they offer functional parity to HTTP targets with a JSON payload, or will there be restrictions?

    Yours truly

    Peter

     

    1
  • Jacquelyn Brewer
    Zendesk Documentation Team

    Jalerson Lima, the automated migration and deprecation process begins February 22, 2022. It will take some time to perform the migration for all accounts, so it's impossible to give a precise date on which any given account will have that process completed. Please be prepared for deprecation by February 22.

    1
  • Chris Sos
    Zendesk Product Manager

    We've made some updates to the scope of this announcement that we'd like to highlight:

    • We'll now have an automated conversion process for HTTP targets created by the following Zendesk integrations: Jira, Salesforce, Hubspot, and Discord.
    • HTTP targets created by existing installed private apps and apps installed from the Zendesk Marketplace will be converted to webhooks.
    • New and updated marketplace apps will fail validation if their requirements include HTTP targets. Similarly, private apps uploaded after the deprecation date will fail validation if they contain HTTP targets in their requirements.json file.
    1
  • Chris Sos
    Zendesk Product Manager

    Hi Anton Maslov,

    Placeholder support was released in late September for webhooks :)

    Chris

    1
  • Sandro Olivieri

    Hi,
    Can you confirm that Placeholder support was released for webhooks?
    Extensions with placeholder in format "/api/v2/tickets/{{ticket.id}}" are not recognized from automatic convertion tool in Admin Center.
    Sandro

    0
  • Greg Katechis
    Zendesk Developer Advocacy

    Hi Jose! There are a couple of ways that you could accomplish this depending on what you were specifically looking for. Before I get into those methods, I do want to point out that when the target is converted, the name and content of the previously active target will be the same as the webhook.

    I'm awaiting confirmation on this, but as far as I can tell, the conversion_id of the webhook is the same as the previous target's id. So if you need to reference that, you can do so in the UI by following these instructions. There is also an undocumented (and thus unsupported as of now!) API that will return a target_id object that is the same as the trigger's original id: https://{{subdomain}}.zendesk.com/api/v2/targets_migrator/

    Once I confirm this or find other options, I will drop an update in here!

    0
  • Nkem Nwankwo

    Zach Anthony

    Thanks for the info. We have some current instances of private apps and there's a possibility of new private app instances being connected.

     

    To confirm, are you saying that (1) there's nothing to do for existing app instances because those will be converted to webhooks automatically, and (2) there's nothing to do (right now) for future connections because the support isn't available yet?

    0
  • Zach Anthony
    Zendesk Product Manager

    Hi Nkem Nwankwo

    That's correct. No action is required for HTTP targets created by existing installations of apps as those HTTP targets will be converted to webhooks automatically by us and for new installation of apps there is no action required right now, until we release support for webhooks to be created as part of app requirements.

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Kyle Pinkley,

    Yes, that's right. From that date active HTTP targets on all accounts will be forcibly migrated to webhooks and there will be no way to revert the changes. New HTTP targets will not be able to be created after that date.

    Chris

    0
  • Jose Ortiz

    Is there some way to know (preferibly from the API) the target from which the webhook was created when migrating?

    Thanks in advance.

    0
  • Justin Federico

    @...

    Support for placeholders in the URL is "coming soon".

    https://support.zendesk.com/hc/en-us/articles/1260803041889/comments/4404782666906

     

    0
  • Kyle Pinkley

    Can you confirm if February 22 is still the date when HTTP targets will be deprecated and converted automatically to webhooks? 

    0
  • Jacob Kjeldahl

    Chris Sos 

    Regarding these two bullets:

    • HTTP targets created by existing installed private apps and apps installed from the Zendesk Marketplace will be converted to webhooks.
    • New and updated marketplace apps will fail validation if their requirements include HTTP targets. Similarly, private apps uploaded after the deprecation date will fail validation if they contain HTTP targets in their requirements.json file.

    Is the conversion automatic or should I be able to do it manually now? I am currently not allowed to update the target I currently have installed as part of a private app.

    The requirements specification does not seem to allow specification of webhooks yet. https://developer.zendesk.com/documentation/apps/app-developer-guide/apps_requirements/ when will this be possible?

    0
  • Arnaud Héritier

    Thanks a lot Chris Sos, I will do it for my instance

    0
  • Arnaud Héritier

    Hi Chris Sos

    My understanding of this article comments is that URL Targets to webhooks are out of the scope for now. Could it change in the future? Should we study to move them to webhooks too ? Will you provide any converter like you did for HTTP Targets?

    Thanks

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Sandro Olivieri,

    Placeholders are supported in URLs as you described. Please ensure the target in question is also active and not associated with an app as these are currently being skipped for conversion.

    If you're still seeing issues, let me know and I'll open a ticket on your behalf to investigate.

    Chris

    0
  • Zach Anthony
    Zendesk Product Manager

    Hi Jacob Kjeldahl

    I can understand that this is a little ambiguous in the announcement above. In regards to conversion, this will be automatically handled by Zendesk as HTTP targets created by apps are excluded from the conversion process available to customers in product.

    With regards to availability of webhooks support in apps requirements, we had hoped this would be able to be released earlier, but this will be coming very shortly - we are currently resolving a few issues here but rest assured this will be available in the coming weeks. Until this is available, apps will continue to be able to create HTTP targets and will not fail validation.

    0
  • Chris Sos
    Zendesk Product Manager

    Hi @...,

    The situation with apps is still being worked on. We hope to very soon have webhooks available in requirements alongside other types. A transition plan is still underway for migration of requirements-created webhooks.

    We will be updating these articles once we have more information for app developers and users.

    0
  • Chris Sos
    Zendesk Product Manager

    Hi all,

    Webhook retry logic is documented here: https://developer.zendesk.com/documentation/event-connectors/webhooks/creating-and-monitoring-webhooks/#webhook-retry-logic

    Webhooks are built to be RESTful and will follow server directions for retries for temporary issues like HTTP 503s or 429s. We would recommend servers not returning these responses if the requests should not be retried.

    We'd love to know what specifically is concerning about this logic.

    0
  • Anton Maslov

    Hi Chris Sos any ETA on when support for placeholders is going to be implemented for webhooks?

    Our goal is to use URL like https://zendesk.com/api/v2/tickets/{{ticket.id}}.json

    0
  • Chris Sos
    Zendesk Product Manager

    Hi @...,

    Thanks for the feedback. Many existing targets users use basic authentication. There's nothing inherently wrong or insecure with basic auth itself, but how the requests are sent.

    For this reason, we are removing any authentication features for webhooks that choose to use HTTP (not secured with TLS).

    0
  • McCabe

    why not just disable the basic username / pw from utilizing webhooks? 

    0
  • Daniël Nieuwendijk

    This specifically talks about the deprecation of HTTP targets. Are URL targets going to be similarly affected? I know it says only HTTP targets will be affected bu I just wanted to be sure.

    I also have this question. The email I received mentioned both URL and HTTP targets being replaced, but the help pages only refer to HTTP targets, as far as I've seen.

    0
  • Tomi Heiskanen

    Could you please clarify the situation with Zendesk apps. In requirements.json the developer is able to define targets (including HTTP targets), but it does not support webhooks. Soon there won't be any way for the apps to define a HTTP target / webhook in the app requirements?

    0

Please sign in to leave a comment.

Powered by Zendesk