Announcing the deprecation of HTTP targets and conversion to webhooks

Return to top

23 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.

    3
  • 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
  • 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
  • Justin Federico

    @...

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

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

     

    0
  • Chris Sos
    Zendesk Product Manager

    Hi @... @...,

    Apologies for the communication. I can confirm this only applies to HTTP targets, not URL targets. Future communications will be updated and made clearer.

    Greetings @...,

    As @... helpfully pointed out, this is indeed coming soon and is planned. We estimate a matter of weeks for this to be supported in webhooks.

    Cheers,

    Chris

    0
  • McCabe

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

    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
  • 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
  • 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
  • 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 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
  • 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 Anton Maslov,

    Placeholder support was released in late September for webhooks :)

    Chris

    1
  • Arnaud Héritier

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

    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
  • 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
  • Kyle Pinkley

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

    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
  • 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
  • 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
  • Jalerson Lima

    Hi Chris,

    Can you confirm what's exactly the deprecation date? Is it February 22nd, 2022?

    Thank you!

    0
  • Jacquelyn Brewer

    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

Please sign in to leave a comment.

Powered by Zendesk