> For the complete documentation index, see [llms.txt](https://docs.rulecube.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rulecube.com/v2.5/how-to-guides/webhooks.md).

# Webhooks

### Overview

Webhooks enable near-real-time notifications of events occurring in third-party systems. Instead of wendypolling those systems, many third-party systems have the possibility to register an HTTPS endpoint (a "callback URL") that will POST event payloads to that endpoint when relevant events occur.

Key principles:

* Webhooks can receive HTTPS POST, PUT or GET requests.
* Each webhook request should include a signature for verification (in header or query parameter).
* Delivered messages should include identifiers to support further processing.
* Delivered messages could contain necessary information in both headers, request parameters as well as the request body. Therefor, Rulecube supports handling all those information containers.

***

### Terminology

* Event: A discrete occurrence in a third party system (e.g., order.created, payment.received, message.sent).
* Subscription: A configuration linking an event (or set of events) in the third-party system to a callback URL.
* Webhook definition: the callback URL defined in Rulecube.
* Delivery: An HTTP request made by the third party system to the Rulecube webhook containing event data.
* Delivery ID: Unique ID for each delivery to help with further processing.

***

### Webhook types

Rulecube supports two distinct webhook types:

* Trigger webhooks: supports the execution of a ruleset and/or the start of a workflow using a webhook definition
* Workflow webhooks: supports the creation of a dynamic webhook from within a workflow

#### Trigger webhook definition

As stated above, this webhook type supports:

* the execution of a ruleset
* the start of a workflow

#### Workflow webhook definition

This webhook type is only available within workflows. These - short-lived - triggers are created in a workflow step and will only wait for one callback from a third-party system, e.g. a payment provider.


---

# 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://docs.rulecube.com/v2.5/how-to-guides/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.