KV - Cloudflare Key-Value Database Full API Integration Workflow
Published 11 months ago
Created by
Nskha
Categories
Template description
This n8n template provides a comprehensive solution for managing Key-Value (KV) pairs using Cloudflare's KV storage. It's designed to simplify the interaction with Cloudflare's KV storage APIs, enabling users to perform a range of actions like creating, reading, updating, and deleting namespaces and KV pairs.
Features
- Efficient Management: Handle multiple KV operations seamlessly.
- User-Friendly: Easy to use with pre-configured Cloudflare API credentials within n8n.
- Customizable: Flexible for integration into larger workflows (Copy / paste your prefered part).
Prerequisites
- n8n workflow automation tool (version 1.19.0 or later).
- A Cloudflare account with access to KV storage.
- Pre-configured Cloudflare API credentials in n8n.
Workflow Overview
This workflow is divided into three main sections for ease of use:
- Single Actions: Perform individual operations on KV pairs.
- Bulk Actions: Handle multiple KV pairs simultaneously.
- Specific Actions: Execute specific tasks like renaming namespaces.
Key Components
- Manual Trigger: Initiates the workflow.
- Account Path Node: Sets the path for account details, a prerequisite for all actions.
- HTTP Request Nodes: Facilitate interaction with Cloudflare's API for various operations.
- Sticky Notes: Provide quick documentation links and brief descriptions of each node's function.
Usage
- Setup Account Path: Input your Cloudflare account details in the 'Account Path' node. you can get your account path by your cloudflare URL
- Choose an Action: Select the desired operation from the workflow.
- Configure Nodes: Adjust parameters in the HTTP request nodes as needed. (each node contain sticky note with direct link to it own document page)
- Execute Workflow: Trigger the workflow manually to perform the selected operations.
Detailed Node Descriptions
I covered in this Workflow the full api calls of Cloudflare KV product.
API NODE: Delete KV
- Type: HTTP Request
- Function: Deletes a specified KV pair within a namespace.
- Configuration: This node requires the namespace ID and KV pair name. It automatically fetches these details from preceding nodes, specifically from the "List KV-NMs" and "Set KV-NM Name" nodes.
- Documentation: Delete KV Pair API
API NODE: Create KV-NM
- Type: HTTP Request
- Function: Creates a new Key-Value Namespace.
- Configuration: Users need to input the title for the new namespace. This node uses the account information provided by the "Account Path" node.
- Documentation: Create Namespace API
API NODE: Delete KV1
- Type: HTTP Request
- Function: Renames an existing Key-Value Namespace.
- Configuration: Requires the old namespace name and the new desired name. It retrieves these details from the "KV to Rename" and "List KV-NMs" nodes.
- Documentation: Rename Namespace API
API NODE: Write KVs inside NM
- Type: HTTP Request
- Function: Writes multiple Key-Value pairs inside a specified namespace.
- Configuration: This node needs a JSON array of key-value pairs along with their namespace identifier. It fetches the namespace ID from the "List KV-NMs" node.
- Documentation: Write Multiple KV Pairs API
API NODE: Read Value Of KV In NM
- Type: HTTP Request
- Function: Reads the value of a specific Key-Value pair in a namespace.
- Configuration: Requires the Key's name and Namespace ID, which are obtained from the "Set KV-NM Name" and "List KV-NMs" nodes.
- Documentation: Read KV Pair API
API NODE: Read MD from Key
- Type: HTTP Request
- Function: Reads the metadata of a specific Key in a namespace.
- Configuration: Similar to the "Read Value Of KV In NM" node, it needs the Key's name and Namespace ID, which are obtained from the "Set KV-NM Name" and "List KV-NMs" nodes.
- Documentation: Read Metadata API
The rest can be found inside the workflow with sticky/onflow note explain what to do.
Best Practices
- Modular Use: Extract specific parts of the workflow for isolated tasks.
- Validation: Ensure correct namespace and KV pair names before execution.
- Security: Regularly update your Cloudflare API credentials for secure access, and make sure to give your API only access to the KV.
Keywords: Cloudflare KV, n8n workflow automation, API integration, key-value storage management.
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
+8
Scrape and store data from multiple website pages
This workflow allows extracting data from multiple pages website.
The workflow:
1) Starts in a country list at https://www.theswiftcodes.com/browse-by-country/.
2) Loads every country page (https://www.theswiftcodes.com/albania/)
3) Paginates every page in the country page.
4) Extracts data from the country page.
5) Saves data to MongoDB.
6) Paginates through all pages in all countries.
It uses getWorkflowStaticData('global') method to recover the next page (saved from the previous page), and it goes ahead with all the pages.
There is a first section where the countries list is recovered and extracted.
Later, I try to read if a local cache page is available and I recover the cached page from the disk.
Finally, I save data to MongoDB, and we paginate all the pages in the country and for all the countries.
I have applied a cache system to save a visited page to n8n local disk. If I relaunch workflow, we check if a cache file exists to discard non-required requests to the webpage.
If the data present in the website changes, you can apply a Cron node to check the website once per week.
Finally, before inserting data in MongoDB, the best way to avoid duplicates is to check that swift_code (the primary value of the collection) doesn't exist.
I recommend using a proxy for all requests to avoid IP blocks. A good solution for proxy plus IP rotation is scrapoxy.io.
This workflow is perfect for small data requirements. If you need to scrape dynamic data, you can use a Headless browser or any other service.
If you want to scrape huge lists of URIs, I recommend using Scrapy + Scrapoxy.
Miquel Colomer
+5
Google Maps Scraper
This workflow allows to scrape Google Maps data in an efficient way using SerpAPI.
You'll get all data from Gmaps at a cheaper cost than Google Maps API.
Add as input, your Google Maps search URL and you'll get a list of places with many data points such as:
phone number
website
rating
reviews
address
And much more.
Full guide to implement the workflow is here:
https://lempire.notion.site/Scrape-Google-Maps-places-with-n8n-b7f1785c3d474e858b7ee61ad4c21136?pvs=4
Lucas Perret
+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
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
+6
Notion AI Assistant Generator
This n8n workflow template lets teams easily generate a custom AI chat assistant based on the schema of any Notion database. Simply provide the Notion database URL, and the workflow downloads the schema and creates a tailored AI assistant designed to interact with that specific database structure.
Set Up
Watch this quick set up video 👇
Key Features
Instant Assistant Generation**: Enter a Notion database URL, and the workflow produces an AI assistant configured to the database schema.
Advanced Querying**: The assistant performs flexible queries, filtering records by multiple fields (e.g., tags, names). It can also search inside Notion pages to pull relevant content from specific blocks.
Schema Awareness**: Understands and interacts with various Notion column types like text, dates, and tags for accurate responses.
Reference Links**: Each query returns direct links to the exact Notion pages that inform the assistant’s response, promoting transparency and easy access.
Self-Validation**: The workflow has logic to check the generated assistant, and if any errors are detected, it reruns the agent to fix them.
Ideal for
Product Managers**: Easily access and query product data across Notion databases.
Support Teams**: Quickly search through knowledge bases for precise information to enhance support accuracy.
Operations Teams**: Streamline access to HR, finance, or logistics data for fast, efficient retrieval.
Data Teams**: Automate large dataset queries across multiple properties and records.
How It Works
This AI assistant leverages two HTTP request tools—one for querying the Notion database and another for retrieving data within individual pages. It’s powered by the Anthropic LLM (or can be swapped for GPT-4) and always provides reference links for added transparency.
Max Tkacz
+3
Notion knowledge base AI assistant
Who is this for
This workflow is perfect for teams and individuals who manage extensive data in Notion and need a quick, AI-powered way to interact with their databases. If you're looking to streamline your knowledge management, automate searches, and get faster insights from your Notion databases, this workflow is for you. It’s ideal for support teams, project managers, or anyone who needs to query specific data across multiple records or within individual pages of their Notion setup.
Check out the Notion template this Assistant is set up to use: https://www.notion.so/templates/knowledge-base-ai-assistant-with-n8n
How it works
The Notion Database Assistant uses an AI Agent built with Retrieval-Augmented Generation (RAG) to query this Knowledge Base style Notion database. The assistant can search across multiple properties like tags or question and retrieves content from inside individual Notion pages for additional context.
Key features include:
Querying the database with flexible filters.
Searching within individual Notion pages and extracting relevant blocks.
Providing a reference link to the exact Notion pages used to inform its responses, ensuring transparency and easy verification.
This assistant uses two HTTP request tools—one for querying the Notion database and another for pulling data from within specific pages. It streamlines knowledge retrieval, offering a conversational, AI-driven way to interact with large datasets.
Set up
Find basic set up instructions inside the workflow itself or watch a quickstart video 👇
Max Tkacz
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
Dynamically generate a webpage from user request using OpenAI Structured Output
This workflow is a experiment to build HTML pages from a user input using the new Structured Output from OpenAI.
How it works:
Users add what they want to build as a query parameter
The OpenAI node generate an interface following a structured output defined in the body
The JSON output is then converted to HTML along with a title
The HTML is encapsulated in an HTML node (where the Tailwind css script is added)
The HTML is rendered to the user via the Webhook response.
Set up steps
Create an OpenAI API Key
Create the OpenAI credentials
Use the credentials for both nodes HTTP Request (as Predefined Credential type) and OpenAI
Activate your workflow
Once active, go to the production URL and add what you'd like to build as the parameter "query"
Example: https://production_url.com?query=a%20signup%20form
Example of generated page
Agent Studio
