Easily Integrate Drift.com Webhooks with your application.


Steps to receive Drift.com Webhooks

  • Sign up for your free Hooky account.
  • Create a new Webhook Source, and select Drift.com. 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 Drift.com, 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 Drift.com webhooks into your application.

Integrating Drift.com Webhooks Using Javascript

Integrating Drift.com 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 Drift.com Webhooks Using Ruby

Integrating Drift.com 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 Drift.com Webhook Authentication

Here's how it works

Supported Drift.com Webhook Events


A contact added their email in chat


A new message was created


A new command message was received. Currently these begin with a slash / - ex: /msg. This is a filtered, lower access, version of new_message. Recommended if your app only cares about a trigger phrase being sent in chat.


A new conversation was started. This explicitly looks at conversations not started by bots - i.e. a site visitor interaction with a welcome message.


The status of the conversation has changed. deprecated - use conversation_push or one of its source events


A conversation has not seen activity after a configurable period of time.


Indicates that a conversation is ready to be consumed by listeners via a manual user action.


Combines events that indicate conversations are ready for consumption (conversation_manual_push and conversation_inactive)


Participants were added to a conversation


Participants were removed from a conversation


A button was clicked in a conversation. The payload will include the contact ID.


This will fire whenever a goal is met with a previously identified contact (i.e. a site visitor that provided their email or is known in the Drift UI). The payload will include the contact ID.


A user unsubscribed from all emails - this is invoked whenever someone opts out of email communication (either manually, or by the API).


A meeting was booked by a contact or site visitor with a member of your team - scheduled by the bot or via your calendar schedule page. Requires calendar connection in Drift.


A previously booked meeting was either rescheduled or canceled.


A contact record has been updated in Drift


A user requested a GDPR-deletion of a contact from drift privacy settings or the API.


A Drift user (organization) disconnected your app.


A Drift user's availability has been changed.


A phone number was captured in a conversation


A Drift user completed call with Chat to Call