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.
115 Comments
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.
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:
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.
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?
@...
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.
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.
The text in JSON that is sent to the destination is compressed in HTML format, e.g.
(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:
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?
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?
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.
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
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?
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?
I just want to comment that I'm in the same situation as @... and @.... Thanks!
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?
Shouldn't this article lead with a link to learn more about webhooks? I haven't heard of Zendesk webhooks before.
@..., 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.
Thanks, @.... For some reason I misread those as if they were referring to HTTP Targets, not webhooks.
We don't even have an integrations tab. Where do I find that?
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'
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.
+1 for Slack integration.
@... 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.
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.
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?

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.
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.
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.
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.
@... Thanks for clarifying. This is helpful to know for planning and how we should communicate to our customers.
@...
Any update on the empty JSON payload issue?
Hi @...,
I've created a ticket to follow up with your issue specifically.
Cheers,
Chris
Please sign in to leave a comment.