Converting HTTP targets to webhooks

Return to top
Have more questions? Submit a request

68 Comments

  • Walter Lin

    Thanks Chris Sos

    I will share details in the ticket.

    0
  • 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
  • Laura Mirto

    Does this impact links that are added in Knowledge Base articles? 

    Thanks,

    Laura M

    0
  • Acenerate

    We have integrated targets into our GitHub/Azure DevOps ticket integration app Git-Zen; the targets are installed via the requirements.json so that they won't be inadvertently altered.  However, there does not seem to be an allocation for webhooks in the requirements.json:

    https://developer.zendesk.com/documentation/apps/app-developer-guide/apps_requirements/

    What is the plan with regard to being able to include webhooks within the app requirements, as is currently done with http_targets?

    0
  • Chris Sos
    Zendesk Product Manager

    Jeremy Heath

    Good question. In the coming months you'll be seeing more settings move to Admin Centre. The reason for this is because Zendesk is more than just ticketing, and webhooks will be extended to cover multiple products (not just Support), so Admin Centre is where this lives to control webhooks across multiple products.

    Laura Mirto

    This only affects targets, it should not affect any links present on a knowledge base.

    Acenerate

    This is coming soon, we do plan to have webhooks available in apps requirements to allow partners to take advantage of it. We are also working on the plan for getting requirement-created targets over as well. Stay tuned.

    0
  • Eric Powell

    Hi Chris Sos

    We just converted ours to webhooks and are running into the same issue as Walter Lin

    No JSON payload is being sent to our endpoint with the webhook. The trigger is configured with a JSON body:

     

    0
  • Jeremy Heath

    Chris Sos

    That makes sense overall thanks.
    Can I suggest then that where the extensions part is in support, we have a jumplink to webhooks so we can find it easily?

    0
  • Peter Hochstrasser

    Hi Chris Sos

    I think it would be worthwile to revise and cross link the articles regarding replacement of http targets with webhooks, and to concentrate comments in one (this?) article only.

    From what I read up to now, current state of affairs is:

    • URL parameters as needed to call the Zendesk API will arrive in weeks, not months
      If your targets are not converted at this time, this might be the problem
    • In some cases, the webhook request JSON payload seems to be empty.

    Yours truly

    Peter

    (Updated with Chris' information)

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Jeremy Heath

    Thank you for the feedback. We'll look into making a quick link from the Targets page to Webhooks.

    Hi Peter Hochstrasser

    Thanks, that's a great breakdown. Comment bodies were fixed a couple of days ago, but the rest is looking good. I'll add this to our article here.

    Chris

    0
  • Jaïs Pingouroux

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

    Thanks!

    0
  • Tanawat Oonwattana

    Chris Sos

    you are saying comment bodies are fixed?

    I don't think so, look at my comment in this conversation 3 days ago, I jsut tested now and comment body is still returning in string in API, which makes JSON mis-format.

    thanks.

    0
  • Charlie Smith

    I tried to convert one target, but the target failed. I went back through the process and clicked 'Convert Targets' but I keep getting an error that there are no targets to convert.

    0
  • Chris Sos
    Zendesk Product Manager

    Tanawat Oonwattana Yes, I can confirm the initial issue with comment bodies with new lines has been fixed. I'll open a ticket on your behalf and we can take a look.

    Charlie Smith I took a look at the target, and it appears the trigger that your target is currently attached to it invalid. I'd recommend taking a look at the trigger specifically, fixing up any issues and re-trying :)

    0
  • Inni

    I tested it in the sandbox and the webhook works fine, but the trigger that sent the webhook is not logged in the event. Is this an error?

    0
  • Aaron Corley

    Hi Chris Sos,

    I am also having the same issue after converting our targets. I am getting an empty payload error when sending a test.

    I would love to hear what the fix was for Walter Lin

    Thanks,

    Aaron

    0
  • Khajik Khajadourian

    When will placeholders be supported by webhooks? 

    1
  • Katarzyna Rudnicka

    My targets are created by survey app and therefore I cannot edit them. Will they be updated automatically?

    0
  • Chris Sos
    Zendesk Product Manager

    Hi Inni,

    You can check on the triggers currently using that webhook by going to the webhook details and viewing the "Event Subscription" tab. We're currently working on improving the ticket events trigger message as well.

    Hi Aaron Corley,

    Thanks for the report. I'll generate a ticket on your behalf and add you to ensure you're notified of the fix. We are aware of an issue with some servers not supporting `chunked` transfer encoding. We are making changes to bring this back to the same as targets with a standard `content-length` header instead.

    Hi Khajik Khajadourian,

    We are aiming to release support for placeholders in URLs in the next few weeks. I will update this thread once that's out.

    Hi Katarzyna Rudnicka,

    This is expected. We will be working with app partners on migrating those targets to webhooks separately. There is no action for you for those targets.

     

    0
  • Vladimir Petrushenka

    Hi Chris Sos

    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 

    2
  • Chris Sos
    Zendesk Product Manager

    Hi Vladimir Petrushenka,

    Placeholders are available to be used now in webhooks for payload bodies. In URLs, this is coming very soon. When it's out, I'll post a comment here and documentation will be updated.

    Chris

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

    Hi Chris Sos -

    Thanks for your continued updates to this thread - it is great to see active engagement, especially for something as important as this!

    Has there been any movement with regard to including this within developer options?  Especially considering the lead time required for Marketplace app approvals, etc, this is important to nail down.  To recap: there does not seem to be an allocation for webhooks in the requirements.json:

    https://developer.zendesk.com/documentation/apps/app-developer-guide/apps_requirements/

    What is the plan with regard to being able to include webhooks within the app requirements, as is currently done with http_targets?

    Thank you!

    0
  • Chris Sos
    Zendesk Product Manager

    Hello everyone,

    I'm pleased to report that placeholders in URLs for webhooks is now live. You can create new webhooks with placeholders in the URL and have them work as they did with targets.

    Note, targets using placeholder URLs are not yet eligible for conversion using our conversion tool just yet. We hope to enable them next week.

    We appreciate everyone's patience on this!

    Chris

    0
  • Chris Sos
    Zendesk Product Manager

    Hey Acenerate,

    Thanks for the comment. Our plan is to have webhooks available inside of app requirements, as well as a transition for existing target requirements to webhooks with minimal to no admin or developer action required.

    Unfortunately, I can't give a more specific time-frame but we have absolutely committed to doing this before the deadline. We will not be shutting anything off if people have not had any opportunity to migrate.

    We'll update once we have a clearer idea of our path forward, so really appreciate you hanging in there!

    Chris

    0
  • Jagadeesan Durairaj

    When can we expect the support for API-Key header or custom header in the Web Hook?

    0
  • 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 Dmitry Kreisserman,

    In Admin Centre on the webhooks page, from the actions menu you should see "Convert targets" in the dropdown, this should allow you to view convertable targets and perform the conversion:

    Are you saying you're not seeing this option at all? Or when on the page you're not seeing any targets available to convert?

    Chris

    0
  • Matt Dunn

    Chris Sos I'm in the same position as Dmitry. On the webhooks page, this is all I see (there is no Actions menu):

    0
  • Dmitry Kreisserman
     
    That dropdown menu wasn't available for me till I clicked on "Create webhook" and then Cancel.
    For users accessing "Webhooks" page for the first time, that menu doesn't exit, and then need to try creating a new webhook and cancel it.
    THANKS for your help, now once I did the trick - I was able to convert all my Targets and now they appear on the Webhook page.

    It would be great if you could fix that UX issue so the dropdown menu will appear in the first place on Webhook page.
    0
  • Chris Sos
    Zendesk Product Manager

    Hey Dmitry Kreisserman,

    Thanks for the extra detail! Yeah I can see that being confusing if you're coming straight to the webhooks page. I've made a note of that and will bring it up with our UX team.

    Glad you're able to convert :)

    Chris

    0

Please sign in to leave a comment.

Powered by Zendesk