If you integrate an external system with Adversus, you can receive live information of events by subscribing to webhooks from Adversus, such as information about currently updated leads.

Please note that all webhooks are configured using the Adversus API. We currently support GET-requests (receive a list of active webhooks), POST-requests (create new webhooks), DELETE-requests (delete webhooks), and PUT-requests (modify an existing webhook). For further information, please take a look at the API documentation page.

For certain events, it is possible to extend the emitted webhook post body. This is done by specifying the template property on creating with a JSON object containing the output data using merge-tags. The template will be merged with the lead data when the webhook is emitted, and the result will be contained within the output as the property data.

Merge tags are specified inside the json-template as substrings having the form [fieldId]. These will be substituted by the corresponding lead-data identified by the fieldId.

Currently, only the webhook event lead_saved support the templating system.

Available lead data for templating: [status], [last_called_by], [lead_id]. Here is an example request:

{ 	"event": "adversus-lead-saved", 	
	"email": "[1337]", 		
	"address": "[1338]", 	
	"current_status": "[status]", 	
	"user": "[last_called_by]", 	
	"lead": "[lead_id]", 	
	"status": "[status]" 
Did this answer your question?