Easily Integrate Talkjs Webhooks with your application.


Steps to receive Talkjs Webhooks

  • Sign up for your free Hooky account.
  • Create a new Webhook Source, and select Talkjs. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
  • Step 1
  • Step 2
  • Once a webhook is received from Talkjs, you'll see it under the Live Logs section of your webhook source.
  • Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Save countless hours integrating Talkjs webhooks into your application.

Integrating Talkjs Webhooks Using Javascript

Integrating Talkjs webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.

Integrating Talkjs Webhooks Using Ruby

Integrating Talkjs webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.

Configuring Talkjs Webhook Authentication

Here's how it works

Supported Talkjs Webhook Events


Occurs when a user is created in TalkJS backend.


Occurs when a user is updated in TalkJS backend.


Occurs when a message is sent in a conversation.


Occurs when another user in the same conversation receives the message in the chat UI. This event will get sent at most once for every member of a conversation other than the sender.


Occurs when the content or metadata of the message is updated. Note that message.updated is not called when the message has been read (message.read).


Occurs when the message has been deleted.


Occurs when a conversation is deleted via the REST API


Occurs when TalkJS decided that a notification is to be sent to a user. In particular, this is the case when both of the following conditions are met:


Occurs when TalkJS has actually sent the aforementioned notification. May be triggered more than once for each notification if TalkJS notifies a user both via email and SMS. Does not get triggered for mobile push notifications.


Occurs when a email was successfully delivered.


Occurs when an email was not successfully delivered. It is triggered for bounces and spam complaints that resulted from outgoing email.


Occurs when a user opens an email notification in an email client. Note that it may not always be triggered, because user’s email client might be blocking tracking pixels.


Occurs when a user clicks a link inside an email notification.