Skip to content
ActionRenderUpdated May 2026

What services exist on Render?

Short answer: Drop the "RenderList Render Services" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Sample request
{}
Returns
[
{
"service": {
"id": "srv-abc123",
"name": "my-web-app",
"type": "web_service",
"serviceDetails": {
"url": "https://my-web-app.onrender.com"
}
}
}
]

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Render Services.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about List Render Services.

What does the List Render Services action do in Render?
Returns every service in the workspace. Useful for inventory and for resolving service IDs at workflow setup.
What inputs does List Render Services require?
List Render Services has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Render returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Render Services support batch operations?
Yes. Run List Render Services inside a Loop node to process arrays. Tiny Command handles Render's rate limits automatically so you don't have to throttle manually.
More actions

Other Render actions.

Send list render services from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.