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
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.
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.
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?
Hi Ahmed,
Please note, this conversion process only applies to HTTP Targets. Other types of targets are not being converted at this time.
Chris
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?
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.
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
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.
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!
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
Is there some way to know (preferibly from the API) the target from which the webhook was created when migrating?
Thanks in advance
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
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?
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
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
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?

Hi Chris Sos Any update with my latest comment regarding the Zendesk-Jira App extensions?
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.
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?
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
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:
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.
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.
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?
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
Hi,
I am trying to convert six active targets to webhooks without any luck. The targets are using HTTPS and are active, but when I click on Convert Targets, then Manage targets, I end up on Targets and cannot select them. The only option I have is to edit or deactivate them. Could someone please assist me with this? Thanks.
Alvin
Please sign in to leave a comment.