Render

Manage services, deployments, and environment variables on Render.

Detail	Value
Category	Cloud & Infra
Base URL	https://api.render.com/v1
Authentication	Bearer Token
Endpoints	8
Connector key	render

Using Render in a workflow

1. Go to Connections and click New Connection.
2. Pick Render 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

Endpoint	Summary
GET /services	List services
POST /services	Create a service
GET /services/{serviceId}	Get service details
PATCH /services/{serviceId}	Update a service
DELETE /services/{serviceId}	Delete a service
GET /services/{serviceId}/deploys	List deploys
POST /services/{serviceId}/deploys	Trigger a deploy
POST /services/{serviceId}/suspend	Suspend a service

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /services

List services

Detail	Value
Operation ID	cloud.listServices
Method	GET
Path	/services

Parameters

No parameters.

Using this endpoint in a workflow

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

POST /services

Create a service

Detail	Value
Operation ID	cloud.createService
Method	POST
Path	/services

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /services/{serviceId}

Get service details

Detail	Value
Operation ID	cloud.getService
Method	GET
Path	/services/{serviceId}

Parameters

No parameters.

Using this endpoint in a workflow

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

PATCH /services/{serviceId}

Update a service

Detail	Value
Operation ID	cloud.updateService
Method	PATCH
Path	/services/{serviceId}

Parameters

No parameters.

Using this endpoint in a workflow

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

DELETE /services/{serviceId}

Delete a service

Detail	Value
Operation ID	cloud.deleteService
Method	DELETE
Path	/services/{serviceId}

Parameters

No parameters.

Using this endpoint in a workflow

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

GET /services/{serviceId}/deploys

List deploys

Detail	Value
Operation ID	cloud.listDeploys
Method	GET
Path	/services/{serviceId}/deploys

Parameters

No parameters.

Using this endpoint in a workflow

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

POST /services/{serviceId}/deploys

Trigger a deploy

Detail	Value
Operation ID	cloud.triggerDeploy
Method	POST
Path	/services/{serviceId}/deploys

Parameters

No parameters.

Using this endpoint in a workflow

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

POST /services/{serviceId}/suspend

Suspend a service

Detail	Value
Operation ID	cloud.suspendService
Method	POST
Path	/services/{serviceId}/suspend

Parameters

No parameters.

Using this endpoint in a workflow

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