n8n-nodes-ninjapipe 0.8.3 → 0.8.4

package/CHANGELOG.md

@@ -1,7 +1,7 @@
 # Changelog
 
-## 0.8.2
-- Refreshed NP logo SVG in both NinjaPipe nodes
-- npm-ready release bundle for direct publishing
-- Added helper scripts for publish and local install
-- Kept hardened validation and cleaner UX from 0.8.x
+## 0.8.4
+- replaced old icon references and bundled the updated NP SVG icon in both nodes
+- removed remaining V7 wording from package docs
+- refreshed README, docs, and release metadata for npm
+- kept hardened validation and safer advanced-mode behavior

package/INSTALL.md

@@ -1,16 +1,18 @@
 # Install
 
-## Install from npm in n8n
+## From npm
 
-Community Nodes package name:
+Install in n8n Community Nodes:
 
-`n8n-nodes-ninjapipe`
+`n8n-nodes-ninjapipe@0.8.4`
 
-## Local publish
+## Local link
 
 ```bash
 npm install
-npm publish
+npm link
+mkdir -p ~/.n8n/custom
+cd ~/.n8n/custom
+npm init -y
+npm link n8n-nodes-ninjapipe
 ```
-
-After updating the package, refresh or restart n8n if the UI doesn't immediately show the new labels or icon.

package/README.md

@@ -1,71 +1,103 @@
 # n8n-nodes-ninjapipe
 
-A clean UI community node package for NinjaPipe in n8n.
+Production-ready NinjaPipe community nodes for n8n.
 
-## Included nodes
+This package focuses on clean UX, safer defaults, updated NP SVG branding, and an update-friendly structure. Instead of scattering NinjaPipe actions across many separate node variants, it keeps the package intentionally simple:
 
-- **NinjaPipe**
-- **NinjaPipe Trigger**
+- **NinjaPipe** for actions
+- **NinjaPipe Trigger** for polling-based event workflows
 
-## V7 focus
+## Highlights
 
-This package keeps the UX intentionally simple.
+- one action node and one trigger node
+- guided fields for core NinjaPipe resources
+- safer validation before requests are sent
+- friendlier error messages for common API failures
+- select boxes for pipelines, contacts, companies, projects, countries, states, currencies, and deal status where supported by the workspace API
+- optional pipeline stage lookup after choosing a pipeline
+- contact upsert by email
+- company upsert by exact company name
+- custom fields as flexible repeatable entries
+- safer advanced mode with relative-path validation
+- bundled example workflows for forms and lead processing
+- updated NP SVG icon included in both nodes
+
+## Included resources
+
+- Contacts
+- Companies
+- Deals
+- Products
+- Projects
+- Tasks
+- Budgets
+- Lists
+- Pipelines
+- Pipeline Items
+- Invoices
+- Orders
+- Databins
+- Custom API Request
+
+## Included examples
 
-### In the action node
-Choose:
+See the `examples` folder:
 
-- **Resource**
-- **Action**
+- `databin-lead-to-contact.json`
+- `np-form-simple-contact-upsert.json`
+- `np-form-multipage-branching.json`
 
-Then fill in only the fields that matter.
+## Install in n8n
 
-### In the trigger node
-Choose:
+Install this package in **Settings → Community Nodes**:
 
-- **Source**
-- **Polling mode**
-- optional **Custom path**
+```text
+n8n-nodes-ninjapipe@0.8.4
+```
 
-## Highlights
+## Run locally from a custom folder
 
-- one main action node
-- one trigger node
-- guided fields for core resources
-- pipeline, contact, company, and project lookups
-- deal status select box
-- country and state select boxes for DACH-friendly setups
-- custom fields as flexible entries
-- custom API request fallback
-- example workflow templates included
+n8n loads custom nodes from `~/.n8n/custom` by default, or from paths provided via `N8N_CUSTOM_EXTENSIONS`.
 
-## Included workflow templates
+## Link a local development copy
 
-See the `examples` folder:
+For local development, use `npm link` in the package folder and link it into `~/.n8n/custom`.
 
-- `np-form-simple-contact-upsert.json`
-- `np-form-multipage-branching.json`
+## Update policy
 
-## Install
+This package follows semantic versioning.
 
-In n8n Community Nodes, install:
+### Practical release rules
 
-```text
-n8n-nodes-ninjapipe
-```
+- `patch` = bug fixes and non-breaking improvements
+- `minor` = new actions or fields without breaking existing flows
+- `major` = breaking UI or payload changes
+
+## Security notes
+
+- credentials are stored in n8n credentials, not inside workflows
+- advanced path overrides only accept relative API paths
+- full URLs are blocked in custom request paths
+- friendly validation runs before common create and update calls
+- custom fields remain flexible, but guided validation protects common mistakes
+
+See `SECURITY.md` for operational guidance.
 
-## Publish locally
+## Known limitations
+
+- owner and pipeline stage lookup depend on what the NinjaPipe workspace exposes through its API
+- if a workspace does not expose those endpoints, the select box may remain empty
+- in that case you can still use Additional Fields or Advanced mode for manual payload overrides
+- no package can guarantee absolute security in every environment, so production use should still be tested in your workspace before rollout
+
+## Publish
 
 ```bash
 npm install
+npm pack --dry-run
 npm publish
 ```
 
-## Important
-
-- Replace the placeholder pipeline IDs in the workflow templates
-- Adjust custom field keys to your NinjaPipe workspace
-- Use **Create Or Update By Email** for public lead forms
-
-## Docs
+## Maintainer
 
