Webhook expected approx execution/delivery time

5 Comentarios

  • Eric
    User Group Leader Community Moderator
    Zendesk Luminary

    Hey Gulzar,

    How are you measuring the time? Are you basing it off the event timestamp?

    0
  • Gulzar Shikalgar

    Eric

    Here is how i am measuring it:

    • We send updated_at timestamp in webhook payload for a ticket.
    • Then after request is received in our backend-service, we just write a logic request_received_time - update_at timestamp , this gives me result.

    Other way i measure is via signature-timestamp in header here is example of same:

    • ticket "updated_at": "2023-08-24T04:22:28Z"
    • X-Zendesk-Webhook-Signature-Timestamp : 2023-08-24T04:22:30Z
    0
  • Eric
    User Group Leader Community Moderator
    Zendesk Luminary

    Gulzar Shikalgar,

    Thanks for the info, this is expected behavior if your Webhook trigger is the last one. Essentially this comes down to the trigger cycle which you can read about here. The easiest way to resolve this is to put the webhook trigger higher in order so that it is one of the first to fire.

    0
  • Luis Valdez

    Gulzar Shikalgar, Hello I'm looking to implement this type of webhook, how do you send the update_at timestamp. I'm unable to find it on the list that has all the postion markers (the codes that arre sorrunded by two curly braces {{}})

    0
  • Greg Katechis
    Zendesk Developer Advocacy

    Hi Luis! You'll find the available options in our placeholder reference.

    0

Iniciar sesión para dejar un comentario.

Tecnología de Zendesk