Introduction to Webhooks

Content Item Publishing Webhooks

By default, you have one default outgoing Webhook trigger available for your Chisel environment, which we encountered in the Site Settings Overview.

This webhook will be fired whenever your content entry is initially published, or when it's publishing after being edited.

Webhooks in Parse Dashboard

In addition to the standard webhook, we also have access to a number of available webhook triggers - and a helpful administrative UI for adding these in the Parse Dashboard interface.

Open up your Parse Dashboard and locate the Webhooks menu item in the left navigation.

https://s3.amazonaws.com/forge-documentation/webhooks.png

Click "Create a Webhook"

You can now complete your Webhook create form with the details of your webhook.

https://s3.amazonaws.com/forge-documentation/webhook-form.png

Webhook Type

This declares the event that will fire the Webhook. We can choose a Cloud Code Function or use one of the available triggers.

BeforeSave AfterSave BeforeDelete AfterDelete

The triggers are pretty self explanatory.

Function Name

If you chose the Function type of hook, you then simply add the name of your Cloud Code function

Class Name

If you chose a trigger, then you will need to provide the name of a Class (or specifically, your Models) that you want to be responsible for firing the Webhook.

For example, you could pass _User to take events for User Signups or on one of your particular Content Models ct_...

Webhook URL

This is the endpoint that you will send the hook to as a destination.

Parse-Server doesn't provide a seperate payload body, so you'd most like need to URI encode and add your payload as a request parameter.

Once you have saved your Webhook, you'll see it is made available in the Webhooks list in Parse Dashboard.

https://s3.amazonaws.com/forge-documentation/webhooks-list.png