n8n-nodes-mane

Unofficial beta community package for MANE API v1 BETA. It contains MANE (115 operations) and MAINE Skills (5 skill-management operations), with shared MANE API credentials.

Status: beta, not verified by n8n. Mock tests exercise request construction and node execution; no authenticated MANE calls have been made. See verification for the precise boundaries.

Supported capabilities

MANE provides workspace/schema reads, object definitions, records and custom-object records, projects, project tasks, products, quotes, invoices, orders, hours, stored messages, appointments, segments, stock moves, recurring costs, catalog lists, planning team members, availability, time off, leave requests, relation links, files, event reads and webhook configuration. Only methods present in the archived contract are exposed.

MAINE Skills provides get, get many, create, update and delete on /skills. Its write fields are name and instructions. There is no public AI execution, chat, job, run or polling operation in this contract. Saving instructions does not execute a skill.

See the generated operation and scope matrix. Workspace-specific attributes and properties keys come from GET /schema; the node does not invent a complete financial-document schema or override protected-document rules.

Installation

This beta is intended for self-hosted n8n. Use a disposable development instance for initial evaluation. Once the beta is published, select n8n-nodes-mane@0.1.0-beta.2 or the beta tag. The package is not available through n8n Cloud's verified-node catalog.

See installation, the operation matrix and usage examples. Four inactive example workflows are included, with no credentials and disabled mutation nodes in the project-write template.

The recorded development checks used Node.js 22.22.2, TypeScript 5.9.3 and n8n-workflow 2.16.0. n8n-workflow is a * peer dependency as required by the official community linter. This does not establish compatibility with every n8n release. No external runtime dependencies are declared.

Credentials

Select MANE API and enter the API base URL copied from MANE Settings → API & webhooks and an existing scoped service key. The default key is empty and password-masked. The documented app base URL is https://app.maneworks.com/api/v1; other single-subdomain *.maneworks.com/api/v1 workspace bases are supported. Credentials are restricted to that configured HTTPS origin/API prefix; redirects are disabled.

The optional credential test performs GET /workspace and therefore needs workspace:read. It has not been run against MANE. A narrower credential can be used for an operation without testing /workspace. This package neither creates keys nor requests OAuth grants.

Usage

1. Choose MANE or MAINE Skills, then a resource and operation. The operation selector displays the exact method, route and required scope.
2. Copy technical IDs from MANE responses or the workspace catalog. Path IDs are encoded as individual URL segments.
3. For list operations, use Limit (1–100) and the documented query JSON. Filters are q, status, project, owner and type where the contract lists them. Undocumented parameters are rejected.
4. For dynamic writes, provide Body (JSON) with catalog attributes and literal properties keys. Structural contract validation runs locally; tenant-required fields, permissions and business validation remain server-side.
5. For dossier/schema writes, supply the read workspace revision without quotes and a stable Idempotency Key. The node sends quoted If-Match. There are no implicit revision reads or automatic write retries.

When Return All is enabled, numeric list cursors carry the same revision across pages. Events use lossless string IDs in after and do not use a list revision. Max Pages defaults to 100; reaching the bound with more pages available is an error, not silent partial success. Limit is the page size when returning all; otherwise it limits the one requested page. Files and webhook configuration have no cursor parameters in this contract, so they are fetched once.

By default, each list entry becomes an output item shaped as { data: <entry>, revision, total, nextCursor, requestId } using available metadata. Every output links to its originating input item. Turn Split List Into Items off for original page envelopes; this preserves empty-list revisions and checkpoints. Read data.name for a split row and data[0].name for a page. Write responses may contain only data.id; read the detail afterward when necessary.

GET /files/{id} returns n8n binary data in binary.data, with the file ID as its local filename. POST /files accepts the documented JSON/base64 body, not multipart data. Upload and webhook management do not use workspace revision/idempotency headers.

Successful delete output includes deleted: true alongside the API envelope, so following nodes receive a confirmation item.

Recovery and data handling

• A 409 requires a fresh read and review of the intended change. Use a new key for a deliberately revised command; never blindly increase the revision.
• An identical timeout retry must preserve method, path, body, revision and key. Writes are never automatically retried by this node. n8n's own Retry On Fail remains a separate user setting.
• Read Retries defaults to zero; optionally allow up to three GET retries on 429/5xx. Retry-After is honored up to 60 seconds; a longer requested wait is surfaced as an error instead of retrying early.
• HTTP failures preserve safe status, code, request ID and Retry-After. Raw server messages, request headers, credentials and response bodies are not placed in error messages.
• Continue On Fail returns a linked error item. A paginated request fails as a unit; it does not return previously fetched pages as successful partial output.
• Nested PATCH arrays/objects replace prior values. Read and preserve required existing values before sending a nested update. Full object schema updates must retain all fields that should remain.
• Successful data responses can contain personal information. Webhook creation returns a one-time signing secret according to the API documentation. These are normal workflow outputs and may be persisted by n8n execution history. Configure retention and access before any live use.

Boundaries

No webhook trigger is implemented: raw-body HMAC verification, replay protection and durable event deduplication need a separately verified receiver. Event reading and webhook configuration use only documented endpoints. Webhook URL DNS/public-destination checks and allowed event values are enforced by MANE; no outbound destination probing occurs locally.

Stored messages do not send email, planning team records do not invite accounts, and invoice writes do not execute bank payments. The package does not add bulk, PUT, forced-save or AI-generation routes.

Four inactive examples contain no credentials. The project-write template has its write and follow-up nodes disabled. See usage and examples before enabling anything.

Contract, license and verification

This implementation follows MANE's reference, its OpenAPI download and manual, version 1.0.0-beta.20261019. The contract has 52 paths and 120 operations. Contract notes describe the limits of generic schemas and event/webhook shapes.

This is an unofficial community beta, not an official MANE connector. The icon is the existing MANE website brand asset, resized to a transparent 60 × 60 PNG for n8n. MANE names and brand assets belong to their respective owners; the MIT license covers the original package code. Original package code is MIT-licensed. MANE source documentation and development test logs are not shipped in this npm package.

156 local mock tests, TypeScript typecheck, official CLI lint/build and isolated tarball loading were recorded as passing. No authenticated MANE calls or live n8n server/editor integration test were performed. See verification. npm publication alone does not imply n8n verification; Creator Portal eligibility requires the current GitHub Actions/provenance process.

The optional npm author/contact fields are omitted because no public contact was supplied. npm associates the publishing account with the package. The public package does not claim strict n8n metadata or Creator Portal eligibility. The recorded official lint run applies to the development source manifest; see the verification notes for this distinction.