Skip to main content
Version: 2.220.0

Overview

Webhooks provide an efficient way to receive notifications whenever a new resource is created or an escalation occurs concerning your resources. They deliver data to your application instantly as the event happens, ensuring you receive information in real-time.

When a webhook is triggered, a JSON object containing all relevant details about the escalation is sent. This includes the type of escalation, information about the resource, and other metadata. The EasyLife 365 Engine forwards these escalation details to the specified webhook URLs in your action's webhook settings via an HTTP POST request in JSON format.

Types of Events​

  • Approvals: These webhooks activate after approval actions occur or when you need to return a list of custom approvers (Learn more).
  • Provisioning: These webhooks are triggered when a resource is created. Configuration options in templates or provisioning actions allow you to customize notifications according to your specific needs (Learn more).
  • Metadata: These webhooks are triggered when a resource's metadata is updated in the EasyLife 365 app. Configuration options in templates or provisioning actions allow you to customize notifications to meet your specific needs (Learn more).
  • Escalations: These webhooks are set off following the escalation of a policy.

Failure​

If EasyLife fails to call your endpoint, it will attempt up to 3 times before ceasing any further attempts.

Testing webhooks​

What if you want to get started with webhooks, but don't have a server (that's open to the Internet) set up to receive them? What if you're troubleshooting a webhook-based system, and you just want to see whether EasyLife 365 successfully sends out webhook requests?

You can use the website https://webhook.site to create a webhook. This website will allow you to create a webhook and monitor the data sent by the EasyLife 365 Engine to it.

tip

Take note to keep the tab open in your browser. Each time you visit https://webhook.site/, even with a previously generated URL, it will always generate a new webhook. This is done to protect your data and privacy. Simply put - nobody else can see your data.