n8n-nodes-eskadia

The official n8n community node for Eskadia. It connects n8n workflows to Eskadia's business management API with permission-aware resource and operation selectors.

The node reads the capabilities of the configured API token at runtime. Users only see operations allowed by the token role, token access level, and modules enabled for their Eskadia organization.

Features

• Dynamic resource and operation selectors for the complete Eskadia API
• Role, scope, and module-aware operation filtering
• Support for path parameters, query parameters, and JSON request bodies
• Automatic pagination for list operations
• Automatic idempotency keys for safe POST retries
• Data-only or full-envelope output
• Array splitting into native n8n items
• Configurable timeout and pagination safety limits
• Official Eskadia icons for light and dark themes
• No runtime dependencies

Installation

n8n interface

On a self-hosted n8n instance, open Settings > Community Nodes, select Install, and enter:

n8n-nodes-eskadia

Restart n8n if your deployment requires it. See n8n's community node installation guide.

Environment-managed installations

For n8n 2.21.0 or newer, the package can also be managed through N8N_COMMUNITY_PACKAGES:

[{"name":"n8n-nodes-eskadia","version":"0.1.0"}]

Credentials

1. Sign in to Eskadia as an owner or administrator.
2. Open Settings > API.
3. Create a token and choose its role and access level:
   • Read only allows GET operations.
   • Read and write allows GET, POST, PUT, and PATCH operations.
   • Full access also allows DELETE operations.
4. Copy the token when Eskadia displays it. It is shown only once.
5. In n8n, create an Eskadia API credential.
6. Enter the Eskadia instance URL and API token.

The default instance URL is https://app.eskadia.com. Enter the base instance URL without /api/v1. HTTPS is required except for local development URLs.

Operations

The node supports every Bearer-authenticated operation exposed by the Eskadia API. The exact list is loaded from GET /api/v1/capabilities and can grow without requiring a new node release.

Resources currently include core CRM, contacts, companies, deals, activities, finance, HR, purchasing, construction, marketing, support, training, integrations, AI agents, promotions, production, webhooks, and administration. A token sees only the subset allowed by its permissions and organization modules.

Parameters

• Resource Name or ID: Select an available Eskadia resource.
• Operation Name or ID: Select an allowed operation. Its HTTP method and path are shown in the description.
• Path Parameters: Add values for placeholders in the selected path, such as id or slug.
• Query Parameters: Add filters, sorting, expansion, or pagination parameters supported by the endpoint.
• JSON Body: Provide the object sent by create and update operations.

Options

• Automatic Idempotency Key generates a unique key for POST requests.
• Idempotency Key supplies a stable key when a workflow must safely retry the same logical request.
• Return All follows every page reported by the API.
• Limit caps output when Return All is disabled.
• Maximum Pages prevents an unexpected pagination loop.
• Response returns only data or the complete Eskadia response envelope.
• Split Into Items converts response arrays into individual n8n items.
• Timeout sets the request timeout in milliseconds.

Examples

Import the examples from the examples directory:

• list-contacts.json lists up to 50 contacts.
• create-contact.json creates a contact with an idempotency key.

Never commit real Eskadia credentials to a workflow export. n8n stores credentials separately and asks you to select them after import.

Permission behavior

Permissions are enforced twice:

1. Eskadia filters the resource and operation selectors returned to n8n.
2. Eskadia validates the selected operation again when the workflow executes.

Removing a module, reducing a token role, or changing token access takes effect without reinstalling the node. A workflow that no longer has permission fails before sending the business request.

Compatibility

• Node.js 22 or newer
• n8n versions that support the current community node package format
• Eskadia API v1 with the capabilities endpoint

The package is built and tested with the latest @n8n/node-cli release in CI.

Development

npm ci
npm test
npm run lint
npm run build
npm pack --dry-run

Security

Report vulnerabilities privately as described in SECURITY.md. Do not include tokens, customer data, or private instance URLs in public issues.

License

MIT