# Webhook

The **Webhook** tool allows you to trigger a MESA workflow from a third-party service. It can similarly be thought of like a notification. It lets a third-party service start a workflow in MESA when something happens in your third-party service.

With Webhook, you can create a chain reaction of events that allows you to focus more on your store than work on repetitive tasks.

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

## Set up a Webhook trigger <a href="#setup" id="setup"></a>

When creating a new workflow, you can select the **Webhook** tool as the trigger.

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

## Add a Webhook URL to your app that you want to connect with <a href="#webhook-url" id="webhook-url"></a>

Hit the Copy button to copy the link from the Webhook URL field and add it to your app in order for MESA to receive notifications from your third-party application.

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

## Send data to a webhook <a href="#sending-data" id="sending-data"></a>

After adding the Webhook URL to your app, data coming from your third-party application is sent to MESA's Webhook trigger in the form of a JSON payload.

## Manually run your webhook <a href="#testing" id="testing"></a>

You will want to manually run your Webhook trigger by sending a notification from your third-party application.

To check the payload coming from your third-party application, click on the **Activity** tab of your workflow in the MESA dashboard. Then expand the recent run of your workflow, click the 3 vertical dots on the right side of the **Webhook** text, and then click **Request Details**.

![](/files/VdehOe9EQ2meGwYFNU99)

On subsequent steps, you can create variables that reference the data that is received in the Webhook trigger. For example, you can use the variable: `{{webhook.team_domain}}`

## Limitations <a href="#limitations" id="limitations"></a>

You are unable to send data back to the request. MESA can only receive data coming from the third-party application.

Variables will not be selectable from the Webhook trigger from the Variables menu on subsequent steps. You will need to manually create the variables following the format: `{{webhook.team_domain}}`

## Examples and use cases <a href="#examples" id="examples"></a>

**Webhook** provides the ability to integrate or provide additional capabilities with third-party applications that are currently not supported in MESA. For example, you can trigger a workflow using a Slack command.

![](/files/JTcOmv1OJegrfo2zpLg6)

![](/files/dqDmqvgnDuwBY2EKLtk7)

After creating an app in Slack and adding a command, you can add the Webhook URL from your MESA workflow to the settings of your Slack command.

When messaging on Slack, you can type in the command and hit Enter to trigger the workflow in MESA.


---

# 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.getmesa.com/tools/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.
