> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/bot-studio/triggers/on-webhook.md).

# On Webhook

On Webhook is a bot trigger that lets DoubleTick start a journey and send platform event data whenever an external system or DoubleTick event calls a webhook URL.

**On Webhook** starts a bot journey when an external system sends data to a **webhook URL**. A webhook is a URL that receives event data automatically. Use this trigger to connect **external events** or **platform updates** with automation workflows.

#### What's covered

* [Where to use this trigger](#where-to-use-this-trigger)
* [How webhooks work in DoubleTick](#how-webhooks-work-in-doubletick)
* [How to use it in DoubleTick](#how-to-use-it-in-doubletick)
* [Key takeaways](#key-takeaways)
* [Frequently asked questions](#frequently-asked-questions)
* [Related articles](#related-articles)

#### Where to use this trigger

Use this trigger when you want DoubleTick to capture events and send them to another tool or system, such as:

* Saving **message delivery logs** in Google Sheets.
* Tracking template status: **Sent**, **Delivered**, **Read**, and **Failed**.
* Capturing **conversation assignment** updates.
* Sending platform activity data to your **CRM** or reporting tools.
* Building custom integrations beyond **Bot Studio**.

This trigger is especially useful for teams that want automated reporting or system-level tracking.

#### How webhooks work in DoubleTick

When you create a bot journey using **On Webhook**, DoubleTick provides a **webhook URL**. Copy this URL to the system that needs to call it. When the selected event occurs, DoubleTick sends the full event information in the webhook response.

#### How to use it in DoubleTick

1. **Copy the webhook URL**: \
   Open **Bot Studio**, create a journey, select **On Webhook**, and copy the generated URL.
2. **Add the URL in DoubleTick**: \
   Open **Settings → Webhooks**, select **Create Webhook**, and paste the URL into **Webhook URL**.
3. **Select an event**: \
   Choose an event, such as **Message Status Update**, **Conversation Assigned**, or **Incoming Message Received**.
4. **Save the webhook**: \
   Click **Save**. DoubleTick then sends updates whenever that event occurs.

For API registration and Postman testing, see [How to configure and register a webhook](/bot-studio/triggers/how-to-configure-and-register-a-webhook.md).

For example, a business wants a complete history of all templates sent from DoubleTick, including Sent, Delivered, Read, and Failed. They copy the On Webhook URL from Bot Studio, paste it in Settings, Webhooks, select the event Message Status Update, and save the webhook. Now, whenever a template is sent, a log is created immediately when it is marked as Sent, another log is created when it becomes Delivered, and another update comes when it is Read. These updates can then be captured in tools like Google Sheets for reporting and tracking.

#### Key takeaways

* **On Webhook** sends real-time event data through a generated webhook URL.
* It supports **Message Status Update**, **Conversation Assigned**, and **Incoming Message Received**.
* Use it for logging, reporting, and integrations with **CRMs** or **Google Sheets**.

#### Frequently asked questions

<details>

<summary>Where do I get the webhook URL to use with this trigger?</summary>

Bot Studio generates it automatically when you add the **On Webhook** trigger to a journey.

</details>

<details>

<summary>Which events can I select for a webhook?</summary>

You can choose events such as **Message Status Update**, **Conversation Assigned**, and **Incoming Message Received**.

</details>

<details>

<summary>Do I need to register the webhook separately for platform events to reach it?</summary>

Yes. Add the copied webhook URL under **Settings → Webhooks**, then select the event it should listen for.

</details>

<details>

<summary>Can I use this data outside DoubleTick?</summary>

Yes. Webhook event data can be pushed into **Google Sheets**, **CRMs**, or other internal systems.

</details>

#### Related articles

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/GMHcI9YuwK3LjoVY2VJ3" %}
[How to configure and register a webhook](/bot-studio/triggers/how-to-configure-and-register-a-webhook.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/1IHB1sMp9nKMTRudNUZ8" %}
[Understanding and Using Webhooks in DoubleTick](/webhooks-and-public-api/webhooks/understanding-and-using-webhooks-in-doubletick.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/pzfwSyD9HYHWwTrfxkqr" %}
[How to use Message Status Update Webhook](/webhooks-and-public-api/webhooks/how-to-use-message-status-update-webhook.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/bot-studio/triggers/on-webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.