Automate Droplet Snapshots on DigitalOcean
Published 22 days ago
Created by
Darryn
Categories
Template description
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 manageable limit, preventing unnecessary storage costs due to an excess of snapshots.
Who is this for?
This workflow is perfect for users managing DigitalOcean Droplets and looking to automate the process of snapshot creation and cleanup to save on storage costs and maintain efficient resource management. Itโs useful for DevOps teams, cloud administrators, or any developer leveraging DigitalOcean for their infrastructure.
What problem is this workflow solving?
When managing multiple DigitalOcean Droplets, snapshots can quickly accumulate, taking up space and increasing storage costs. Manually deleting and creating snapshots can be time-consuming and inefficient. This automation solves this problem by automating the snapshot management process, ensuring that no more than a defined number of snapshots are kept per droplet.
What this workflow does
- Runs every 48 hours: The workflow is triggered by a cron node that runs every 48 hours, ensuring timely snapshot management.
- List all droplets: The workflow retrieves all droplets in the DigitalOcean account.
- Retrieve snapshots: For each droplet, the workflow retrieves a list of existing snapshots.
- Filter snapshots: If the number of snapshots exceeds 4, the workflow filters for snapshots that need to be deleted.
- Delete snapshots: Excess snapshots are automatically deleted based on the filter criteria.
- Create new snapshot: After cleaning up, the workflow creates a new snapshot for each droplet, ensuring that backups are always up-to-date.
Setup
- 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.
- 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.
- Set Execution Frequency: The cron node is set to run every 48 hours, but you can adjust the timing to suit your needs.
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.
Workflow Summary
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.
Share Template
More Engineering workflow templates
Creating an API endpoint
Task:
Create a simple API endpoint using the Webhook and Respond to Webhook nodes
Why:
You can prototype or replace a backend process with a single workflow
Main use cases:
Replace backend logic with a workflow
Jonathan
Joining different datasets
Task:
Merge two datasets into one based on matching rules
Why:
A powerful capability of n8n is to easily branch out the workflow in order to process different datasets. Even more powerful is the ability to join them back together with SQL-like joining logic.
Main use cases:
Appending data sets
Keep only new items
Keep only existing items
Jonathan
+11
Back Up Your n8n Workflows To Github
This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node.
It then loops over the data checks in Github to see if a file exists that uses the workflow name. Once checked it will then update the file on Github if it exists, Create a new file if it doesn't exist and if it's the same it will ignore the file.
Config Options
repo_owner - Github owner
repo_name - Github repository name
repo_path - Path within the Github repository
>This workflow has been updated to use the n8n node and the code node so requires at least version 0.198.0 of n8n
Jonathan
More DevOps workflow templates
Git backup of workflows and credentials
This creates a git backup of the workflows and credentials.
It uses the n8n export command with git diff, so you can run as many times as you want, but only when there are changes they will create a commit.
Setup
You need some access to the server.
Create a repository in some remote place to host your project, like Github, Gitlab, or your favorite private repo.
Clone the repository in the server in a place that the n8n has access. In the example, it's the ., and the repository name is repo. Change it in the commands and in the workflow commands (you can set it as a variable in the wokflow). Checkout to another branch if you won't use the master one.
cd .
git clone repository
Or you could git init and then add the remote (git remote add origin YOUR_REPO_URL), whatever pleases you more.
As the server, check if everything is ok for beeing able to commit. Very likely you'll need to setup the user email and name. Try to create a commit, and push it to upstream, and everything you need (like config a user to comit) will appear in way. I strong suggest testing with exporting the commands to garantee it will work too.
cd ./repo
git commit -c "Initial commmit" --allow-empty
-u is the same as --set-upstream
git push -u origin master
Testing to push to upstream with the first exported data
npx n8n export:workflow --backup --output ./repo/workflows/
npx n8n export:credentials --backup --output repo/credentials/
cd ./repo
git add .
git commit -c "manual backup: first export"
git push
After that, if everything is ok, the workflow should work just fine.
Adjustments
Adjust the path in used in the workflow. See the the git -C PATH command is the same as cd PATH; git ....
Also, adjust the cron to run as you need. As I said in the beginning, you can run it even for every minute, but it will create commits only when there are changes.
Credentials encryption
The default for exporting the credentials is to do them encrypted. You can add the flag --decrypted to the n8n export:credentials command if you need to save them in plain. But as general rule, it's better to save the encryption key, that you only need to do that once, and them export it safely encrypted.
Allan Daemon
+4
Host your own Uptime Monitoring with Scheduled Triggers
This n8n workflow demonstrates how to build a simple uptime monitoring service using scheduled triggers.
Useful for webmasters with a handful of sites who want a cost-effective solution without the need for all the bells and whistles.
How it works
Scheduled trigger reads a list of website urls in a Google Sheet every 5 minutes
Each website url is checked using the HTTP node which determines if the website is either in the UP or DOWN state.
An email and Slack message are sent for websites which are in the DOWN state.
The Google Sheet is updated with the website's state and a log created.
Logs can be used to determine total % of UP and DOWN time over a period.
Requirements
Google Sheet for storing websites to monitor and their states
Gmail for email alerts
Slack for channel alerts
Customising the workflow
Don't use Google Sheets? This can easily be exchanged with Excel or Airtable.
Jimleuk
+10
๐ฆ Get a bird's-eye view of your n8n instance with the Workflow Dashboard!
Using n8n a lot?
Soar above the limitations of the default n8n dashboard! This template gives you an overview of your workflows, nodes, and tags โ all in one place. ๐ช
Built using XML stylesheets and the Bootstrap 5 library, this workflow is self-contained and does not depend on any third-party software. ๐ It generates a comprehensive overview JSON that can be easily integrated with other BI tools for further analysis and visualization. ๐
Reach out to Eduard if you need help adapting this workflow to your specific use-case!
๐ Benefits:
Workflow Summary** ๐: Instant overview of your workflows, active counts, and triggers.
Left-Side Panel** ๐: Quick access to all your workflows, nodes, and tags for seamless navigation.
Workflow Details** ๐ฌ: Deep dive into each workflow's nodes, timestamps, and tags.
Node Analysis** ๐งฉ: Identify the most frequently used nodes across your workflows.
Tag Organization** ๐๏ธ: Workflows are grouped according to their tags.
Visually Stunning** ๐จ: Clean, intuitive, and easy-to-navigate dashboard design.
XML & Bootstrap 5** ๐ ๏ธ: Built using XML stylesheets and Bootstrap 5, ensuring a self-contained and responsive dashboard.
No Dependencies** ๐: The workflow does not rely on any third-party software. Bootstrap 5 files are loaded via CDN but can be delivered directly from your server.
โ ๏ธ Important note for cloud users
Since the cloud version doesn't support environmental variables, please make the following changes:
get-nodes-via-jmespath node. Update the instance_url variable: enter your n8n URL instead of {{$env["N8N_PROTOCOL"]}}://{{$env["N8N_HOST"]}}
Create HTML node. Please provide the n8n instance URL instead of {{ $env.WEBHOOK_URL }}
๐Example:
Check out our other workflows:
n8n.io/creators/eduard
n8n.io/creators/yulia
Eduard
More IT Ops workflow templates
+3
Backup n8n workflows to Google Drive
Temporary solution using the undocumented REST API for backups using Google drive.
Please note that there are issues with this workflow. It does not support versioning, so please know that it will create multiple copies of the workflows so if you run this daily it will make the folder grow quickly. Once I figure out how to version in Gdrive I'll update it here.
Angel Menendez
+8
Advanced Telegram Bot, Ticketing System, LiveChat, User Management, Broadcasting
A robust n8n workflow designed to enhance Telegram bot functionality for user management and broadcasting. It facilitates automatic support ticket creation, efficient user data storage in Redis, and a sophisticated system for message forwarding and broadcasting.
How It Works
Telegram Bot Setup: Initiate the workflow with a Telegram bot configured for handling different chat types (private, supergroup, channel).
User Data Management: Formats and updates user data, storing it in a Redis database for efficient retrieval and management.
Support Ticket Creation: Automatically generates chat tickets for user messages and saves the corresponding topic IDs in Redis.
Message Forwarding: Forwards new messages to the appropriate chat thread, or creates a new thread if none exists.
Support Forum Management: Handles messages within a support forum, differentiating between various chat types and user statuses.
Broadcasting System: Implements a broadcasting mechanism that sends channel posts to all previous bot users, with a system to filter out blocked users.
Blocked User Management: Identifies and manages blocked users, preventing them from receiving broadcasted messages.
Versatile Channel Handling: Ensures that messages from verified channels are properly managed and broadcasted to relevant users.
Set Up Steps
Estimated Time**: Around 30 minutes.
Requirements**: A Telegram bot, a Redis database, and Telegram group/channel IDs are necessary.
Configuration**: Input the Telegram bot token and relevant group/channel IDs. Configure message handling and user data processing according to your needs.
Detailed Instructions**: Sticky notes within the workflow provide extensive setup information and guidance.
Live Demo Workflow
Bot: Telegram Bot Link (Click here)
Support Group: Telegram Group Link (Click here)
Broadcasting Channel: Telegram Channel Link (Click here)
Keywords: n8n workflow, Telegram bot, chat ticket system, Redis database, message broadcasting, user data management, support forum automation
Nskha
Backup workflows to GitHub
Note: This workflow uses the internal API which is not official. This workflow might break in the future.
The workflow executes every night at 23:59. You can configure a different time bin the Cron node.
Configure the GitHub nodes with your username, repo name, and the file path.
In the HTTP Request nodes (making a request to localhost:5678), create Basic Auth credentials with your n8n instance username and password.
ghagrawal17
