← All N8N workflows
Automation & utilitiesHTTP RequestManual TriggerEdit Fields

Delete NM of KV (By Name Serach)

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

Workflow preview
Web / APIDelete KVHTTP RequestWeb / APIDelete KV1HTTP RequestTransformKV to RenameEdit FieldsTransformAccount PathEdit FieldsWeb / APIDelete KVs inside NMHTTP RequestWeb / APICreate KV-NMHTTP RequestWeb / APIWrite KVs inside NMHTTP RequestWeb / API-Get Keys inside NMHTTP RequestWeb / APIDelete KV inside NMHTTP RequestWeb / APIRead Value Of KV In NMHTTP RequestTriggerManual TriggerManual TriggerWeb / APIList KV-NMs (1)HTTP RequestTransformSet KV-NM Name (2)Edit FieldsTransformSet KV-NM Name (1)Edit FieldsTransformSet KV-NM Name (3)Edit FieldsWeb / APIList KV-NMs (2)HTTP RequestWeb / APIList KV-NMs (3)HTTP RequestTransformSet KV-NM Name (4)Edit FieldsWeb / APIWrite V & MD of KV InNMHTTP RequestTransformSet KV-NM Name (5)Edit FieldsTransformSet KV-NM Name (6)Edit FieldsWeb / APIList KV-NMs (4)HTTP RequestWeb / APIList KV-NMs (5)HTTP RequestWeb / APIList KV-NMs (6)HTTP RequestWeb / APIList KV-NMs (7)HTTP RequestWeb / APIList KV-NMs (8)HTTP RequestWeb / APIList KV-NMs (9)HTTP RequestWeb / APIList KV-NMs (10)HTTP RequestTransformSet KV-NM Name (7)Edit FieldsTransformSet KV-NM Name (8)Edit FieldsWeb / APIRead MD from KeyHTTP Request

Node categories in this workflow

  • Web / API
  • Transform
  • 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
Delete KVWeb / APIHTTP RequestDELETE
Delete KV1Web / APIHTTP RequestPUT
KV to RenameTransformEdit FieldsSee node parameters
Account PathTransformEdit FieldsSee node parameters
Delete KVs inside NMWeb / APIHTTP RequestDELETE
Create KV-NMWeb / APIHTTP RequestPOST
Write KVs inside NMWeb / APIHTTP RequestPUT
-Get Keys inside NMWeb / APIHTTP RequestSee node parameters
Delete KV inside NMWeb / APIHTTP RequestDELETE
Read Value Of KV In NMWeb / APIHTTP RequestSee node parameters
Manual TriggerTriggerManual TriggerSee node parameters
List KV-NMs (1)Web / APIHTTP RequestSee node parameters
Set KV-NM Name (2)TransformEdit FieldsSee node parameters
Set KV-NM Name (1)TransformEdit FieldsSee node parameters
Set KV-NM Name (3)TransformEdit FieldsSee node parameters
List KV-NMs (2)Web / APIHTTP RequestSee node parameters
List KV-NMs (3)Web / APIHTTP RequestSee node parameters
Set KV-NM Name (4)TransformEdit FieldsSee node parameters
Write V & MD of KV In NMWeb / APIHTTP RequestPUT
Set KV-NM Name (5)TransformEdit FieldsSee node parameters
Set KV-NM Name (6)TransformEdit FieldsSee node parameters
List KV-NMs (4)Web / APIHTTP RequestSee node parameters
List KV-NMs (5)Web / APIHTTP RequestSee node parameters
List KV-NMs (6)Web / APIHTTP RequestSee node parameters
List KV-NMs (7)Web / APIHTTP RequestSee node parameters
List KV-NMs (8)Web / APIHTTP RequestSee node parameters
List KV-NMs (9)Web / APIHTTP RequestSee node parameters
List KV-NMs (10)Web / APIHTTP RequestSee node parameters
Set KV-NM Name (7)TransformEdit FieldsSee node parameters
Set KV-NM Name (8)TransformEdit FieldsSee node parameters
Read MD from KeyWeb / APIHTTP RequestSee 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

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

List NMs

List NMs

to change parameters read Docs

Create NM

Create NM

to change parameters read Docs

Delete NM of KV (By Name Serach)

Delete NM of KV (By Name Serach)

to change anything read Docs

Delete KV

Delete Selected KV

Rename NM of KV (By Serach)

Rename NM of KV (By Serach)

to change parameters read Docs

Delete KV1

/storage/kv/namespaces/

Account Path

Required for all nodes

Delete multiple KV pairs

Delete multiple KV pairs

to change anything read Docs

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ **`Cloudflare Key-Value Full API integration Workflow`**

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ Cloudflare Key-Value Full API integration Workflow

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ Integrate your N8N with CF KV Free instead of selfhosting Redis or any RAM based Storages!!

Delete KVs inside NM

Delete bulk Keys-Values inside select Namespace

Write multiple KV pairs

Write multiple KV pairs

to change anything read Docs

Create KV-NM

Create New Key-Value Namespace

List NM-Keys

List NM-Keys

to change anything read Docs

-Get Keys inside NM

Get Available Keys

Read MD in spesific key

Read MD in spesific key

to change anything read Docs

Delete KV

Delete KV

to change anything read Docs

Delete KV inside NM

Delete selected KV in NM

Read KV

Read KV

to change anything read Docs

Write KV

Write KV

to change anything read Docs

This n8n template provides a seamless and efficient way to manage Key-Value (KV) pairs in Cloudflare's KV storage. all you need just take the part of action you want then use it with your workflow, keep in mind that the **_`Account Path`_** node is required for all actions as it's used to set the path of account, other authentication values is automatically set by n8n pre configured cloudflare api.

This n8n template provides a seamless and efficient way to manage Key-Value (KV) pairs in Cloudflare's KV storage. all you need just take the part of action you want then use it with your workflow, keep in mind that the Account Path node is required for all actions as it's used to set the path of account, other authentication values is automatically set by n8n pre configured cloudflare api.

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌

shortcuts:

  • NM or NMs = NameSpace/s

  • KV or KVs = Key/s - Value/s

  • MD = MetaData

Manual Trigger

Replace Me

List KV-NMs (1)

Get Available Namespaces

Set KV-NM Name (2)

Set Key-Value Namespace for deleting

Set KV-NM Name (3)

Set Key-Value Namespace for Deleting

Set KV-NM Name (4)

Set Key-Value Namespace for kv

Write V & MD of KV In NM

Put value with Metadata to NM key

Set KV-NM Name (6)

Set Key-Value Namespace

Delete NM of KV (By Name Serach)

Delete NM of KV (By Name Serach)

Purpose and structure

This folder contains the Delete NM of KV (By Name Serach) workflow. Its executable nodes use httpRequest, manualTrigger, set. 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

Manual Trigger

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/0384_HTTP_Manual_Create_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • ‌ ‌‌‌‌ ‌ ‌ ‌ ‌‌‌‌ ‌ Bulk Actions
  • ‌ ‌‌‌‌ ‌ ‌ ‌ Specific Actions
  • ‌ ‌‌‌‌ ‌ ‌ ‌ ‌‌‌‌ ‌ ‌‌‌‌ ‌ ‌ ‌ ‌ ‌ Single Actions

More in Automation & utilities