Understand the webhook world

Transcript

Any application or software platform that is connected to the internet and allows the sending of HTTP requests can send webhooks to Workfront Fusion. Some app connectors already available within Fusion may have some modules which create and register a webhook automatically. Others will create webhooks and provide instructions on how to register the webhook with the software platform or third party service. Finally, you can also create generic webhooks and use the corresponding URL to trigger the scenario, which we’ll demonstrate in the next walkthrough exercise. Webhooks can be set up to be either responsive or passive. A responsive webhook can return some specific data to the calling third party service. A passive webhook will by default return either a 200 HTTP status code with the simple text accepted in the body, or a 400 code, meaning that the queue is full.

On that note, it’s important to note that once a webhook is established, it will be associated with a queue, which you can find in the left-hand panel of the Fusion features. It’s also important to know that until a scenario containing a webhook is activated, incoming deliveries of data will be stored in the queue until able to be processed. When working with multiple scenarios using the same webhook, all scenarios share the same queue and must all be activated, otherwise the queue will fill up with incoming data. If you clone a scenario and want to use a different webhook and queue, you will need to update the clone scenario’s webhook. -