Short answer: You can get render service in Render by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Render Get Render Service action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Service ID serviceId | string | Required | Service ID. Example: srv-abc123 |
{"serviceId": "e.g. srv-abc123"}
{"id": "srv-abc123","name": "my-api","type": "web_service","createdAt": "2025-01-01T00:00:00Z","serviceDetails": {"url": "https://my-api.onrender.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.