ActionRenderUpdated September 2026
How do I trigger a Render deploy?
Short answer: You can trigger render deploy in Render by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Render Trigger Render Deploy action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 |
Clear Build Cache clearCache | options | Optional | Clear Build Cache. Options: No, Yes |
Sample request
{"serviceId": "e.g. srv-abc123","clearCache": "{{trigger.clearCache}}"}
Returns
{"id": "dep-abc123","commit": {"id": "abc123","message": "Update"},"status": "created","createdAt": "2025-01-15T12:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Trigger Render Deploy.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Trigger Render Deploy.
What does the Trigger Render Deploy action do in Render?
Manually triggers a deploy. Optional commitId for rollback or specific-commit deploys. For "approval clicked → deploy to production" or rollback workflows.
What inputs does Trigger Render Deploy require?
Required: Service ID. Every input accepts a static value or a variable from any upstream node in your workflow.
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 run history shows the failed step with its input and the error message Render returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Trigger Render Deploy support batch operations?
Run Trigger Render Deploy inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Render's rate limits.
More actions