← All N8N workflows
Automation & utilitiesCronFilterHTTP Request

Trigger workflow every 48 hours

Configured with Cron, Filter, HTTP Request. Review the connections and setup before adapting this template.

Workflow preview
RoutingFilterFilterWeb / APIList Snapshots for aDropletHTTP RequestWeb / APIList All DropletsHTTP RequestWeb / APIDelete a SnapshotHTTP RequestWeb / APIDroplet Actionssnapshot…HTTP RequestTriggerRuns every 48hrsCron

Node categories in this workflow

  • Routing
  • Web / API
  • Trigger

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
FilterRoutingFilterSee node parameters
List Snapshots for a DropletWeb / APIHTTP RequestSee node parameters
List All DropletsWeb / APIHTTP RequestSee node parameters
Delete a SnapshotWeb / APIHTTP RequestSee node parameters
Droplet Actions snapshot (n8n.optimus01.co.za)Web / APIHTTP RequestSee node parameters
Runs every 48hrsTriggerCronSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • httpHeaderAuth

Workflow notes

List All Droplets

f3bc462f9219860aafe79747ee369e2f79ccd7f9b096dfe66b55d946871e8942

Trigger workflow every 48 hours

Trigger workflow every 48 hours

This node triggers the workflow to run every 48 hours. You can adjust the frequency if needed to suit your snapshot management requirements.

Get all droplets from DigitalOcean

Get all droplets from DigitalOcean

Fetches a list of all the droplets in your DigitalOcean account. This is the first step in managing snapshots for each droplet.

Retrieve snapshots for a droplet

Retrieve snapshots for a droplet

Retrieves all the snapshots associated with a specific droplet. This ensures that we know how many snapshots currently exist for each droplet.

Check if there are more than 4 snapshots

Check if there are more than 4 snapshots

Checks if the number of snapshots for a droplet is equal to or greater than 4. If true, it proceeds to delete the oldest snapshot.

Delete the oldest snapshot

Delete the oldest snapshot

Deletes the oldest snapshot from the droplet if the number of snapshots exceeds the limit (4 in this case), based on the filter's condition.

Create a new snapshot

Create a new snapshot

Creates a new snapshot for the droplet after cleaning up the old snapshots. Ensures that backups are always up to date.

What this workflow does

What this workflow does

  1. Runs every 48 hours: The workflow is triggered by a cron node that runs every 48 hours, ensuring timely snapshot management.
  2. List all droplets: The workflow retrieves all droplets in the DigitalOcean account.
  3. Retrieve snapshots: For each droplet, the workflow retrieves a list of existing snapshots.
  4. Filter snapshots: If the number of snapshots exceeds 4, the workflow filters for snapshots that need to be deleted.
  5. Delete snapshots: Excess snapshots are automatically deleted based on the filter criteria.
  6. Create new snapshot: After cleaning up, the workflow creates a new snapshot for each droplet, ensuring that backups are always up-to-date.
Get More Templates Like This 👇

Get More Templates Like This 👇

Setup

Setup

  1. DigitalOcean API Key: You’ll need to configure the HTTP Request nodes with your DigitalOcean API key. This key is required for authenticating requests to list droplets, retrieve snapshots, delete snapshots, and create new ones.
  2. Snapshot Threshold: By default, the workflow is set to keep no more than 4 snapshots per droplet. This can be adjusted by modifying the filter node conditions.
  3. Set Execution Frequency: The cron node is set to run every 48 hours, but you can adjust the timing to suit your needs.
Automate Droplet Snapshot Management on DigitalOcean

Automate Droplet Snapshot Management on DigitalOcean

Built for the Let's Automate It Community by Optimus Agency

This workflow automates the management of DigitalOcean Droplet snapshots by keeping the number of snapshots under a defined limit, deleting the oldest ones, and ensuring new snapshots are created at regular intervals.

How to customize this workflow

How to customize this workflow

  • Adjust Snapshot Limit: Change the value in the filter node if you want to keep more or fewer snapshots.
  • Modify Run Frequency: The workflow runs every 48 hours by default. You can change the frequency in the cron node to run more or less often.
  • Enhance with Notifications: You can add a notification node (e.g., Slack or email) to alert you when snapshots are deleted or created.
Trigger workflow every 48 hours

Trigger workflow every 48 hours

Purpose and structure

This folder contains the Trigger workflow every 48 hours workflow. Its executable nodes use cron, filter, httpRequest. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Runs every 48hrs

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0611_HTTP_Filter_Automation_Scheduled.json MIT; preserve source notices.

More in Automation & utilities