# Steamworks Event Triggers

{% hint style="success" %}

#### Like what you're seeing?

Support us as a [GitHub Sponsor](/old-kb/where-to-buy/become-a-sponsor.md) and get instant access to all our assets, exclusive tools and assets, escalated support and issue tracking and our gratitude.\
\
These articles are made possible by our [GitHub Sponsors](/old-kb/where-to-buy/become-a-sponsor.md) ... become a sponsor today!
{% endhint %}

##  Introduction

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

The Steamworks Event Triggers component works similarly to Unity's Event Trigger component letting you easily connect to any Steamworks SDK static event quickly and easily. There is no reason to use this component in C# code as all of these events are available on their respective API extensions. This component exists only to expose those events to the Unity Inspector.

## Use

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

Simply click the Add New Event Type and select the event you wish to add

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

When done you can connect objects to the event as you would any other Unity Event. You are not required to use this component to access these events. Each event is also available on related "Managers" such as the [Lobby Manager](/old-kb/old-toolkit-for-steamworks/unity/objects/ui-components/lobby-manager.md) as well as in code via the respective [API extensions](/old-kb/old-toolkit-for-steamworks/unity/api-extensions.md).


---

# 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://kb.heathen.group/old-kb/old-toolkit-for-steamworks/unity/objects/components/steamworks-event-triggers.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.