HubSolv comes with the ability to accept notifications from other services such as a dialler to then interact with the system to perform changes, these could be anything from status changes which then can trigger workflows and emails to be sent out.
An example would be a dialler keeping the statuses on HubSolv in sync so they're both the same.
Notifications
URL: https://xxxxx.hubsolv.com/api/notification
Fields:
- HUBSOLV-API-KEY
- clientid
- notification_from
- notification
HUBSOLV-API-KEY is standard across all API routes into HubSolv, this is required to authenticate you.
The clientid should just be the integer number for the client record.
Notification_from should simply be where this notification is coming from, such as Company Ltd
notification should be what is actually occuring. This should be following this json convention:
{"statusid":"ID of status","status_shortname":"Anything you want"}
Notification Data
The notification data can hold JSON, an example would be the following:
{"statusid":"ADD","status_shortname":"ADD LEAD SUCCESSFUL"}
HubSolv can then target the specific keys such as statusid or status_shortname and use these as conditions for further key refinement on triggers. So if the statusid came through and was ADD it would change the status of the case to Pushed to X - Successful as an example.
Comments
0 comments
Please sign in to leave a comment.