> For the complete documentation index, see [llms.txt](https://asperazera.gitbook.io/simple-event-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asperazera.gitbook.io/simple-event-system/quickstart/send-event.md).

# Send Event

The **Send Event** node is the primary way to broadcast a message.

***

### Step 1: Add the Node

Open any Blueprint (Actor, Widget, GameInstance, etc.) where you want to trigger an event.

1. Right-click on the graph.
2. Search for **"Send Event"**.
3. Select the function under the **Simple Event System** category.

<div align="left"><figure><img src="/files/kR2LjQIH2IAvUoQZtSLT" alt=""><figcaption></figcaption></figure></div>

***

### Step 2: Define the Event Tag

Events in **Simple Event System** are identified by **Gameplay Tags**.&#x20;

{% hint style="info" %}
**Tip:** You don't need to define them in Project Settings beforehand; you can create them on the fly.
{% endhint %}

<div align="left"><figure><img src="/files/k0ZHC6tdUzGFO8ibcNcx" alt=""><figcaption></figcaption></figure></div>

1. Click the **Event Tag** dropdown on the node.
2. Click <mark style="color:$success;">**Plus**</mark> Icon.
3. Type the name of your event (e.g., `TriggerOverlap.Start`).
4. Select **Source** as `DefaultGameplayTags.ini`.
5. Click **Add New Tag** to save it.

<div align="left"><figure><img src="/files/siEDoURFSIbTF9kNLovh" alt=""><figcaption></figcaption></figure></div>

***

### Step 3: Select the Tag

Once added, ensure the tag is selected in the dropdown. Your node is now ready to fire!

<div align="left"><figure><img src="/files/Kr0lcihkBcpX9t7sO4FR" alt=""><figcaption></figcaption></figure></div>


---

# 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://asperazera.gitbook.io/simple-event-system/quickstart/send-event.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.