Converting HTTP targets to webhooks

Return to top

115 Comments

  • Drago Markov

    We had a couple of those @Emilie Duveau, turned out the triggers that used the targets contained a deactivated ticket field. Best check if there might be something like this on your instance. In our case we had to activate the ticket field in order to update the trigger, otherwise it would not allow us to update it. Next we deactivated the trigger target & field, as it turned we hadn’t used those in more than a year anyways. Hope that helps.

    0
  • Emilie Duveau

    Drago Markov Hi, thanks for your answer! Sadly, this didn't help, but it turned out that I also get the error when I create a webhook from scratch, the connection test with no link to any trigger doesn't work either. So I'll investigate further.

    0
  • Ahmed

    Hello,

    I have some active targets that use HTTPs urls and have placeholders in the url. They don't use authentication.

    They still don't appear in the list of of targets that can be converted into Webhooks. How can I know what is preventing them from being eligible?

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Ahmed,

    Please note, this conversion process only applies to HTTP Targets. Other types of targets are not being converted at this time.

    Chris

    0
  • Ahmed

    Hi Chris Sos,

     

    Thanks for your reply. My targets are actually URL targets. Does that mean those will not be deprecated and I should just ignore that announcement?

    0
  • Peter Hochstrasser

    Hi Chris Sos

    As I stated before, the automatic conversion of (my) HTTP targets to Webhooks worked great.

    However, I reviewed those targets today and found:

    So, the Username is empty. They all work, so the username has to have been stored, but it just seems a bit odd.

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Ahmed,

    That's right, URL targets are not part of this EOL program. However, I would strongly recommend thinking about moving over to webhooks as targets are more legacy features which may be removed in future.

    Hi Peter Hochstrasser,

    That's right, the credentials are stored but they do not show in the UI. We recognise this isn't ideal as it may seem like the credentials are blank and we have work prioritised to address this coming soon.

     

    Chris

    0
  • Mark Leci

    Jacquelyn Brewer Thank you for clarifying that this doesn't apply to me! Unfortunately, I've wasted a lot of my time looking into this, attempting to work around the missing options to convert and trying to convert targets that ultimately I didn't need to convert because I received repeated emails from Zendesk stating that I needed to do it 

    "Important reminder to convert your Targets to webhooks"

    "You’re receiving this message because you are currently using Targets that need to be converted to webhooks before the discontinuation."

    My feedback is for next time please try not to send repeated important reminder emails to clients unless there is actually action required. 

    0
  • Mark Ellers

    When converting targets to webhooks, will currently active triggers with actions set to notify targets be automatically updated to the respective webhooks, as well?

    I have a large number of triggers, all with unique JSON bodies, so manually updating all of these triggers would be incredibly inconvenient - especially since changing the action drop down selection automatically deletes the existing JSON body.

    It's hard to test this out myself because there's no way to convert a single target at a time without deactivating all other targets.

    Any insight would be greatly appreciated!

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Mark Ellers,

    That's right. All triggers that are using the target will also be updated with the existing JSON body to use webhooks. There should be no need for you to manually update the triggers during this process.

    However, if your triggers can't be updated you'll see this in the conversion log (and the changes will not be finalised). If any conversions fail to occur for whatever reason, everything will continue to work as it did pre-conversion.

    Hope this helps.

    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
  • Chris Sos
    Zendesk Product Manager

    Hi Jose Ortiz,

    The name and description of the created webhook will be the same as that of the target. There's no specific record of the target in the webhook.

    Chris

    1
  • RichL

    Hi Chris Sos Is there a known limitation or bug regarding Zendesk webhooks and Sunshine API custom objects?

    I always get a 400 Response "Invalid Headers" when using a Zendesk webhook to POST to this endpoint: https://mycompany.zendesk.com/api/sunshine/objects/records

    I was, however, able to setup an old school "HTTP Target" which worked fine with the above endpoint. I was able to create a new object record as intended. But then after successfully converting that HTTP target to a webhook, the resulting webhook would again only produce the 400 "Invalid Headers" response.

    Is this a scenario where support would be able to help me to convert the functional HTTP Target to a Webhook or is there some known/expected limitation with webhooks and Sunshine API?

    0
  • Yaniv Dayan

    Hi Chris Sos 

    Five months ago you wrote "Yes, we will be ensuring placeholder in URL support will be coming before the cutover (at this point, it's a few weeks away but definitely not months). "

    Any update on that? 

    We still cannot convert all our targets to webhooks. 

    Cheers

     

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Yaniv Dayan

    Placeholder support has been available in URLs since September of 2021, apologies if that was not clear. You should be able to convert any targets with URL placeholders.

    Chris

    0
  • Yaniv Dayan

    Hi Chris Sos

    Thanks for confirming it. 

    Converting our targets to webhooks, three targets were not converted. That includes the two Zendesk-Jira App extensions and one URL target (see below).

    Any suggestion?
     

    0
  • Yaniv Dayan

    Hi Chris Sos Any update with my latest comment regarding the Zendesk-Jira App extensions?

    0
  • Jacquelyn Brewer
    Zendesk Documentation Team

    Yaniv Dayan - About a week ago we updated the announcement with information about webhooks created by Zendesk integrations, including Jira. Here's a link to a comment that summarizes the changes: https://support.zendesk.com/hc/en-us/articles/4408826284698/comments/4418202384794. I hope that has the information you're looking for.

    0
  • Yaniv Dayan

    Hi Jacquelyn Brewer and Chris Sos,

    Still - trying to convert the extensions to webhook, I get zero results, though I have two extensions, one of them is Jira:

     

     

    Any ideas?

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Yaniv Dayan,

    That looks like expected behaviour to me. The Jira integration will be converted by Zendesk and no action is required from you.

    This process only applies to HTTP targets, so URL targets are not being converted at this time.

    Chris

    0
  • Tomer Ben-Arye

    Hi all,

    Since I have faced the same issue as most of you had (or have), I script something to help me identify the needed changes in triggers and automation in ZD.

    The issue
    HTTP targets were successfully converted, but you see double and the targets are still in active mode

    Why do you see it?
    ZD uses the active targets in triggers and automations

    The solution ( not baked enough - quick and dirty! but will let you know if something is going to fail in 22-Feb)
    In my case, there was a total of 45 scenarios, and I did copy-paste to make them work.
    Most of my scenarios were to use the API UPDATE ticket PUT command to write some internal comments. it IS possible that your scenario is different - therefore, you'll have to change the code a bit...

    Python3:

    from zenpy import Zenpy
    from dotenv import load_dotenv, find_dotenv
    import os

    load_dotenv(find_dotenv())


    ZD_USER = os.environ.get("ZD_USER")
    ZD_PASSWORD = os.environ.get("ZD_PASSWORD")
    ZD_URL_PREFIX = os.environ.get("ZD_URL_PREFIX")

    creds = {'email': ZD_USER,
    'password': ZD_PASSWORD,
    'subdomain': ZD_URL_PREFIX}

    zenpyclient = Zenpy(**creds)


    def m(component, component_name):
    if component.active:
    for action in component.actions:
    if action['field'] == 'notification_target' and action['value'][0]\
    in http_targets:
    print(f"component: {component.title}, {component.id},"
    f" https://sentinelone.zendesk.com/agent/admin"
    f"/{component_name}"
    f"/{component.id}")
    print(f"Old value:\n{action['value'][1]}")




    # Mapping HTTP targets
    http_targets = []
    targets_generator = zenpyclient.targets()
    targets = targets_generator[::]
    for target in targets:
    if target.type == 'url_target_v2':
    http_targets.append(str(target.id))

    # Checking affected triggers with those targets:
    triggers_generator = zenpyclient.triggers()
    triggers = triggers_generator[::]


    for trigger in triggers:
    m(trigger, 'triggers')

    # Checking affected automations with those targets:
    automations_generator = zenpyclient.automations()
    automations = automations_generator[::]

    for automation in automations:
    m(automation, 'automations')

     

    0
  • Dave Kaminsky (Qumulo)

    Chris Sos Can we get an update (or at least where on road map) for placeholder use in webhooks?  I have several projects over the next 3 quarters that have a dependency on the ability to use placeholders for net new targets/webhooks.

    Will be we able to edit our existing targets as needed while we wait for placeholder functionality to be "moved" to webhooks?  

     

    this impacts many customers' abilities to execute planned enhancements and integration. 

    0
  • Jacquelyn Brewer
    Zendesk Documentation Team

    Dave Kaminsky (Qumulo) Chris posted the following comment on the Announcement about support for placeholders: https://support.zendesk.com/hc/en-us/articles/4408826284698/comments/4411110247322. In summary, they're supported now.

    0
  • Walter

    Chris Sos,

    I don't know if I am mistaken, but I thought I that the new webhook targets support custom headers.  And just today, it seems that custom headers are no longer available? 

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Walter,

    They do not support custom headers at this time. This was something though that we're exploring for a future enhancement but I can confirm this was never part of webhooks previously.

    Hope this helps!

    Chris

    0

Please sign in to leave a comment.

Powered by Zendesk