Appearance
Unity Cloud
undefined
| Detail | Value |
|---|---|
| Category | Gaming |
| Base URL | https://build-api.cloud.unity3d.com/api/v1 |
| Authentication | API Key |
| Endpoints | 5 |
| Connector key | unity |
Using Unity Cloud in a workflow
- Go to Connections and click New Connection.
- Pick Unity Cloud 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 | Organizations |
GET | Projects |
GET | Build Targets |
GET | Builds |
GET | Build Logs |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Organizations
| Detail | Value |
|---|---|
| Operation ID | organizations_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Unity Cloud connection from the Connection dropdown.
- In the Operation dropdown, select
organizations_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 Unity Cloud API reference.
GET
Projects
| Detail | Value |
|---|---|
| Operation ID | projects_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Unity Cloud connection from the Connection dropdown.
- In the Operation dropdown, select
projects_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 Unity Cloud API reference.
GET
Build Targets
| Detail | Value |
|---|---|
| Operation ID | build_targets_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Unity Cloud connection from the Connection dropdown.
- In the Operation dropdown, select
build_targets_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 Unity Cloud API reference.
GET
Builds
| Detail | Value |
|---|---|
| Operation ID | builds_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Unity Cloud connection from the Connection dropdown.
- In the Operation dropdown, select
builds_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 Unity Cloud API reference.
GET
Build Logs
| Detail | Value |
|---|---|
| Operation ID | build_logs_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Unity Cloud connection from the Connection dropdown.
- In the Operation dropdown, select
build_logs_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 Unity Cloud API reference.