Configure webhooks
Prerequisites
You must have Read and write permission for Webhook config in the Developer tools.
To enable a webhook to send payloads using a Bearer token:
Go to > .
Select .
If you would like webhooks to be sent in batches, select . We recommend activating batching.
Select from the Auth type drop-down menu.
Add your secret to the field. Ensure that your integration checks the secret when webhook payloads are received. This will make sure a malicious third party can't intercept the payload and provide you with false information.
Add the endpoint you want to receive payloads to the field.
Select the webhook events you want to listen to from Enabled events. You can select as many as you like.
Select .
To enable a webhook to send payloads using OAuth client credentials:
Note
The OAuth client credentials only work with the Salesforce Connector.
Go to > .
Select .
If you would like webhooks to be sent in batches, select . We recommend activating batching.
Select from the Auth type drop down menu.
Add your Client ID to the field.
Add your secret to the field. Ensure that your integration checks the secret when webhook payloads are received. This will make sure a malicious third party can't intercept the payload and provide you with false information.
Add your Token URL to the field.
Add the endpoint you want to receive payloads to the field.
Select the following webhook events from Enabled events.
Note
Only the following webhook events will process. The Salesforce Connector will ignore any other selected webhook events.
Select .
Batching
When batching is enabled, multiple webhooks are delivered in a single request.
Webhook messages are added to a queue and Maxsight delivers the first 100 messages in the queue approximately every 0-10 seconds.
We recommend that high-volume clients enable batch processing. Without batching, webhooks are sent one at a time in the order they were triggered.