Easily Integrate the ckeditor storage.document.removed Webhook into your application using Javascript, Ruby, and other frameworks.
Triggered when the document data is removed from the storage. The document can be removed using a REST API call (see the Documents REST API section) or when the document storage feature is being turned off. After you disable the feature in the CKEditor Ecosystem customer dashboard for SaaS or in the Management Panel for On-Premises, all stored documents are removed.
Steps to receive the Ckeditor storage.document.removed Webhook
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select ckeditor. This will be the endpoint that receives the Ckeditor storage.document.removed webhook on behalf of your application, and forwards them using the unified SDK.
- Once the storage.document.removed webhook is received from Ckeditor, you'll see the payload under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in Ruby or Javascript, and start receiving webhooks.
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select ckeditor. This will be the endpoint that receives the Ckeditor storage.document.removed webhook on behalf of your application, and forwards them using the unified SDK.
- Once the storage.document.removed webhook is received from Ckeditor, you'll see the payload under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in Ruby or Javascript, and start receiving webhooks.