# 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.