n8n-nodes-datamcp 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -32,7 +32,9 @@ The published package has also been loaded with n8n 2.44.6.
32
32
 
33
33
  1. Create the database source in DataMCP.
34
34
  2. Open **API Keys → Integration keys** in the DataMCP dashboard.
35
- 3. Create a read-only key limited to only the source(s) the workflow needs.
35
+ 3. Create a read-only key for the source(s) the workflow needs, or choose
36
+ **Write selected tables** and grant only the specific tables and actions
37
+ needed for row mutations.
36
38
  4. Copy the `dm_int_` secret immediately; it is shown once.
37
39
  5. In n8n, create **DataMCP Integration API**, choose QA or Production, and
38
40
  paste the secret.
@@ -72,9 +74,9 @@ row larger than 512 KiB is rejected rather than silently cut in half.
72
74
 
73
75
  ### Create Row, Update Row, and Delete Row
74
76
 
75
- Row mutations are currently enabled in QA but disabled in production. They
76
- require integration writes to be enabled in your DataMCP environment. Choose
77
- up to 20 schema-qualified tables in one source, then grant
77
+ Row mutations are available in QA and production when integration writes are
78
+ enabled in the DataMCP environment. Choose up to 20 schema-qualified tables
79
+ in one source, then grant
78
80
  only the Create, Update, and Delete actions the workflow needs. A write
79
81
  credential may also allow Read Query. Read Query can reach any table covered
80
82
  by the database user's SELECT grants in that source; selecting write tables
@@ -108,9 +110,14 @@ returned HTTP 429, which a running n8n workflow displayed as a safe rate-limit
108
110
  error. The packed archive was checked separately from the source checkout.
109
111
 
110
112
  Production Read Query was verified with a source-scoped key and `SELECT 1`;
111
- the key was revoked after the test. Production row mutations have not yet been
112
- enabled or verified. Version 0.1.0 was published manually, but did not include
113
- provenance and therefore did not pass the n8n community-package scanner.
113
+ the key was revoked after the test. Production create/read/update/delete was
114
+ also verified against a disposable PostgreSQL table through Local Agent
115
+ Tunnel using the published 0.1.1 node code in a local n8n container. The test
116
+ also confirmed cross-table writes and write SQL through Read Query are denied,
117
+ and that revoking the key immediately blocks further requests. The test key,
118
+ tunnel, table, and database role were removed afterward. Version 0.1.0 was
119
+ published manually, but did not include provenance and therefore did not pass
120
+ the n8n community-package scanner.
114
121
 
115
122
  The QA credentials and disposable databases used during development are test
116
123
  fixtures and must never be included in this package.
package/dist/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "n8n-nodes-datamcp",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Source-scoped DataMCP actions for n8n",
5
5
  "license": "MIT",
6
6
  "homepage": "https://datamcp.app",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "n8n-nodes-datamcp",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Source-scoped DataMCP actions for n8n",
5
5
  "license": "MIT",
6
6
  "homepage": "https://datamcp.app",