Converting HTTP targets to webhooks

Return to top

95 Comments

  • Jaïs Pingouroux

    Hello,

    I use 7 active targets, all in https.

    When I go to the Admin Center > Integrations > Webhooks, I'm not offered to convert anything.

    I can only create new webhooks.

    Shall I recreate my existing targets, or will it create conflicts?

    11
  • Rich L

    I'm having the same experience as Jaïs. I have 3 active HTTP targets, each is using HTTPS, and none of them use basic authentication. Yet when I go to Integrations -> Webhooks I get a page with an empty list and a button at the top right to create a new webhook.

    Is this conversion thing maybe not rolled out to all Zendesk instances yet?

    6
  • Cameron Ball

    I just want to comment that I'm in the same situation as @... and @.... Thanks!

    6
  • Aaron Rylaarsdam

    Will the Slack integration Endpoint that was "Created by Slack App" that is an HTTP target be updated to a webhook?  I ask because this particular target cannot be edited in the Admin > Extensions page.

    5
  • Rich L

    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
  • Ben Weaving

    We are a partner of Zendesk and we use HTTP Targets with lots of our customers. We also use placeholders in the URL. Are you able to confirm that placeholders will be allowed prior to the cutover in 2022?

     

    Thanks in advance.

    3
  • Jeremy Heath

    Is it just me, or does anyone else think it's weird having this situated in the Admin section?

    So now when I'm building something and need a webhook, I'm going to have to enter the Admin part, which I really only use to allow Zendesk Assumption.

     

    Was there some logic for removing it from the normal working area where I make changes?

    3
  • Abed Islam

    Shouldn't this article lead with a link to learn more about webhooks? I haven't heard of Zendesk webhooks before.

    2
  • Chris Ryland

    +1 for Slack integration.

    2
  • Tanawat Oonwattana

    Hi Chris,

    When you say 'Support for placeholders in URLs is coming soon', do you have time timeline? as the document here says that 'HTTP targets are being deprecated in February 2022'.

    If the feature is coming later than HTTP targets being obsoleted, it would affect our business operations.

     

    One additional question:

    Currently, my business logic is using {{ticket.latest_public_comment}} or {{ticket.latest_comment}} in the body of HTTP Target.

    e.g.

    {
    "id":{{ticket.id}},
    "comment": "{{ticket.latest_comment}}"
    }

    The text in JSON that is sent to the destination is compressed in HTML format, e.g.

    {
    "id":123456,
    "comment": "Reply\n\nSincerely yours\nTanawat"
    }

    (you can notice \n for new line)

    However, when I tried creating Webhook with the same payload/placeholder in the body, it send the API out using this format instead:

    {
    "id":123456,
    "comment": "Reply

    Sincerely yours
    Tanawat"
    }

    The format is changed from what we are having in HTTP target, which cause the error in API.

    Is there anymethod to convert the comment text, back to be similar with HTTP Target?

    2
  • Chris Sos
    Zendesk Product Manager

    Hi @...,

    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). The announcement post also speaks that this is coming soon, as well as some other targets like for Zendesk integrations.

    @...

    We're working on this presently, thanks for the report!

    Chris

    1
  • Cameron Ball

    @..., it does; there is a link in the first sentence of this article under the word "created", leading to https://support.zendesk.com/hc/en-us/articles/1260803996569.

    1
  • 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
  • Johannes Ganter

    Deprecating HTTP targets is a problem for passing on ticket comments that include line breaks. Webhooks don't work well with line breaks unless they are replaced with "\n". However, just adding a placeholder such as {{ticket.latest_public_comment}} won't allow me to do that. Therefore, the JSON will break and the webhook will fail. Do you have any solution for that problem?

    1
  • JB

    What happens if we want to use a support placeholder in the url? 

    We're actually using an HTTP target to call zendesk update ticket endpoint at the moment in order to update the CC field as needed.
    Eg:

    /api/v2/tickets/{{ticket.id}}
    {
    "ticket": {
    "email_ccs" : [
    { "user_email": "{{ticket.ticket_field_360024147572}}", "action": "delete"}
    ],
    }
    }
    1
  • Dmitry Kreisserman

    Hi Chris Sos, we still cannot see an option to convert targets in the Admin Center, although all our Targets are httpS and active.

    We see only "Create webhook" option available.

    1
  • Chris Sos
    Zendesk Product Manager

    Hi everyone, just to update we have resolved the issue some people were experiencing with blank payloads being sent.

    Chris

    1
  • Vladimir Petrushenko

    Hi @...

    We use placeholders in majority of our targets so we are keen to hear when conversion of these targets will be supported. 

    How can we subscribe for updates on this subject? Will the update be via a comment here or there will be an email notification sent as an announcement? 

    Thanks 

    1
  • Chris Sos
    Zendesk Product Manager

    Hi Chris Ryland Shawn Rasmussen Beth Runzel Aaron Rylaarsdam

    Targets created via apps requirements, like Zendesk's Slack integration, are not yet eligible for migration. It is expected behaviour that this will not be migrated at this time. The migration process has some checks to ensure ineligible targets are not converted and will instead be skipped.

    More detail on why a target may be skipped for conversion is available on the main announcement.

    Hi CJ Johnson Mark Leci Rich Cameron Ball

    There was an issue earlier where we temporarily disabled the migration tool, but we have re-enabled it for all accounts a few hours ago after fixing the issue. Conversion is the best way to get over, and the safest since it's fully reversible. We don't recommend trying manual recreation as this may be prone to errors or duplication.

    Hi Au Finh Saechao

    HTTP targets after this date will become unavailable (however after this date will be force-migrated to webhooks). No workflows that HTTP targets currently provide should be affected. Targets themselves are no longer in development, and longer term we'll see movement away from these older targets to newer workflows and automations to achieve the same goals in a better way.

    1
  • Walter

    After converting some targets to webhooks, I sent a test with one of the new webhooks.  It does not seem to work properly.  The JSON payload in the test did not get sent.  It also did not work in a live situation.

    1
  • Tanawat Oonwattana

    I am seeing the same logs in ticket events as Rich L >> WebhookEvent (not implemented).

    Not sure if anyone finds the same behavior?

    1
  • Beth R.

    We only have 3 Targets, 2 are HTTPS already and the other is our Slack App integration. I'm lost on what I need to do here folks. Do I need to convert these or not? Also, the Slack App didn't offer the option to edit it. Like some of the posts above, I also didn't see the convert option for my targets just the option to create new webhooks.

    1
  • Mark Leci

    I also didn't have any option to convert my existing webhooks (in sandbox). I tried to convert manually but it didn't work properly, I assume because I am also using the placeholder in URL functionality. I also checked in the live environment and there is no option to convert available, just 'create Webhook' 

    1
  • Au Finh

    Looking forward to placeholders support as we won't be able to migrate targets that we've created on behalf of our customers until they're available. Please keep us updated. 

    As for HTTP targets being "deprecated" or "discontinued" in Feb 2022, does that mean targets will stop working after the cutoff, or does it just mean you'll stop supporting targets?

    1
  • 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
  • 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
  • Khajik Khajadourian

    When will placeholders be supported by webhooks? 

    1
  • Shawn Rasmussen

    I only have one HTTP target, which was created by Zendesk's own Slack integration. I believe this is the same issue that Aaron Rylaarsdam mentioned above. This is not able to be converted with this process, at least not right now.

    1
  • Jaïs Pingouroux

    As far as I'm concerned, the issue regarding the migration of existing http target has been fixed.

    Thanks!

    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

Please sign in to leave a comment.

Powered by Zendesk