# Webhooks Automations

<figure><img src="/files/IXXVKuILM70RdpP3NL9P" alt=""><figcaption></figcaption></figure>

**Webhooks Automations** in Tiledesk allow you to expose an automation flow as an HTTP endpoint that can be invoked by external systems.\
They work in a very similar way to **Make.com webhooks**, enabling event-driven integrations, backend-to-backend communication, and custom automation triggers.

A webhook automation acts as an **entry point** into a Tiledesk flow, receiving an HTTP request, processing it through the flow logic, and optionally returning a structured HTTP response.

## Create your webhook

Go in Flows > Automations anche choose "Webhook"

<figure><img src="/files/Vgqu6EwMdOKTMuDTSLzB" alt=""><figcaption></figcaption></figure>

Choose a name for your Webhook

<figure><img src="/files/z8IZUqxa0fT5pNtJb31x" alt=""><figcaption></figcaption></figure>

You are moved to the Webook Design Studio

<figure><img src="/files/VPaex0JvaUiwJAeIvjtI" alt=""><figcaption></figcaption></figure>

When you create a Webhook Automation, Tiledesk automatically generates **two distinct webhook URLs**:

* **Development Webhook URL**
* **Production Webhook URL**

Each URL is tied to the same automation flow but serves a different purpose.

<figure><img src="/files/0eglwK624d3HhQouxYiB" alt=""><figcaption></figcaption></figure>

#### Development Webhook

The **development webhook** is designed for testing and debugging.

Key features:

* Invoking this endpoint allows you to **observe the execution of the flow in real time**
* A **live debug panel** appears at the bottom of the flow editor

<figure><img src="/files/6rijc0JswBveuZjbpWt2" alt=""><figcaption></figcaption></figure>

* You can inspect:
  * Incoming payload
  * Node execution order
  * Variables and intermediate data
  * Errors and exceptions

This makes it ideal for:

* Flow design and testing
* Payload inspection
* Debugging integration logic

#### Production Webhook

The **production webhook** is intended for live environments.

Characteristics:

* No real-time debug panel
* Optimized for performance and stability
* Should be used by production systems and external clients

Once your automation is tested via the development webhook, you can safely switch clients to the production URL.

### Incoming Payload Handling

All data sent to the webhook request is automatically made available inside the flow through the **`payload`** object.

#### Example

If an external system sends the following JSON body:

```json
{
  "name": "Andrea",
  "email": "andrea@example.com"
}
```

You can access these values anywhere in the flow using:

* `payload.name`
* `payload.email`

In the following example we are echoing the name provided in the post payload in the call

<figure><img src="/files/ZCkOFuZ7Gcri61BcvJ70" alt=""><figcaption></figcaption></figure>

### Returning a Response

To return a response to the calling client, you must explicitly use the **Response** action inside the flow.

#### Response Action

The **Response** action allows you to define:

* HTTP status code (e.g. `200`, `201`, `400`, `500`)
* JSON response body

### Fire-and-Forget Webhooks

If **no Response action** is present in the flow:

* The webhook behaves as **fire-and-forget**
* Tiledesk immediately returns a default response to the caller
* The automation continues executing asynchronously in the background

This mode is useful when:

* The caller does not need a response
* You are triggering long-running or background processes
* You want maximum responsiveness on the client side

### Webhook Logs & Administration

Tiledesk provides a dedicated **Webhook Administration** section in the dashboard.

<figure><img src="/files/gYIfZnOcIgdv2QqunPHv" alt=""><figcaption></figcaption></figure>

From this panel you can:

* Monitor **runtime webhook logs**
* Inspect request payloads and execution outcomes
* Temporarily **disable a webhook** if needed (e.g. for maintenance or security reasons)

<figure><img src="/files/Aa53B8iBaeOH7MOCkMHx" alt=""><figcaption></figcaption></figure>

This component is especially useful in production environments to ensure observability and operational control.

### Typical Use Cases

Webhook automations are ideal for:

* Integrating external systems (CRM, ERP, backend services)
* Triggering workflows from third-party platforms
* Receiving events from custom applications
* Building server-to-server automations
* Implementing asynchronous background processing

### Tiledesk Webhook Summary

* Webhooks automations expose Tiledesk flows as HTTP endpoints
* Two URLs are available: **Development** (with real-time debug) and **Production**
* Incoming request data is accessible via the `payload` object
* Use the **Response** action to return custom HTTP responses
* Without a Response action, the webhook runs in **fire-and-forget** mode
* The dashboard provides full monitoring and administrative control

This makes Tiledesk Webhooks a powerful and flexible foundation for event-driven automation and system integration.


---

# 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://guide.tiledesk.com/ai-chatbots-and-automation/automations/webhooks-automations.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.