> 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/devices-and-settings/object-management/output-control-block.md).
# Commands block
## Overview
The **Commands** block lets you define custom commands for a device in Navixy and send them on demand from the device's [Object widget](/docs/user/guide/tracking/objects-list/object-widget.md). Use it to send a firmware-level instruction directly to a device, such as sending a CAN command or activating an output, or to call any external system that accepts HTTP requests, such as a Slack channel, a notification service, a CRM, or a custom API endpoint. Once configured, commands can be dispatched with a single click.
The Commands block supports two command types:
* **Device command** sends a protocol-level instruction string directly to the device (e.g., to send a CAN command or activate an output).
* **Software command** sends an HTTP POST request with a JSON body to any URL, optionally including current device data such as location, speed, or device ID in the payload.
Commands are saved per device and remain available for repeated use.
{% hint style="info" %}
**When to use Commands vs. IoT Logic**
**Commands** is designed for ad-hoc, manual actions targeting a single device. Use it when you need to send a one-off command without configuring an automation flow.
For automated, rule-based command sending, such as triggering a device action or a webhook when a sensor threshold is crossed, or sending the same command across multiple devices, use [IoT Logic](/docs/user/guide/account/iot-logic.md). The **Device action** and **Webhook** nodes in IoT Logic provide the same underlying capabilities with full flow automation and multi-device targeting.
{% endhint %}
## Configuration
To configure Commands for a device:
1. Go to **Devices and settings** in the left sidebar.
2. Select the device you want to configure.
3. Locate and expand the **Commands** block.
You can add multiple commands of each type. Each command is saved individually.
### Device commands
A **device command** sends a protocol-level instruction string directly to the device over its communication channel.
To add a device command, click **Add device command** at the bottom of the block. Configure the following fields:
1. **Command name**: a label for the command as it will appear in the Object widget (e.g., `device reboot`). Choose a name that clearly describes what the command does.
2. **Command string**: the exact instruction string that will be sent to the device (e.g., `cpureset`).
{% hint style="warning" %}
Valid command strings are device-specific and defined by the device manufacturer. Always refer to the official documentation for your device model to find the correct command strings. Entering incorrect values may have unintended effects on the device.
{% endhint %}
Click **Save** to store the command. Click **Delete** to remove it.
### Software commands
A **software command** sends an HTTP POST request with a JSON body to a URL you specify. This can be an external service endpoint (such as Slack, a custom webhook receiver, or any REST API) or a Navixy API endpoint.
The request body is JSON and must be structured according to what the destination endpoint expects. You can include device data attributes in the body using the `{{attribute_name}}` syntax.
Software commands are configured across two tabs: **General** and **Body**.
To add a software command, click **Add software command** at the bottom of the block.
#### General tab
{% columns %}
{% column width="58.333333333333336%" %}
Configure the following:
1. **Title**: a label for the command as it will appear in the Object widget.
2. **URL**: the full endpoint URL where the POST request will be sent (e.g., `https://hooks.slack.com/services/...` or `https://api.eu.navixy.com/v2/...`).
3. **Headers**: key-value pairs sent as HTTP request headers. Add headers as needed for the destination endpoint. Click **Add header** to insert a new row.
* Use the `Authorization` header for token-based authentication (e.g., `Authorization` / `Bearer your_token`).
* Other authentication methods supported by the destination, such as API keys passed as query parameters in the URL, can also be used.
{% endcolumn %}
{% column width="41.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
#### Body tab
{% columns %}
{% column width="58.333333333333336%" %}
The **Body** field is where you compose the JSON payload. Write valid JSON that matches the format expected by the destination endpoint.
To include live device data in the payload, use the `{{attribute_name}}` syntax. Click the attribute picker button at the top-right of the body field to open a searchable list of available attributes for the device. Selecting an attribute inserts the corresponding `{{attribute_name}}` placeholder into the body at the cursor position.
{% endcolumn %}
{% column width="41.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
The available attributes depend on the specific device and the data it transmits to the platform. Only attributes actually sent by the device appear in the list. Use the picker to avoid typos or incorrect attribute names.
{% endhint %}
Click **Save** to store the command. Click **Delete** to remove it.
#### Example: sending a Slack notification
Slack supports receiving messages from external services via Incoming Webhooks. Once you have set up a webhook in your Slack workspace and obtained the webhook URL (see the [Slack Incoming Webhooks guide](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/)), create a software command with the following configuration:
**General tab:**
* **Title**: `Notify Slack`
* **URL**: your Slack Incoming Webhook URL (e.g., `https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXX`)
* **Headers**: no headers required
**Body tab:**
{% code overflow="wrap" %}
```json
{
"text": "Device {{device_id}}: speed {{speed}} km/h at {{latitude}}, {{longitude}}"
}
```
{% endcode %}
Slack expects a JSON object with a `text` field. The `{{device_id}}`, `{{speed}}`, `{{latitude}}`, and `{{longitude}}` placeholders will be replaced with the current values for the device at the moment the command is sent. When triggered from the Object widget, the message will appear in the Slack channel configured for your webhook.
## Sending commands from the Object widget
Once commands are saved, they appear in the **Commands** block of the device's [Object widget](/docs/user/guide/tracking/objects-list/object-widget.md) in the Tracking module.
Click the **send** button (▷) next to a command name to dispatch it immediately. There is no confirmation dialog and the command is sent as soon as you click. The Commands block shows all device commands and software commands configured for that device.
{% hint style="info" %}
Commands are per-device. Commands configured for one device do not appear in other devices' Object widgets. To send commands to multiple devices based on rules or conditions, use IoT Logic.
{% endhint %}
---
# 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/devices-and-settings/object-management/output-control-block.md?ask=&goal=
```
`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.