# Configurator blueprint API
## Overview
This example walks through the steps of binding runtime gameplay logic to Level or Object Configurator events.
{% hint style="info" %}
Make sure you have set up your blueprint to start receiving events, from within your [level configurat](/realtime-configurator/level-and-object-configurator/level-configurator.md)[or](/realtime-configurator/level-and-object-configurator/level-configurator.md) or your [object configurator](/realtime-configurator/level-and-object-configurator/object-configurator.md).
{% endhint %}
## Switch on configurator key
In most cases you'll want to set up a **Switch on Configurator Key** node to separate logic based on the specific property you are targeting.
1. Right click on the event node and select **Split Struct Pin:**
2. Drag out of Event Data Key and select **Switch on Configurator Event Key**:
3. Select the new node and in it's options assign the correct **Configurator Dataset** asset to it:
4. Your **Switch on Key** node should now be populated with the correct properties.
## Acting on configuration event data
Depending on your property type you have different options for acting on the configuration event data (flowing from the **Event Data** pin).
### Strings and numbers
In the case of strings and numbers, the Event Data Value can be passed directly to the consuming node:
### Enums and booleans
Enum and booleans Configurator values are easy to work with thanks to the **Switch on Configurator enum value** node. Once added, specify the correct Key in its node settings:
### Images
1. Reacting to an Image event type is easy. The Event Data Value can be linked to a **Get Image From URL** node.
2. The bound delegate will fire once the file is downloaded and turned into a runtime texture:
### Triggers
Trigger events do not carry any value, and can be used to fire non-parametrized events. Simply drag off the **Switch on Key** node to listen for Trigger events.
---
# Agent Instructions: 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.odyssey.stream/realtime-configurator/level-and-object-configurator/configurator-blueprint-api.md?ask=
```
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.
