- Integrations
- /
- DigitalOcean
- /
- Actions
- /
- Reboot Droplet
ActionDigitalOceanUpdated May 2026
How do I reboot a DigitalOcean droplet?
Short answer: Drop the "DigitalOcean → Reboot Droplet" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Droplet ID droplet_id | string | Required | Droplet ID. Example: 123456 |
Sample request
{"droplet_id": "e.g. 123456"}
Returns
{"action": {"id": 789,"type": "reboot","status": "in-progress"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Reboot Droplet.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Reboot Droplet.
What does the Reboot Droplet action do in DigitalOcean?
Sends ACPI shutdown then powers back on — disk persists. Useful for "weekly maintenance restart" workflows or for "service hung, try reboot" incident-response patterns.
What inputs does Reboot Droplet require?
Required: Droplet 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 DigitalOcean 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 Reboot Droplet support batch operations?
Yes. Run Reboot Droplet inside a Loop node to process arrays. Tiny Command handles DigitalOcean's rate limits automatically so you don't have to throttle manually.
More actions
Other DigitalOcean actions.
Action
Create Droplet
Provisions a new droplet with image, size, region, SSH keys, and optional cloud-init user_data. Useful for "spin up a sandbox for this PR" CI/CD workflows or for elastic-scaling "add a worker when queue depth crosses N" infrastructure automation.
ActionDelete Droplet
Permanently destroys a droplet — irreversible, all data lost. For automated cleanup after CI tests, for cost-control workflows that tear down idle dev droplets overnight, or for incident-response "isolate compromised host" patterns.
ActionGet Droplet
Returns droplet metadata — IPs, status, image, region, size, features. The standard lookup after Create Droplet to wait for status=active (Create returns immediately while provisioning is still in progress).
ActionList Droplets
Returns paginated droplets with optional tag filter. Useful for fleet-management workflows ("show me all droplets tagged staging") or for cost-rollup reporting workflows.
Send reboot droplet from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.