Skip to content
For LLMsView as Markdown·

Unity Cloud ​

undefined

DetailValue
CategoryGaming
Base URLhttps://build-api.cloud.unity3d.com/api/v1
AuthenticationAPI Key
Endpoints5
Connector keyunity

Using Unity Cloud in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Unity Cloud from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
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

DetailValue
Operation IDorganizations_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Unity Cloud connection from the Connection dropdown.
  3. In the Operation dropdown, select organizations_0.
  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.

GET ​

Projects

DetailValue
Operation IDprojects_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Unity Cloud connection from the Connection dropdown.
  3. In the Operation dropdown, select projects_1.
  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.

GET ​

Build Targets

DetailValue
Operation IDbuild_targets_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Unity Cloud connection from the Connection dropdown.
  3. In the Operation dropdown, select build_targets_2.
  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.

GET ​

Builds

DetailValue
Operation IDbuilds_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Unity Cloud connection from the Connection dropdown.
  3. In the Operation dropdown, select builds_3.
  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.

GET ​

Build Logs

DetailValue
Operation IDbuild_logs_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Unity Cloud connection from the Connection dropdown.
  3. In the Operation dropdown, select build_logs_4.
  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.