Working with Webhooks

role administrator minimum version 2023 4 about webhooks webhooks process incoming messages triggered by events initiated in third party tools and sent to an endpoint incoming message data must be valid json or xml this is a new centralized webhook feature that can ultimately support multiple webhooks, endpoints, and authentication methods each webhook can be assigned to an action via a variable that allows the automatic parsing of the data received this diagram shows the high level process webhooks processing incoming webhooks are processed by the rest api, which validates the webhook and url validates that the format type declared in an incoming message header matches the body format if they do not match, the request is rejected validates that an incoming message does not exceed the webhook limit specified for your system provides a response code to the sender for more information, see webhooks logging docid\ dkc2w7sa66l0iqgijwzly parsing json or xml data webhooks use json and xml modifiers configured for actions to parse, change, and use data between an external tool and for json, incoming data must be a valid json object this parsing process uses the update variables or stored values type of action as the method to convert valid json or xml strings into data that can consume it creates a variable that declares a data type of json, xml, or xml collection and holds valid string data of the selected data type webhooks authentication for this release, the webhooks feature can only support api key authentication, but this will be expanded in future releases normally, the type of authentication you set for your webhook endpoint depends on the third party tool from which events are initiated for example, amazon simple notification services (sns) uses basic authentication for webhooks other tools, such as jira software, use no authentication