Gruveo supports the ability to post call information to a custom webhook at the end of each call in your Gruveo account. You can use this feature with Zapier webhooks or a custom backend implementation to trigger actions for each incoming Gruveo call. The actions can include adding a record to your CRM, storing the call details in an internal call log, and others.
Below is a sample of the data posted to the webhook.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 | { “timestamp”: 1598615831871, “maxParticipants”: 2, “duration”: 183, “link”: “@acme.sales”, “location”: “Greece”, “resolution”: “answered”, “user”: { “name”: “John Smith”, “email”: “john@acme.com” }, “tracking”: { “customer_id”: “14810” }, “waitingTime”: 5, “account”: { “id”: “9cf7336a-e40e-4628-bdac-4370298ccf14”, “organization”: “Acme Corp.” }, “assignedUsers”: [ { “name”: “John Smith”, “email”: “john@acme.com” }, { “name”: “Patty Jones”, “email”: “patty.jones@acme.com” } ] } |
The fields are as follows:
timestamp– UNIX timestamp for the call in millisecondsmaxParticipants– the maximum number of participants reached during the call. This would be 2 for a one-on-one call and more for a group conversationduration– call duration in secondslink– the permanent link calledlocation– approximate caller location (derived from their IP address)resolution– whether the call wasmissed,answeredordeclineduser– contains name and email of the user who answered the calltracking– any custom parameters passed in the permanent linkwaitingTime– how long the caller waited before the resolution, i.e. hanging up or their call being answered/declinedaccount– contains ID and the organization name of the Gruveo accountassignedUsers– a list of account users who were assigned to the permanent link at the time of the call.
Passing Custom Parameters in the Permanent Link
You can make a permanent Gruveo link carry with it any additional information about the call that you collect outside of Gruveo. For example:
https://www.gruveo.com/@acme.sales?customer_id=14810
Any custom GET parameters you pass this way (in our case, customer_id) will be reported in the webhook under the tracking field.
Verifying Data Authenticity
For each webhook-enabled Gruveo account, we generate a random unique key that is used for computing the SHA-256 HMAC of the webhook’s request body. This HMAC is then sent in the X-Gruveo-SHA256-HMAC HTTP header of the request. You can verify the authenticity of the data by computing the SHA-256 HMAC of the request body and comparing it against the value passed in the header.
The signing key is communicated to you securely as part of the webhook setup.
Setting up the Reporting Webhook
If you’d like to set up webhook reporting for your account, please have your webhook URL ready and get in touch with us.