> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/populating-salesforce-data/platform-events-flexible/orderevent-flow.md).

# Listen to OrderEvent Flow

**LFS Version requirement:** 12.64 or higher

Encouraging the use of our product, especially platform events, is crucial. Some users may hesitate to adopt platform events due to unfamiliarity, but we believe that providing the right resources can close this knowledge gap. By addressing these issues, we aim to help more users fully utilise platform events, enhancing their overall experience with our product.

The package includes a new flow designed to respond to the **i42as\_\_OrderEvent\_\_c**.

This flow is easily customisable by administrators, allowing for flexibility. Importantly, it starts in an inactive draft state, enabling administrators to adjust the logic to their needs before activation. Once tailored, the flow can be activated ensuring smooth integration of platform events into existing processes.

## How to use the flow?

First, you need to add the logic you want to run when an event is received. Then you will only need to activate the updated flow version.

This flow is auto-launched which means that as soon as you **activate** it, it will listen to the events of i42as\_\_OrderEvent\_\_c type on the background and any time Limio publishes an event of this type, it will get evoked executing the defined logic.

In our example draft flow, we mapped event's order type value to the description of an asset record.

**Note**: this is for example purposes only and needs to be updated to meet your business case.

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

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

## What fields does the event include?

The event's data model is available in the platform event definition in the setup. Field mappings for each order type are outlined in this document: [Platform Events Definitions](/integrations/populating-salesforce-data/platform-events-flexible/platform-events-definitions.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 dynamically by asking a question.

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

```
GET https://docs.limio.com/integrations/populating-salesforce-data/platform-events-flexible/orderevent-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
