Creating webhooks in Admin Center

Return to top


  • Jacob Christensen
    Community Moderator

    Very exciting stuff!

    Testing this I was expecting to see an event in the ticket event log, for tickets where a trigger ran a webhook action, but it isn't. Is this deliberate?

  • Jacquelyn Brewer

    Hi Jacob. Thanks for your question. This is expected. Webhooks run in response to something else happening, such as a ticket event. The event that triggers the webhook to run might be captured in the ticket event log, but all of the webhook logging is captured in the webhook activity logs.

  • Jacob Christensen
    Community Moderator

    Thanks Jacquelyn. I get that the webhook specific logging is captured in the webhook activity logs, but since a trigger is firing on a ticket event, I would expect to see that action logged on said ticket - like any other trigger would.

  • Chris Hynes

    How do we reference the contextual ticket ID in the URL? 

    With Targets, we are able to reference a ticket like this:{{}}.json

    Which allows our automations to make updates to tickets. I don't see how to do this with the webhook model.

  • Peter Hochstrasser



    It looks as if the webhook URL is static at the moment.

    This would require to rewrite all these targets into applications using a third party server or create Zendesk Apps to serve the purpose.

  • Nathan Gutauckas


    We are also using this same model to update tickets.

    Our use case: Each user has a custom field: "CC Email". When a ticket is created by that user, that add that CC to the ticket's email CCs. (ie. add your manager to your tickets)

    Right now our layout is: Trigger activates on update of ticket using JSON (PUT to email_ccs).
    Trigger notifies HTTPs target{{}}.json to update the ticket.

    Looking to see how we can achieve this with webhooks. Thanks!

  • Jason Brown

    I had the same question as Chris. I found that I could use the Update Many API endpoint and just pass a single ticket id. Placeholders are used in the Trigger JSON to set ticket ID.

  • Maik Künnemann

    @... we use this targets, how can we do this with webhooks?




  • Amber Ring

    Is there a plan to enable the use of placeholders in the Endpoint URL before HTTP targets are deprecated?

  • Peter Hochstrasser

    @..., @...

    Have a look at this article, and my comment:

    BR, P.

  • Chris Hronek

    In the "Testing a webhook" section is step 4 implying that we should be able to add request headers to the webhook? I don't see the option for creating headers in the webhook when I create it. Is this going to be an option?

  • Nathan Purcell

    Is there a reference for the expected payload structure? 

  • Peter Hochstrasser

    Hi @...

    As the webhooks will replace targets (at this time, only http targets), the payload is not defined in the webhook definition, but in the webhook execution in a trigger or automation. 
    In there, you can define the payload (as json).

  • Nathan Gutauckas

    I was able to get my previous Trigger working by using the Update Many endpoint like @... mentioned.

    For me, my end result looks like this:

    Created new Webhook named Update Many Tickets with Endpoint "https://[domain]", PUT (not POST), and JSON.

    Trigger Action -> Notify active Webhook -> Update Many Tickets
    JSON body:

    "tickets": [
    { "id": "{{}}",
    "email_ccs": [
    { "user_email": "{{ticket.requester.custom_fields.cc_email}}", "user_name": "{{ticket.requester.custom_fields.cc_email}}", "action": "put"}

    After these changes everything seems to be working.

  • Rahmat Budiharso

    Can I create custom request header for webhook?

  • Beau P.
    Zendesk Customer Care

    Hello Rahmat,

    Currently it is not possible do so, but there is an active discussion here that our product management team is monitoring. I'd recommend following and adding your use-case to this discussion as this helps guide future platform improvements!

    Beau | Customer Advocate

    Ask our Zendesk Community

  • Charles Larry

    "Webhook requests are automatically retried up to three times if the endpoint returns certain HTTP response codes. Unlike targets, consecutive failed requests won't deactivate webhooks."

    What are the "certain HTTP response codes"?  Is this documented somewhere?

  • Chris Sos
    Zendesk Product Manager

    Hi @...,

    Yes, this is documented on Creating and monitoring webhooks on our developer documentation.


  • Bruno Cabral

    I am also interested in the custom request header feature

  • Dave Dyson
    Zendesk Community Manager

    Hi Bruno,

    Head over to Passing API Header in HTTP Target, upvote that, and add your use case into the comments thread. The more information about what you'd need this for, the better. Thanks!

  • Carmelo Rigatuso


    We're using a web hook to create a ticket in an internal system for certain types of support requests. In the activity log, I can see that there is a response from the internal system which contains an ID that I would love to be able to add to the Zendesk ticket. Is there any way to read each response and add it to a form field in a ticket?

  • Kevin Ford
    Community Moderator

    Hi Carmelo Rigatuso,

    Unless Zendesk adds some new functionality, the only way you're going to be able to populate a ticket field is to have your internal system use the Zendesk API to update the field outside of sending the response.


  • Takkme


    I want to send ticket information to my notion database. So I'm try to make webhook but i can't make it because of the error saying 

    "{"object":"error","status":400,"code":"missing_version","message":"Notion-Version header failed validation: Notion-Version header should be defined, instead was `undefined`."}"

    How can I add Notion-Version to the header of zendesk webhook??

  • Christopher Kennedy
    Zendesk Developer Advocacy
    Hi Takkme,
    At this time, it's not possible to supply custom headers when creating webhooks.  Our Product Management team is considering additional authentication methods as a possible future feature enhancement.  Feel free to share the details of your use case in a product feedback post.  It can help us, as well as other users, gain insight into the problem you're looking to solve.

Please sign in to leave a comment.

Powered by Zendesk