Webhooks

In this article, we will detail how to set up a Webhook to automate your data.

Webhooks are a useful function that allows you to automate your data from Salesfire to an Endpoint e.g. your marketing software.  A webhook is primarily acting as a link between two chains, a non-invasive integration that is straightforward to set up.

In your Dashboard, go to the Preferences section using the left-hand navigation. Click 'Webhooks' which gives you the below page:

Screenshot 2021-06-02 at 09.39.35

This gives you the below window:

 

Give the Webhook a name and provide the Webhook URL  from your webhook partner e.g. AppRelay.co.uk or Zapier.com then click 'Add'. This will set up the webhook and will look something like this (this is purely an example and does not contain an account-specific webhook URL. This can be seen further below):

The default setting will automatically set the status to active.

Now, go to the lists section of the admin located in the navigation of your dashboard:

Screenshot 2021-06-02 at 09.42.59And click the settings button which will give you the above window pop up.  Now click the X box next to the webhook and save.  This will now send each piece of data or email address etc to the Webhook.  

To check to see if the data is passing from Salesfire to the Webhook provider e.g. AppRelay then you can return to the preferences page and access the webhook from the left-hand navigation and click view log as below:

This will then show you each event (or data) that has passed to the Webhook e.g.

The status 200 as shown above is the code shown for each event that has successfully passed.

Clicking view attempts will show you the payload data that is being passed.  

Note:  We only guarantee that the data is passed from Salesfire to the Webhook provider.  If the data is not being passed to the endpoint e.g your marketing suite then this issue needs to be picked up with either of the two fore mentioned.  We can't advise on 3rd party software. If there is anything other than a 200 response code then please contact our support team.

 

Webhook integration error messages:
If you come across any of the following errors, please seek advice from your Webhook provider or the endpoint the data is stored within to remedy the issue. 

Potenital Error Codes:

404 Not Found The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

402 Payment Required

500 Internal Server Error A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501 Not Implemented, the server either does not recognize the request method, or lacks the ability to fulfil the request. Usually, this implies future availability (e.g., a new feature of a web-service API)