> 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/management-dashboard/events/working-with-event-data.md).

# Working with Event Data

If you use dots in event names, for example `tenant.created`, you need to correctly reference such event types to ensure seamless integration between Emporix Orchestration Engine and Make or other third-party platforms.

You may need to reference such event types it in the following situations:

* When using the OE API process run search endpoint.
* When using the search process run module in Make.
* In other places in Make, when referencing the event type as an attribute of a payload.

To reference an event type with a dot in its name, enclose the event type name in backticks (backquotes) **\`\`**:

```
`tenant.created`  
```

## Usage examples

### OE API Execution Run Search Endpoint

When using the OE API process run search endpoint, ensure that you enclose the event type name in backticks.

For example:

```
{
    "eventType": "`tenant.created`"
}
```

### Make integration

When working with Make, enclose the event type name in backticks when using the search process run module or referencing the event type as an attribute of a payload.

For example:

* In the search process run module:

  ```
    {
        "eventType": "`tenant.created`"
    }
  ```
* When referencing the event type as an attribute of a payload:

  ```
    {
        "eventTypeAttribute": "tenant.created`.attribute"
    }
  ```

Using backticks to enclose event type names with dots, ensures compatibility with Make and other third-party platforms. By following this convention when referencing these event types, you can maintain seamless integration and prevent potential issues during the processing of your workflows.


---

# 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://developer.emporix.io/oe/management-dashboard/events/working-with-event-data.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.