Automate droplet snapshots on DigitalOcean
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on a schedule (legacy Cron node). It uses only n8n's built-in nodes. It also calls api.digitalocean.com over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- List All Droplets (HTTP Request): calls api.digitalocean.com
- List Snapshots for a Droplet (HTTP Request): calls an HTTP API
- Filter: keeps only the items that match a condition
- Delete a Snapshot (HTTP Request): calls an HTTP API
- Droplet Actions snapshot (n8n.optimus01.co.za) (HTTP Request): calls an HTTP API
HTTP calls to: api.digitalocean.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron in Runs every 48hrs: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Runs every 48hrs | Schedule Trigger |
Nodes used (3)
- Filter
n8n-nodes-base.filter - HTTP Request
n8n-nodes-base.httpRequest - Cron
n8n-nodes-base.cron
From the author
This workflow automates the management of DigitalOcean Droplet snapshots by listing all droplets, filtering based on the number of snapshots, and deleting excess snapshots before creating new ones. It ensures your droplet snapshots stay organized and within a…