Registry / database / n8n-nodes-plug-database

n8n-nodes-plug-database

library1.1.2jsnpmunverified

n8n community package providing REST-only nodes for the Plug Database blockchain API. Current stable version is 1.1.2, released with patch updates for icons and navigation. It consolidates SQL execution, client access, and user access management into a single node with resource-based navigation, supporting operations like Execute SQL, Request Agent Access, and Approve Access Request. Key differentiators: fixed API base URL, support for both guided and advanced JSON-RPC modes, pagination via Return All, and credential override per node. No socket or realtime trigger support in v1.

database http-networking

npm install n8n-nodes-plug-database

github ↗package ↗

INSTALL

IMPORT

SIG · N8N-NODES-PLUG-DAT

n8n-nodes-plug-database

databasejavascriptv1.1.2

harness data pending

Install & Compatibility

Where this runs

No compatibility data collected yet for this library.

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

Plug Database

✓ import { Plug Database } from 'n8n-nodes-plug-database/credentials/PlugDatabaseApi.credentials'

✗ import PlugDatabaseApi from 'n8n-nodes-plug-database'

Credentials are exported from a separate path; do not import from the main package index

PlugDatabaseNode

✓ import { PlugDatabaseNode } from 'n8n-nodes-plug-database/nodes/PlugDatabase/PlugDatabase.node'

✗ import { PlugDatabase } from 'n8n-nodes-plug-database'

The node class is exported from a nested path; the package index does not export it directly

PlugDatabaseApi

✓ import { PlugDatabaseApi } from 'n8n-nodes-plug-database/credentials/PlugDatabaseApi.credentials'

✗ import { PlugDatabaseApi } from 'n8n-nodes-plug-database'

Credentials are not re-exported from the package root

Demonstrates creating a Plug Database node, setting credentials, and executing a SQL query with aggregated JSON output.

// Install: npm install n8n-nodes-plug-database // In n8n UI, add a 'Plug Database' node // Credentials: fill User (email), Password, optional Default Agent ID, optional Default Client Token // Example: Execute SQL // Create a node with: // Resource: SQL // Operation: Execute SQL // Agent ID: (override or leave empty to use credential default) // SQL Query: SELECT * FROM agents; // Output: Aggregated JSON // The node returns one item per row. // For listing agents: Resource: Client Access, Operation: List Client Agents, Return All: true

Debug

Known issues

breakLegacy access-only nodes are hidden from new workflows; existing workflows using them will continue to work but new users must use the consolidated node.

fix

Switch to the consolidated 'Plug Database' node and use Resource-based navigation.

affects: >=1.1.0

gotchaThe API base URL is fixed to https://plug-server.se7esistemassinop.com.br/api/v1 and cannot be changed via credentials or node settings.

fix

Ensure your Plug Database server is accessible at that URL; no customization available.

affects: >=1.0.0

gotchaNo socket transport or realtime triggers are supported in v1; all operations are REST-only.

fix

Poll for changes via scheduled workflows or wait for future versions with socket support.

affects: >=1.0.0 <=1.1.2

gotchaExecute Batch runs over REST only; it may be slower than a single SQL execution for large batches.

fix

Consider splitting large batches into smaller sets or use Execute SQL for fewer statements.

affects: >=1.0.0

Errors

Common errors & fixes

Cannot find module 'n8n-nodes-plug-database/credentials/PlugDatabaseApi.credentials'

Import path typo or missing file in the package.

fix

Use correct path: 'n8n-nodes-plug-database/credentials/PlugDatabaseApi.credentials'

Error: Plug Database API returned 401 Unauthorized

Invalid or missing credentials; email/password wrong or expired.

fix

Verify user email and password in the credentials dialog, and ensure the account has access.

Error: Agent ID is required for this operation

No Agent ID provided via node field or credential default.

fix

Set the Agent ID either in the node's 'Agent ID' field or in the credential's 'Default Agent ID'.

The node type "Plug Database" is not known

n8n instance may not have the package installed or the community node is not approved.

fix

Install the package via npm install n8n-nodes-plug-database and restart n8n, or check admin settings for community node approval.

Upgrade

Version history

1.1.2latest on npm

Audit

Dependencies

n8n-workflowoptionalpeer dependency required by all n8n community nodes

Agent activity

7 hits · last 30 days

node

Amazon

Resources

githubhttps://github.com/cesar-carlos/plug_node ↗

packagehttps://www.npmjs.com/package/n8n-nodes-plug-database ↗