> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/integrations/webhook.md).

# Webhook

Forward device readings from Brewfather to your own endpoint using webhook integration.

Use webhook forwarding to send device readings from Brewfather to your own endpoint.

To send RAPT device readings **to Brewfather**, follow the [RAPT Brew data stream setup](/integrations/rapt.md#send-device-readings-to-brewfather). The webhook settings on this page forward readings **from Brewfather** to another service.

## Configure a webhook

1. Open **Settings**.
2. In **Power-ups**, enable the integration you want to use.
3. Click **(configure webhook)** for that integration.
4. Set:
   * **Enable webhook**
   * **URL**
   * **Format** (`Processed` or `Raw`)
5. Click **Save**.

## Format options

* **Processed**: Sends the reading as stored/processed by Brewfather.
* **Raw**: Sends the reading payload as received from the device/integration.

## Delivery behavior and limits

* Brewfather sends an HTTP `POST` when the device sends a value.
* Delivery is limited to at most **once every 15 minutes per device**.
* The webhook URL must be valid.
* Brewfather domains are blocked as webhook targets.

## Integrations with webhook configuration in current UI

* Tilt Hydrometer
* iSpindel
* Custom Stream
* RAPT Brew
* Brewbrain Float Hydrometer
* Plaato Airlock
* DIY Floaty Hydrometer
* BrewPiLess

## Troubleshooting

* No forwarded data: verify the power-up is enabled and the device is actively sending readings.
* Save fails: re-check URL format and make sure it does not point to a Brewfather domain.
* Need batch JSON export payloads instead of reading events: use [Custom Endpoint](/integrations/custom-api-endpoint.md).

## Related docs

* [Custom Endpoint](/integrations/custom-api-endpoint.md)
* [Devices](/devices.md)
* [Settings](/settings.md)


---

# 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://docs.brewfather.app/integrations/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.