# Webhook

## Introduction

The Webhook feature responds to real-time events from external applications. Webhooks are a powerful way to initiate workflows based on specific actions, such as the creation, updation, or deletion of data in connected applications like Microsoft Dynamics CRM Online, or QuickBooks Online.

By configuring Webhook Subscriptions, you can have your workflow triggered automatically when certain events occur in these external systems. This eliminates the need for manual intervention and allows for seamless integrations between different platforms, ensuring that your workflows stay up-to-date with the latest changes in real time.

In the Webhook section of DBSync Cloud Workflow, select the triggering application (like Microsoft Dynamics CRM Online or QuickBooks Online), choose the objects (for example, Account, Invoice, etc.) to initiate the workflow, and define the specific operations (create, update, or delete) that will trigger the webhook. Click **Subscribe** to complete the configuration.&#x20;

Once done, the webhook will listen for these events and activate the corresponding workflow whenever the specified conditions are met.

<figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FnbvRYKd3uH2tmGbVhb6o%2Funknown.png?alt=media&#x26;token=0d1fe4df-450b-4a3c-8d55-6035835411d2" alt=""><figcaption></figcaption></figure>

## Key Operations

The following fields are available within the Webhook tab.

<figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FTu1FIFu7Vq17ZRo1AyPd%2Funknown.png?alt=media&#x26;token=437fa2b5-06b3-4c01-a231-bb01cfcc83d2" alt=""><figcaption></figcaption></figure>

**Triggering App**: This allows you to select the app that will trigger the webhook.\
**Subscribe**: After selecting the required app and object, click **Subscribe** to initiate the webhook subscription.

* **Functionality**: Once you click **Subscribe**, it triggers the webhook to start listening to the selected app for the specified object and operations, making the system respond to these events by triggering workflows.

**Object**: This lists the available objects for the selected application. These objects represent the entities or data structures that can trigger the webhook.

* **Example**: In the screenshot, various objects are listed, such as Bill Payment, Account, and Class.
* **Functionality**: Check the boxes next to the objects you want to subscribe to. These objects will be monitored for changes or updates.

**Operation:** For each selected object, this column allows you to specify which operations should trigger the webhook. The Operation options include:

* **Insert**: The webhook will be triggered when a new record is created for the selected object.
* **Update**: The webhook will trigger when an existing record is updated.
* **Delete**: The webhook will trigger when a record is deleted.
* Functionality: You can choose multiple operations (**insert**, **update**, **delete**) for each object. For instance, in the Account object example, the webhook is set to trigger on insert, update, and delete operations.

**Additional Object Examples**: In the screenshots, objects like **Account**, **Bill Payment**, and **Class** are listed, showcasing different QuickBooks Online objects that can be subscribed to for webhook triggers.

* **Functionality**: You can select multiple objects and operations, allowing the webhook to listen for changes across various data points within the chosen application.

<figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FQ5PnTHEQMFPMoOK97pDR%2Fimage.png?alt=media&#x26;token=9fe8286f-cdde-420b-a8c2-0a86f787501c" alt=""><figcaption></figcaption></figure>

**Operations Checkboxes**: For each object listed in the **Object** column, you can choose which operations (insert, update, delete) should trigger the webhook. You can enable or disable these operations based on your needs.

* **Functionality**: Click to select/unselect checkboxes corresponding to the operations you want the webhook to listen for. For instance:
  * For the **Account** object, check i**nsert**, **update**, and **delete** checkboxes to trigger the webhook whenever an account is inserted, updated, or deleted.

<figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2Fmc2wk6n3nnMNOGGK2dSt%2Funknown.jpeg?alt=media&#x26;token=e3cb1a1b-c92a-490b-a9fa-bc97efc20c32" alt=""><figcaption></figcaption></figure>

#### Additional Features

* Search: If you have a long list of objects, use the search option to quickly find specific objects to subscribe to.
* Modify Subscription: Depending on your system’s design, modify your subscriptions by checking/ unchecking operations or objects.

The Webhook tab helps configure automatic triggers based on events in external applications, like Microsoft Dynamics CRM Online and QuickBooks Online. By subscribing to specific objects and operations, you can set up webhooks that allow your workflows to be triggered in real-time whenever the chosen events occur, helping you automate and streamline processes more effectively.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mydbsync.com/cloud-workflow/2026_create-your-workflow/flow-management/webhook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
