Appearance
Tuya
undefined
| Detail | Value |
|---|---|
| Category | IoT |
| Base URL | https://openapi.tuyaus.com/v1.0 |
| Authentication | HMAC-SHA256 |
| Endpoints | 6 |
| Connector key | tuya |
Using Tuya in a workflow
- Go to Connections and click New Connection.
- Pick Tuya from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Devices |
GET | Device Status |
GET | Commands |
GET | Functions |
GET | Homes |
GET | Scenes |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Devices
| Detail | Value |
|---|---|
| Operation ID | devices_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Tuya connection from the Connection dropdown.
- In the Operation dropdown, select
devices_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Tuya API reference.
GET
Device Status
| Detail | Value |
|---|---|
| Operation ID | device_status_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Tuya connection from the Connection dropdown.
- In the Operation dropdown, select
device_status_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Tuya API reference.
GET
Commands
| Detail | Value |
|---|---|
| Operation ID | commands_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Tuya connection from the Connection dropdown.
- In the Operation dropdown, select
commands_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Tuya API reference.
GET
Functions
| Detail | Value |
|---|---|
| Operation ID | functions_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Tuya connection from the Connection dropdown.
- In the Operation dropdown, select
functions_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Tuya API reference.
GET
Homes
| Detail | Value |
|---|---|
| Operation ID | homes_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Tuya connection from the Connection dropdown.
- In the Operation dropdown, select
homes_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Tuya API reference.
GET
Scenes
| Detail | Value |
|---|---|
| Operation ID | scenes_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Tuya connection from the Connection dropdown.
- In the Operation dropdown, select
scenes_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Tuya API reference.