About converting targets to webhooks
Consider the following before converting your targets.
- The conversion tool only converts HTTP targets.
- Targets must be active to be converted. Disabled and deactivated targets won’t be converted.
- Webhooks don’t support HTTP authentication. Any targets that use authentication must be updated to use HTTPS before you can convert them.
- All eligible targets will be converted. It isn’t possible to convert one target at a time.
- Targets will remain active until they’ve been successfully converted or until HTTP targets are deprecated.
- If any part of the conversion fails, everything related to the target(s) that failed is rolled back. In no circumstances should a failed conversion affect existing configurations of triggers and business rules.
- The conversion is fully reversible until HTTP targets are deprecated. If, for any reason, you want to revert a target you converted, you can do so.
Preparing HTTP targets to be converted
There are two scenarios in which targets cannot be converted:
- Targets use HTTP instead of HTTPS and have basic authentication enabled
- Targets are inactive
In most cases, there are simple ways to modify the targets so that they can be included in the conversion.
Changing from HTTP to HTTPS
During the conversion process, you can choose to Convert unsecure targets to secure webhooks (HTTPS) or skip them. If you choose to convert insecure targets, no action is required to resolve this ahead of time.
If you wish to convert only some of your HTTP targets that use HTTP, you can manually update the URLs for just those targets and then select Don’t convert unsecure targets during the conversion process.
To change a target URL from HTTP to HTTPS
- In Admin Center, click the Apps and integrations icon (
) in the sidebar, then select Targets > Targets.
- Find the target in the list and click Edit.
- Update the Url value to use https.
- Select Update target from the drop-down and click Submit.
Making sure targets are active
Only active HTTP targets are eligible for conversion.
To activate a target
- In Admin Center, click the Apps and integrations icon (
) in the sidebar, then select Targets > Targets.
- Find the target you want to reactivate inn the Inactive targets list and click activate.
Converting HTTP targets to webhooks in Admin Center
The conversion process starts by cloning all existing targets. The business rules are then modified to use webhooks instead of targets. The final step is deactivating the targets and activating the webhooks.
If the conversion is successful, the HTTP targets are deactivated, the webhooks are activated, and the business rules are updated almost simultaneously.
If the conversion of a target failed, the target and corresponding triggers will remain active and unchanged.
To convert HTTP targets to webhooks
- In Admin Center, click the Apps and integrations icon (
) in the sidebar, then select Webhooks > Webhooks.
- Click Get Started.
If you have targets that are eligible for conversion, you’ll be guided through the conversion process.
- Click Manage targets to ensure your targets are prepared for the conversion and then click Next.
- Review the summary of eligible targets and click Convert targets.
- If insecure (HTTP) targets are detected, you can choose to Convert unsecure targets to secure webhooks (HTTPS) or Don’t convert unsecure targets.
Note: Converting insecure targets to secure webhooks could break your workflows if your server doesn’t support HTTPS.
- Click View targets conversion log to see which targets were successfully converted as well as any that failed.
Targets skipped during conversion
Viewing the conversion log
At the end of the conversion process, there’s a prompt to view the conversion log. You can also access it at any time from the Webhooks page. To view the conversion log, click Actions at the top of the page and then click View targets conversion log.
- The Converting tab is only populated during the conversion process. It should be empty most of the time.
- The Converted tab shows a record of all webhooks that were successfully converted. From this tab you can view a webhook in more detail, revert a webhook back to a target, and find the conversion ID for a given webhook.
- The Failed to convert tab shows a record of each eligible target that didn’t convert successfully. Use this tab to see the details about why the conversion failed and retry the conversion for each target.
Retrying a conversion
From the Conversion Log, you can see which targets failed to convert and retry the conversion.
To retry the conversion of a target
- In Admin Center, click the Apps and integrations icon (
) in the sidebar, then select Webhooks > Webhooks.
- Click Actions at the top of the page and then click View targets conversion log.
- Click the Failed to convert tab, and find the target you want to retry.
- Resolve the error described for the target.
- Click the options icon (
) on the target's row and click Retry conversion.
While the conversion is retried, the target will be listed on the Converting tab. When the conversion retry is complete, the target will either be moved to the Converted tab or the information about the target’s failed conversion will be updated on the Failed to convert tab and the target will be moved to the top of the table.
Resolving conversion errors
Failure | Reason | Fix |
---|---|---|
Failed to update trigger | The update to the trigger that is calling the webhook failed. This if often caused by an invalid trigger configuration, unrelated to the conversion. | Review your triggers to ensure they can be modified and saved, then try the conversion again. |
Failed to update target | The update to disable the HTTP target failed. This is typically caused by an invalid target configuration, such as an invalid target URL. | Review your HTTP targets and ensure that the targets can be modified and saved, then try the conversion again. |
Failed to update webhook | The webhook wasn't created because of validation issues. | Review your HTTP targets to ensure they are properly prepared to be converted, then try the conversion again. |
Reverting a converted webhook back to a target
To revert a webhook to a target
- In Admin Center, click the Apps and integrations icon (
) in the sidebar, then select Webhooks > Webhooks.
- Click Actions at the top of the page and then click View targets conversion log.
- Click the Converted tab, and find the target you want to revert to a target.
- Click the action menu icon (
) and click Revert to target.
After the webhook is successfully reverted to a target, it's removed from the list on the Converted tab.
116 Comments
Are stored usernames and passwords carried over in the migration?
Hi @... -
Any word yet on the progress of including the webhooks in app requirements? We are in a real bind here, as this is an important piece to making some apps work. There is a big difference from a security standpoint (not to mention coding effort) to create the webhooks programmatically as opposed to including them in the app requirements, and we simply can't continue with the existing "targets" knowing that they are being deprecated.
Thank you for your continued support!
Hi @...,
Thanks for the message. We totally understand how this uncertainty can affect your app development underway.
We are making progress and it's being worked on as I type this. I don't have an ETA I can share at this time, but I hope I'll be able to update on this very soon!
Chris
Thank you @...!
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!
Hi @...
Any news regarding webhooks in app requirements?
/Jacob
Any update on allowing placeholders/URLs in webhooks so we can finish our conversion?
Hi @...
Placeholders in URLs are now supported. You should be able to proceed with the conversion without issue :)
Hi @...,
This work is still continuing. I don't have any specific news yet on this front.
Chris
So, the only targets I have are Salesforce Integrations. When I navigate to the web hooks area, nothing shows up for the "Get Started" area. Does this mean my targets cannot be converted?
Kevin Lewis this migration and deprecation only applies to HTTP targets. Targets created from Zendesk Integrations aren't being migrated or deprecated at this time. For more information, see the announcement.
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:
After clicking on "Convert Targets", I get an error saying "Internal Server Error. Something is wrong". Has anyone seen this and know how to fix it? Thank you!
We have only 1 active target that I think needs to be converted, it's a URL target not associated with any app. I wasn't able to convert it before, I assumed because it uses placeholders. When I start the conversion process, I get the message 'You have 0 active targets ready to convert now or later.' Why can I still not convert this target?
Mark Leci The migration is currently only for HTTP targets. URL targets aren't being deprecated or migrated at this time.
Do we have an update on converting HTTP targets that use placeholders? I've been watching for an announcement but haven't seen one yet.
Ginni Goggins placeholders are now supported. We have removed reference to placeholders from the documentation around reasons that conversion may be skipped. These targets will no longer be skipped for conversion.
Under the section "Preparing HTTP targets to be converted" it mentions "Find the target in the list and click Edit.". I cannot find the edit button for my Slack Integration.
I understand that targets created via apps requirements, like Zendesk's Slack integration, are not yet eligible for migration. I am surprised that an app as popular as Slack cannot yet be migrated. When will Zendesk's Slack app be eligible for migration?
I converted my HTTP targets with URL parameters a while ago - all worked well.
If it wouldn‘t work, it would tell you so and leave all in place - so why not just try?
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
HI Julio H
I believe I fall into the category that you described in your previous comment. As you can see I have one Slack integration, which I am unable to convert.
So I am confused as to why I received this email:
Was that email sent in error? or do I need to convert my Slack integration?
Hi Chris Sos, or maybe Julio Hernandez,
Any update on my question above?
This Zendesk/Slack integration is integral to my day to day work, any help on this would be greatly appreciated.
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
I am seeing the same logs in ticket events as RichL >> WebhookEvent (not implemented).
Not sure if anyone finds the same behavior?
Tanawat Oonwattana
I see it too, but it does not seem to prevent our webhooks from executing.
Everything seems to be working fine for us.
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.
Tanawat Oonwattana @ walter_
This was never acknowledged as a bug or still in development here but this appears to be resolved on my Zendesk instance.
Conversation events on tickets very recently (I think maybe on Friday?) started showing the link to the Trigger where the webhook was called. Maybe this is a phased roll out? Not sure because Zendesk hasn't commented on it here but I'm just glad it seems to be sorted for me. Good luck!
Hi Tanawat Oonwattana, Walter RichL,
This is a bug that we are actively working on a fix for. For non Agent Workspace accounts this fix is out and the "Not Implemented" message has been replaced with the same message that appeared for Targets.
For Agent Workspace accounts (where there is currently nothing shown), a fix is coming very soon here.
Hope this helps clear this up!
Chris
Hello,
Could you please confirm if URL targets and HTTPS targets will be affected by this change?
Thanks in advance!
Drago Markov The migration is currently only for HTTP targets. URL targets aren't being deprecated or migrated at this time, though you can manually recreate your URL targets as webhooks if you'd like.
Hello,
I have the same error David Chiu had: after clicking on "Convert Targets" or while testing the creation of a new webhoook, I get the error "Internal Server Error. Something is wrong".
I use the same data as our current HTTP targets, that are not in error.
Does anyone know what I am missing?
Thank you.
Please sign in to leave a comment.