Hey there! Have you ever heard of webhooks? They’re a really useful tool that can help you send real-time notifications of events within tawk.to to external services.
There are three specific events you can configure a webhook for: chat starts, chat ends, and new ticket creation. Whenever one of these events happens, tawk.to can automatically send a notification to an external service like Slack or Zapier.
A webhook is made up of three parts:
A URL you have configured, to which a webhook event will be posted
One or more events, which will be posted to a specified URL
A secret key, which can be used to verify a webhook payload was sent by tawk.to
When a webhook is triggered, a JSON payload specific to the event type will be sent in a POST request to the configured URL.
Managing webhooks is really easy! You can do it right from the tawk.to dashboard in the Admin section. And if you want to learn more, you can check out the tawk.to developer website for more details and example code.
If you add events chatsent and chatreceived, I can build a ChatGPT interface for you so ChatGPT starts getting trained on a property’s questions.
Webhook for each chatreceived and chatsent then sents data to php endpoint, which then feeds to ChatGPT perpetual session, ChatGPT response to chatreceived is returned, human decides if ChatGPT response is good or not, provides human written response, which is sent back to tawk and to GPT for training “Correct answer is: “
Property gets trained to eventually take over basic inquiries.
bump. I agree additional chat message webhooks and endpoint on rest API for posting messages to chat id would really increase the integration of the app.
