Our webhook API is a simple, industry-standard method of linking different systems together to let you send out an NPS survey in response to an event on a different system.
For example, you could:
Link your helpdesk system to SightMill using webhooks to send a survey after a support ticket is closed.
Read moreOr you could send a survey when a purchase is made on your website.
Read moreOr send a survey response from a customer to a Slack channel.
Read more
To link two systems using a webhook, the receiver software provides the sender with a URL. For SightMill, we provide a unique URL for each account and project to receive webhooks. You'll find this in your Project/Settings - Webhooks menu.
Webhooks functions
The SightMill webhooks support lets you:
- send an email survey
- send an SMS survey
- add a new contact (that is then included in a scheduled survey)
In addition, the email webhooks function supports a delay feature - so you can setup your email to go out a certain number of hours after the webhooks request is received.
Webhooks endpoint / URL
When SightMill sends data, your receive application will provide a unique URL that you copy and paste in to SightMill. You'll find this in the Project/Settings - Webhooks menu
Webhooks data / payload format
The data that is exchanged is in JSON format and contains a range of fields including the NPS score, verbatim comments, tags, etc.
For example, if linking SightMill to Slack so that SightMill can post new survey results in real-time to your Slack channel, you would copy your Slack unique webhook URL into the integrations setup for your project in SightMill. Read more here.
The format for the information your CRM or application sends across to SightMill via a webhook needs to be in a specific format with nine fields supported:
- firstname,
- surname,
- email address (or phone number for an SMS survey)
- segment,
- spend,
- product,
- tag,
- owner
- id (this is a unique identifier for this contact - if your system does not generate unique IDs then repeat the email address or phone number here)
The only two that MUST be included are the id field and the email address (or phone number for SMS) field.
Here's a simple example to send an email survey:
{"Email":"
test@example.com", "FirstName":"John", "LastName":"Smith", "id":"12345"}
or with additional meta fields:
{"Email":"
test@example.com", "FirstName":"John", "LastName":"Smith", "segment":"legal", "spend":"$1500", "product":"Gold-plan", "id":"12345"}
NOTE. ensure that the contact has its own unique id field - normally a CRM or helpdesk system will have an ID field, otherwise repeat the email address or phone number here)