# GPIO Config Input Event
Configures in what forms to trigger the **GPIO State Changed** event and in which variables to store the PIN and State values.
Action available for the following operating systems:
### Parameters
* **Event Mode** - Configures in what forms to trigger the event.
* **Top Form** *-* The notification will be sent only to the top form.
* **First Form** *-* The notification will be sent only to the first form of the App.
* **Topest Form with event** - The notification will be sent only to the topest form that has the event.\
If the top form does not have the event, the the previous form will be used, if the previous form does not have the event, then its previous form will be used, and so on, untill a form is found that has the event.
* **Top or First** *-* If the Top form has the event, than the Top form event will be executed, if not, then the event will be executed in the application top form.
* **All Forms** - The event will be executed in all open forms that have the event.
* **Targets PIN** - This variable will hold the PIN in which the state change event occured.
* **Targets Value** - This variable will hold the new PIN state. It can be:
* 0 - Low
* 1 - High
---
# 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://doc.sysdevmobile.com/kalipso5/developing/form/actions/actions-description/group-others/gpio-config-input-event.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.