Converting HTTP targets to webhooks

Return to top

92 Comments

  • 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
  • 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
  • Walter

    Jonathan- It seems like you can't.  You may need to use a third party service such as Power Automate to handle the ticket update.

    I just did a test.  And it failed.

    The failure was probably due to the placeholder not evaluating in the URL.

    0
  • Chris Sos
    Zendesk Product Manager

    Jonathan,

    That's correct. Support for placeholders in URLs is coming soon. These targets are for the moment skipped from conversion. Once available, they'll be "un-skipped" and ready to convert.

    Walter,

    Would be good to understand the issues you're running into. Did you add the payload to the trigger action that you expect? What did you receive in a live test?

    -3
  • Walter

    @...

    Yes, I added the payload to the trigger action.  On the receiving end, the payload was not there.  The body of the HTTP request was completely empty.  Only the headers were there.

    0
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • Abed Islam

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

    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
  • Abed Islam

    Thanks, @.... For some reason I misread those as if they were referring to HTTP Targets, not webhooks.

    0
  • Chris Ryland

    We don't even have an integrations tab. Where do I find that?

    0
  • 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
  • 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.

    4
  • Chris Ryland

    +1 for Slack integration.

    1
  • Cameron Ball

    @... the Integrations Tab is in the Admin Center, which is global across Zendesk products (Support, Explore, etc.). It's not the gear on the left side. It's the four squares in the top right corner. Click on Admin Center at the bottom of that menu.

    0
  • Chris Ryland

    Ah, thank you. So rarely use that I forget about it.

    But we do have a Slack integration, but I see no targets to update.

    0
  • CJ Johnson

    There's no "Get Started" and no options to convert any webhooks when I visit the section in the admin center. Is this a bug, or should I assume that none of my webhooks can be converted? 

    0
  • Rich L

    CJ, Several people, including myself, have encountered this.

    As far as I can tell my HTTP targets meet the criteria to be eligible for conversion so I'm not sure what to make of this yet.

    0
  • 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.

    0
  • 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.

    0
  • 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
  • Au Finh

    @... Thanks for clarifying. This is helpful to know for planning and how we should communicate to our customers. 

    0
  • Walter

    @...

    Any update on the empty JSON payload issue?

    0
  • Chris Sos
    Zendesk Product Manager

    Hi @...,

    I've created a ticket to follow up with your issue specifically.

    Cheers,

    Chris

    -1

Please sign in to leave a comment.

Powered by Zendesk