priority-gateway

n8n node for Priority ERP via WebSDK Gateway

Package Information

Released: this month
Downloads: 54 weekly / 1,016 monthly
Latest Version: 4.1.2
Author: Priority Software

Documentation

n8n-nodes-priority-gateway

An n8n community node for integrating with Priority ERP via the WebSDK Gateway.

Features

  • WebSDK Operations — Read, create, update, and delete records in Priority forms
  • OData Operations — Query, create, update, and delete records via Priority's OData API
  • Procedures & Reports — Run Priority procedures and reports with full field/option discovery
  • Form Actions — Execute form-level activations (e.g., wave picking, document generation)
  • SQLI Queries — Run read-only SQL with joins, GROUP BY, and aggregates against Priority's database layer
  • File Uploads — Upload files to Priority forms via WebSDK or OData

Prerequisites

This node requires a running instance of WebSDK Gateway — a TypeScript/Fastify REST API that wraps the Priority Web SDK, OData, and SQLI interfaces into a unified HTTP API. The n8n node does not connect to Priority directly; it calls the Gateway's REST endpoints, and the Gateway handles all communication with Priority ERP.

Installation

n8n Cloud

  1. Go to Settings > Community Nodes
  2. Enter n8n-nodes-priority-gateway
  3. Click Install

Self-hosted n8n

cd ~/.n8n/nodes
npm install n8n-nodes-priority-gateway
# Restart n8n

Configuration

  1. Add Priority Gateway credentials in n8n:

    • Gateway URL — URL of your WebSDK Gateway instance
    • Gateway Key — Gateway API key (pk_…). Identifies your gateway customer. Required in Gateway Key + Priority Login mode on a hosted gateway; in Connector Token mode it may stay empty when the token was minted in the licensing portal or by your gateway admin (such tokens are bound to your key and authenticate on their own). A token self-minted at <gatewayUrl>/connector without a key still needs it (the gateway answers 401 MISSING_API_KEY otherwise), and the Company dropdown in a node's Connection Overrides always needs it. A single-key on-prem gateway needs no key at all.
    • Authentication — pick one:
      • Connector Token (recommended) — paste a revocable gct_ token. It carries the whole Priority identity (server, tabulaini, user, language, and any App / Cloudflare-Access keys it was minted with), so no other Priority fields are needed. Get one from your gateway admin (a service token, minted without typing a password) or mint it yourself in the licensing portal (Get a connector token): portal-minted tokens carry the app-user and product binding that lets your administrator de-license a single user, and need no Gateway Key. Self-minting at <gatewayUrl>/connector works too, but paste your Gateway Key there or fill it in this credential. Tokens last 365 days and are revocable at any time from the gateway (admin console or DELETE /api/v1/connections/<id>). Changing the Priority password invalidates the token.
      • Gateway Key + Priority Login — configure the Priority connection manually: Priority URL, tabulaini, user / password, language, plus optional OData URL. Rarely-needed fields (WCF URL, OData user, App ID/Key, CF-Access keys) sit behind the Show Advanced Fields toggle. Empty fields fall back to the gateway's configured identity (login-default, then master).
    • Company — Priority company. Available in both modes: it is the one per-request field (overrides the token's default company).
  2. Connection settings — including the token — can be overridden per-node (Connection Overrides) for multi-environment workflows.

  3. Company in Connection Overrides offers a live dropdown of the companies your Gateway Key may reach, so multi-company workflows can pick per node instead of typing. It needs a pk_ Gateway Key and a gateway tenant whose host matches the connection's Priority URL; when neither is true (single-tenant on-prem gateways, or Connector Token mode with no Gateway Key) the list comes back empty — switch the field to By Name and type the company, exactly as before.

Operations

Operation Description
WebSDK Read Query form rows with filters
WebSDK Create Create new records in a form
WebSDK Update Update existing records
WebSDK Delete Delete records from a form
WebSDK Upload Upload files to form records
OData Query Query records via OData with filters, expand, and pagination
OData Create Create records via OData
OData Update Update records via OData
OData Delete Delete records via OData
OData Upload Upload files via OData
Run Procedure/Report Execute Priority procedures or reports
Run Form Action Run form activations with field discovery
SQLI Run read-only SQL (joins, GROUP BY, aggregates) via the gateway

Dynamic Field Discovery

The node automatically discovers available forms, fields, procedures, and dropdown options from your Priority server. When configuring operations, fields and options are loaded dynamically — no manual configuration needed.

License

MIT

Discussion