n8n-nodes-nexoid

Custom n8n community node for connecting workflows and AI Agents to Nexoid.

Current capabilities

Authentication modes

• API User — signs in using the Nexoid API user stored in n8n credentials.
• Provided Session — uses a supplied Nexoid session_id, usually from an upstream app/chat flow. This is the preferred mode for AI Agent use because actions run with the real user's Nexoid permissions.

Resources

Record

• Get a record
• Create a record
• Update a record
• Delete a record
• Search records

Attachment

• List attachments
• Rename attachment
• Delete attachment
• Get upload URL
• Upload Binary from an n8n binary property via Nexoid's signed upload URL flow

Schema

• List Tables
• Describe Table
• Generate Schema

Schema generation samples live records and infers:

• field names and Nexoid field-prefix types
• enum-like text fields
• relationship/reference fields such as object_*
• likely decimal/currency long_* candidates

Because Nexoid stores all numbers as integer-style long_* fields, decimal/currency precision cannot be inferred perfectly. Use Schema Overrides (JSON) to manually correct/enrich generated schemas.

Example override:

{
  "tables": {
    "sale": {
      "notes": ["Reviewed manually"],
      "fields": {
        "long_total": {
          "decimal_scale_hint": 2,
          "manual_notes": ["Currency scaled by 100"]
        },
        "text_state": {
          "enum_values": ["Lead", "Demo", "Won", "Lost"]
        }
      }
    }
  }
}

AI Agent / MCP Server Trigger tool use

The Nexoid node is marked with n8n's usableAsTool metadata. That means supported n8n versions can wrap the Nexoid node as a tool for:

• n8n AI Agent workflows
• n8n's built-in MCP Server Trigger, so external MCP clients can call the Nexoid tool through n8n

Recommended MCP setup:

1. Create an n8n workflow with an MCP Server Trigger.
2. Add this Nexoid node as one of the tools exposed by that MCP Server Trigger.
3. Prefer Provided Session auth and pass the user's Nexoid session_id from the app/chat context where possible.
4. Prefer Schema -> Get Saved Schema as the first MCP/AI step when you already have a reviewed tenant schema pasted into the node.
5. If no reviewed schema is saved yet, use Schema -> Generate Schema, review it, then paste that reviewed result into Get Saved Schema for future runs.
6. For write actions, keep human approval or confirmation in the workflow until the schema and permissions are well proven.

Important: this package does not run its own standalone MCP server. The intended path is: external AI/MCP client → n8n MCP Server Trigger → Nexoid node as an n8n tool.

Local testing checklist

From this package directory:

npm install
node -e "require('./lib/nexoidClient.js'); require('./lib/schemaDiscovery.js'); require('./nodes/Nexoid/Nexoid.node.js'); console.log('load ok')"
npm pack --dry-run

Expected:

• module load prints load ok
• npm pack --dry-run includes:
  • nodes/Nexoid/Nexoid.node.js
  • nodes/Nexoid/nexoid.svg
  • credentials/NexoidApi.credentials.js
  • lib/nexoidClient.js
  • lib/schemaDiscovery.js
  • README.md
  • LICENSE

n8n runtime testing checklist

Credentials

• Create Nexoid API credentials with:
  • API URL, for example https://uk1.api.nexoid.com
  • customer ID
  • username
  • password
• Test API User mode.
• Test Provided Session mode with a live session_id.

Record tests

• Get one known record.
• Search one small table.
• Create/update/delete only against a safe test object/record.

Attachment tests

• Pick a safe test record.
• Upload a small binary file using Attachment -> Upload Binary.
• List attachments on that record.
• Rename the uploaded attachment.
• Delete the uploaded attachment.

Schema tests

• Run Schema -> Get Saved Schema with a pasted reviewed schema and confirm it returns the saved schema payload.
• Run Schema -> List Tables.
• Run Schema -> Describe Table for a small table.
• Run Schema -> Generate Schema in quick mode before deeper modes.
• Add a manual Schema Overrides JSON block and confirm it appears in output.

AI Agent tests

• Add Nexoid as an AI Agent tool.
• Use Provided Session auth.
• Start with read-only questions, for example:
  • list available tables
  • describe the contact table
  • search records in a safe test table
• Then test writes only with explicit workflow approval or a safe sandbox object.

Packaging for local n8n install

Create a local package tarball:

npm pack

This creates a file like:

n8n-nodes-nexoid-1.1.0.tgz

Install it wherever your n8n custom/community nodes are installed. Exact install steps depend on your n8n deployment style.

Common self-hosted pattern:

npm install /path/to/n8n-nodes-nexoid-1.1.0.tgz

Then restart n8n.

Publishing to npm

One-time setup:

npm login

Before publishing:

npm version patch --no-git-tag-version   # optional if you have not manually bumped package.json
npm pack --dry-run

Check the dry-run file list carefully. Do not publish generated test files, .env, tmp/, or credentials.

Publish:

npm publish --access public

For future releases:

1. Update code.
2. Bump version in package.json using semver:
   • patch: bugfix only, e.g. 1.1.1
   • minor: new features, e.g. 1.2.0
   • major: breaking change, e.g. 2.0.0
3. Run load check.
4. Run npm pack --dry-run.
5. Publish.

Notes

• tmp/ and *.tgz are ignored and should not be committed/published.
• Full deep schema generation across very large tenants can hit response-size or runtime limits. Prefer quick full-tenant schema generation first, then deeper targeted table descriptions.