> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/events-and-notifications/inputs-and-outputs/output-triggering.md).

# Output triggering

## Overview

Vehicle GPS devices often come equipped with configurable outputs that enable users to control various vehicle functions, such as engine immobilization, alarm activation, and more. These outputs can be managed directly from the dashboard in your telematics platform. By configuring a rule for output state changes, you can receive notifications via the user interface, mobile app, SMS, or email whenever there is a modification in the output's status.

This feature ensures you remain informed about any changes to the equipment connected to your GPS device. Whether you’re activating or deactivating specific functions, this rule provides a reliable way to monitor and manage the status of your vehicle outputs.

For example, in fleet management, this rule is particularly useful for monitoring the status of an engine block or fuel cut-off system. If a GPS device is configured to control these outputs, the rule can generate alerts whenever the engine block is activated or deactivated. This allows fleet managers to ensure that security measures are being properly applied and that unauthorized vehicle use is prevented.

## Rule settings

#### Output

Specify the hardware output you want to monitor by selecting the appropriate output number. Refer to the tracker manufacturer's documentation to determine which output controls which functionality.

## System operation details

* **GPS-Independent event alert:** If the platform detects an output change event (such as a switch from 1 to 0 or vice versa) from a tracker data packet without valid coordinates, it will still count the event as valid and display it. This applies regardless of whether the event occurred inside or outside a geofence, as the Inside/Outside geofence logic is ignored to ensure potentially important events are not overlooked.
* **Selective alerts:** If you want to receive alerts only for specific output changes, such as from "OFF to ON" and not from "ON to OFF," you can achieve this by clearing the notification text for the undesired output state in the settings.
* **Reset timer:** The "Outputs Triggering" alert has a 10-second reset timer, meaning it will not trigger more frequently than once every 10 seconds. If another event occurs during the reset period, it will be omitted from the platform, including in reports.
* **Multiple devices:** You can assign multiple trackers to this rule, with each tracker utilizing the same output number specified in the rule settings. For example, if you select output #2, the rule will notify you whenever any of the selected trackers reports a change in its output #2.


---

# 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, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/user/guide/events-and-notifications/inputs-and-outputs/output-triggering.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
