> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/oe-user-guides/management-dashboard/events.md).

# Events

A value stream can react on an action (event) happening in internal or external systems.

External events work as triggers for value stream to run or wake up sleeping processes. These events, such as notifications regarding stock levels, quote requests, and many others, are transmitted as authenticated webhooks to a pre-configured Orchestration Engine event-receiver endpoint. When receiving these notifications, the system interprets them and initiates, or wakes, relevant value stream accordingly. This approach enables real-time adaptation and decision-making, allowing businesses to efficiently manage resources and respond to changing conditions in their operational environment, creating business agility.

OE is schema-less, it utilizes the Cloud Event specification for both receiving and sending events. This framework enables OE to seamlessly gather event information from designated endpoints responsible for transmitting such data. By adhering to this specification, OE ensures efficient and standardized communication, facilitating seamless integration with various systems and endpoints.

For details about events in OE, check the following documentation:

* [Events Registry](/oe-user-guides/management-dashboard/events/event-registry.md)
* [Events Log](/oe-user-guides/management-dashboard/events/event-log.md)
* [Cloud Events in OE](/oe-user-guides/management-dashboard/events/cloud-events-in-oe.md)
* [Events Authentication and Configuration](/oe-user-guides/management-dashboard/events/events-configuration.md)
* [Working with Event Data](/oe-user-guides/management-dashboard/events/working-with-event-data.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://developer.emporix.io/oe-user-guides/management-dashboard/events.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.