-Additional package docs live in the `docs` folder.
+Michael Hemmersbach

package/SECURITY.md

@@ -1,13 +1,14 @@
 # Security
 
-## What this package does
-- Stores API credentials in n8n credentials, not inside workflows
-- Validates common required fields before sending requests
-- Restricts advanced path overrides to relative API paths
-- Blocks full URLs and path traversal patterns in custom request paths
-
-## Operational guidance
-- Use least-privilege NinjaPipe API keys when possible
-- Test new package versions in a staging workflow first
-- Prefer patch releases for fixes and minor releases for non-breaking additions
-- Review workflow mappings after upgrading if you changed resource fields
+This package uses n8n credentials for API secrets and does not store secrets inside workflows.
+
+Operational guidance:
+
+- use least-privilege NinjaPipe API keys where possible
+- test in a non-production workspace before rollout
+- keep n8n and this package updated
+- use guided fields unless you specifically need Advanced mode
+- review custom field mappings before enabling public forms
+
+Important:
+No third-party package can guarantee 100 percent security in every environment. This package is hardened for safer defaults, but production safety still depends on your n8n setup, server security, key management, and NinjaPipe workspace configuration.

package/docs/CLEAN-UI.md

@@ -0,0 +1,12 @@
+# NinjaPipe Clean UI
+
+This package keeps the UX intentionally simple:
+
+- one **NinjaPipe** action node
+- one **NinjaPipe Trigger** node
+- resource first, action second
+- guided fields for common NinjaPipe use cases
+- custom fields as repeatable entries
+- advanced options hidden unless explicitly enabled
+
+The goal is not to mirror the raw API one to one, but to provide a safer and more usable n8n integration.

package/install-local.sh

@@ -1,11 +1,11 @@
 #!/usr/bin/env bash
 set -euo pipefail
-PROJECT_DIR="${1:-$(cd "$(dirname "$0")" && pwd)}"
-cd "$PROJECT_DIR"
+cd "$(dirname "$0")"
 npm install
 npm link
-mkdir -p "$HOME/.n8n/custom"
-cd "$HOME/.n8n/custom"
+mkdir -p ~/.n8n/custom
+cd ~/.n8n/custom
 [ -f package.json ] || npm init -y >/dev/null 2>&1
 npm link n8n-nodes-ninjapipe
-printf '\nLocal link installed. Restart n8n and hard-refresh the browser.\n'
+
+echo "Local link created. Restart n8n and hard refresh the browser."

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "n8n-nodes-ninjapipe",
-  "version": "0.8.3",
-  "description": "Production-ready NinjaPipe community nodes for n8n with the new NP logo, safer defaults, and npm-ready packaging.",
+  "version": "0.8.4",
+  "description": "Production-ready NinjaPipe community nodes for n8n with clean UX, updated NP SVG icon, safer defaults, and update-friendly packaging.",
   "keywords": [
     "n8n-community-node-package",
     "n8n",

package/publish.sh

@@ -1,9 +1,7 @@
 #!/usr/bin/env bash
 set -euo pipefail
-PROJECT_DIR="${1:-$(cd "$(dirname "$0")" && pwd)}"
-cd "$PROJECT_DIR"
-echo "Project: $PROJECT_DIR"
-grep -E '"name"|"version"' package.json || true
+cd "$(dirname "$0")"
+echo "Publishing $(node -p "require('./package.json').name")@$(node -p "require('./package.json').version")"
 npm install
 npm pack --dry-run
 npm publish

package/docs/V7-CLEAN-UI.md

@@ -1,71 +0,0 @@
-# NinjaPipe V7 Clean UI
-
-## What changed
-
-This package keeps the structure intentionally simple:
-
-- **NinjaPipe** for actions
-- **NinjaPipe Trigger** for polling-style events
-
-Inside the action node you first choose:
-
-- **Resource**
-- **Action**
-
-After that, only the relevant fields should matter.
-
-## UI goals
-
-- clearer labels instead of generic "record" wording
-- easier select boxes for valid values
-- pipeline, contact, company, and project lookups
-- countries and states for common DACH use cases
-- flexible custom fields without forcing raw JSON
-- advanced fields only when needed
-
-## Recommended usage
-
-Use the node for:
-
-- contacts and companies
-- deals and pipelines
-- products and budgets
-- projects and tasks
-- custom API requests for edge cases
-
-Use the trigger for:
-
-- polling contacts
-- polling deals
-- polling tasks
-- polling Databins
-- polling a custom path
-
-## Workflow templates included
-
-See the `examples` folder for starter templates:
-
-- `np-form-simple-contact-upsert.json`
-- `np-form-multipage-branching.json`
-
-## Important setup notes
-
-### Pipeline IDs in workflows
-The included form workflows use a readable **pipeline choice** in the public form and then map this choice to a real NinjaPipe pipeline ID in a Code node.
-
-You must replace the placeholder values in the Code node, for example:
-
-- `REPLACE_PIPELINE_SALES_ID`
-- `REPLACE_PIPELINE_B2B_ID`
-- `REPLACE_PIPELINE_SUPPORT_ID`
-
-### Custom field keys
-If your NinjaPipe workspace uses different keys, update these in the NinjaPipe nodes:
-
-- `lead_source`
-- `product_interest`
-- `deal_interest`
-- `budget_range`
-
-### Contact deduplication
-Use **Create Or Update By Email** whenever a public form may be submitted more than once for the same email address.