> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/workflows/webhooks.md).

# Webhooks

Webhooks are a powerful way for apps to send automated messages or information to other apps. Think of webhooks as similar to SMS notifications: when a specific event happens, an automated message is sent to notify or trigger an action in another app.

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

In this example, let’s say you want to be notified in Microsoft Teams whenever a new order comes in. Using a webhook, you can set up an automated notification in your Teams channel that includes relevant information about the order.

When a new order is created, the Equipme Automation App's webhook component will capture this data and trigger the **SendChannelMessage** component in Microsoft Teams. This allows you to instantly notify your team of new orders and share details, helping them stay up-to-date and respond efficiently.

**Using Webhooks in the Equipme Automation App**

In the Equipme Automation App, you’ll find the Webhook component under the "HTTP" utility. This component allows you to connect your workflows with other apps through webhooks, making it easy to pass information between different systems.

To set up your webhook flow:

1. **Add the Webhook component** to your flow from the HTTP utilities.
2. **Configure the Webhook URL** – this is the unique URL that other apps (such as your ordering system) will use to send data when a new order is created.
3. **Set up the SendChannelMessage component** – connect this component to the webhook so that it receives data from the new order and sends a notification in Teams.

**Key Terminology for Webhooks**

* **Webhook**: The tool that allows apps to send automated messages or data to each other.
* **Webhook URL**: The URL endpoint that receives data. This is the link to which other apps send information.
* **Response**: This feature lets you send a response back to the app that sent data to your webhook. Instead of using a direct response, the Equipme Automation App recommends using the "Response" component to keep flows organized.
* **Trigger**: This sends data received by the webhook to other components or apps in your flow, activating the next steps in your automation.
* **Immediate Response**: This setting allows an instant response to the app that sent the webhook request, useful if a quick acknowledgment is needed. However, if you’re planning to use the RESPONSE HTTP component later in your flow, this option should be turned off.

By integrating webhooks into your flows, you can create a dynamic automation experience. Webhooks provide a flexible way to automate notifications and keep your team informed in real-time through the Equipme Automation App.


---

# 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 dynamically by asking a question.

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

```
GET https://hub.equipme.io/documentation/automation/workflows/webhooks.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.