PRIORITY AI-TOOLS n8n node What’s new Request an invite
n8n community node for Priority ERP

Automate Priority ERP from n8n

One node covers all of Priority: records, procedures, reports, the buttons on a form, and read-only SQL. It reads your forms and fields from your own server while you build. Nothing drifts out of sync.

Install the node See what it does
n8n-nodes-priority-gateway v3.17.1 MIT licensed 61 published versions
Priority Gateway — WebSDK · Read
Parameters Settings Docs
1 Form from your server
CUSTsearching your server…
CUSTOMERS Customers ✓
CUSTPERSONNEL Customer contacts
CUSTDESTS Customer sites
CUSTOBLIGO Customer credit and obligo
2 Fields from your server
CUSTNAME CUSTDES STATDES PHONE EMAIL PAYDES +116 more
3 Subforms unlocked
CUSTORDERS — Open orders
Level 3 — choose a subform

Level 3 became selectable the moment level 2 was picked.

Nothing above was typed by hand. The node reads it from your Priority while you build the flow.

What Priority automation costs without a node

Three protocols, and each one stops somewhere

Priority answers in three different ways, and each one stops short. The first runs procedures, but only from JavaScript. The second reads records in bulk, but only approved forms, and it cannot join. The third joins across tables, and it lives in the developer console. Wiring all three by hand means three patterns to build and then maintain forever.

Hand-typed field lists go stale

A field name pasted into an HTTP node is a copy, and copies drift. Every column the customer adds is a flow that breaks in production instead of while you are building it.

One node, one credential, and a field list that cannot go stale.

Five operations. Every Priority surface.

Pick what you want to do. The node works out how, underneath.

WebSDK

Form operations

Filtered reads three levels deep, row writes, and attachments taken from a file or a URL.

ReadCreateUpdateDeleteUpload File
OData

Record operations

Bulk reads that bring parent and children back together, writes that create an order and its lines in one go, and paging handled for you.

QueryCreateUpdateDeleteUpload File
WebSDK

Procedures and reports

Run a procedure or a report, with its fields found for you. Out comes HTML, Excel or PDF.

ProcedureReport
WebSDK

Form actions

Press the same button a person would press inside Priority, against the row you picked.

Run Form Action
SQLI

Read-only SQL

Totals and breakdowns across several tables at once. The builder works out the joins, or write the query yourself if you prefer.

Visual BuilderRaw SQLI
On read

Attachments inline

Bring attachments back along with the records. Embed them for a one-off job, or link to them for a screen full of results.

Base64 data URIProxied URL

Every part of the panel flips between two modes. A guided form while you are exploring, raw input once you know exactly what you want.

It reads your Priority, not a schema file

Forms, fields, subforms, buttons and dropdown values all come from the server your credential points at, while you are building the flow.

The node's parameter panel in n8n: operation OData, action Query, entity LOGPART — Part Catalogue, and an open field list showing Priority columns with their types — OWNERLOGIN: Assigned to (select), CREATEDDATE: Date Opened (date), PUNITNAME: Buy/Sell Unit (select), EXTFILENAME: Picture (text), CONV: Conversion Ratio (number).
The field list on a real server. Every entry — name, label and type — came back from that Priority, not from anything shipped in the node.

Cascading, not flat

Each choice narrows the next. Pick a form and its subforms appear; pick a row and the buttons that apply to it appear.

Values, not just names

A dropdown carries the values Priority itself would offer, each marked with what it is: the default, a fixed Choose list, a searchable lookup, or a yes/no flag. You pick from the real set instead of guessing a code.

Answers while you type

Half-typed names are answered from a local cache. Without it, n8n throws away the request still in flight and the dropdown below goes blank exactly while you are typing.

Filters without an operator dropdown

Type the comparison into the value itself, and the node translates it.

You typeIt means
>=100at least 100
<>ABCanything except ABC
SO*starts with SO
1..100between 1 and 100

One syntax, translated three different ways depending on how the call goes out.

Joins you did not have to write

Priority cannot normally join across tables. The builder finds the shortest path between the tables your columns live on, and writes the join for you.

You pick
Form
ORDERS
Columns
CUSTDES under CUSTOMERS
Aggregates
COUNT(*), SUM(TOTPRICE)
Group by
CUSTDES

Columns from joined tables appear in the same dropdown, grouped under the table they belong to. Picking one adds the join.

The node sends
SELECT CUSTOMERS.CUSTDES, COUNT(*), SUM(ORDERS.TOTPRICE)
  FROM ORDERS, CUSTOMERS
 WHERE ORDERS.CUST = CUSTOMERS.CUST
 GROUP BY 1
FORMAT;

_meta: { generatedSql, executionTime, rowsReturned }

Read-only by construction. The gateway rejects every mutating verb before a query leaves the building, so a SQLI step cannot write to the ERP even if someone asks it to. Raw SQLI mode is the escape hatch when you would rather compose the query yourself, and it is read-only too.

Procedures that ask questions, answered in advance

Priority procedures stop on confirmation dialogs. A scheduled flow has nobody to press Continue, so you decide the answers while you build it.

Dialog 1 First confirmation the procedure raises Confirm
Dialog 2 Second confirmation Confirm
Dialog 3 Third confirmation Cancel
Dialog 4+ Anything the procedure raises beyond your list Dialog Policy

One setting answers every dialog the same way. A list overrides it in order, so the third entry answers the third question.

Reports that come out the right shape

Choose HTML, Excel, or PDF, and pick from the format templates Priority actually offers for that report. A Word template selects Word PDF on its own. Reports with a second parameter page are handled as a normal step, not a workaround.

Three levels deep, in one step

Parent, subform and sub-subform, whether you are reading or writing. Each level takes its own columns and its own filter.

One credential. No Priority password in n8n.

A connector token carries the whole Priority identity, so the credential form asks for three things and hides the rest.

Priority Gateway API
Gateway URL
https://your-gateway/api/v1
Gateway Key
pk_••••••••••••••

Also fills the Company dropdown.

Connector Token
gct_••••••••••••••
Test ✓ Connection successful

Everything else sits behind the Advanced toggle.

What the token carries

Server, tabulaini, user, language, and any App or Cloudflare Access keys it was minted with. No other Priority field is needed, and no Priority password is stored in n8n.

Mint one yourself at <gatewayUrl>/connector. It lasts 365 days, and revoking it takes seconds.

Per-node Connection Overrides — 14 of them — let one flow reach a second company or a test environment without a second credential.

Written by the node itself

An AI agent can author the workflow

The node generates its own authoring spec — 26 sections, emitted from the node's own parameter definitions, so it cannot drift from what the panel accepts. The gateway serves that spec to any LLM.

▸ You     Build me an n8n flow that pushes new web orders
          into Priority and runs the confirmation procedure.

  Claude  priority_discover(action: "n8n_node",
                    params: { section: "envelope,op-websdk-create" })

          → node type, typeVersion, parameter template,
            and the runtime rules for filters and pickers

          Three nodes written. Paste them into n8n.

Point an agent at GET /api/v1/n8n-guide, or let an MCP client call priority_discover({action:"n8n_node"}). It writes a working workflow JSON without opening the editor.

60 seconds to your first row

Install it the way your n8n runs, paste three fields, and import the example.

n8n Cloud

Install from the community-nodes screen

Settings → Community Nodes → Install, then search for n8n-nodes-priority-gateway. The node appears on the canvas straight away.

Self-hosted

Install from npm

Run npm install n8n-nodes-priority-gateway inside ~/.n8n/nodes, then restart n8n.

One prerequisite: a running Priority Gateway. One gateway serves every n8n instance you have, and it is what puts WebSDK, OData, and SQLI behind a single credential. The node never talks to Priority directly, so no Priority SDK is installed on the n8n host.

One Priority behavior worth knowing up front: a WebSDK read with no filter returns zero rows. That is Priority, not the node — the SDK fetches rows only once a filter has been applied. The shipped example starts with a filter for exactly this reason. OData Query has no such requirement.

Then run the example

The package ships a workflow you can import as-is.

Fileexamples/workflows/websdk-read-filtered.json
What it doesReads CUSTOMERS, filtered on CUSTNAME with SO*
To run itImport, select your credential, press Execute

Where it stands today

Every number here comes from the repository and the public npm registry.

13
actions in
one node
61
published
versions
208
commits
since February 2026
MIT
licensed
source is public

Figures current to 8 August 2026. Published as n8n-nodes-priority-gateway.

Where the gateway runs

The node runs in your own n8n. What it calls is the Priority Gateway, hosted for you on Amazon Web Services with Cloudflare in front — there is nothing on your side to install or keep running.

Hosted on AWS

The hosted gateway runs in Amazon's Tel Aviv region, deployed from a versioned pipeline. Secrets live in AWS Parameter Store, encrypted, never in a database or a config file.

Cloudflare in front

Every call your workflow makes arrives through Cloudflare: TLS, DDoS protection, a web application firewall, rate limiting and bot filtering, plus caching and routing that shorten the trip.

No open front door

The servers accept no inbound connections. They dial out to Cloudflare and traffic comes back down that tunnel, so there is no public port to find and nothing to scan. Admin surfaces sit behind a second gate.

Your n8n can be self-hosted or on n8n Cloud, and your Priority can sit in Priority’s cloud or on your own servers. The gateway sits between them and reaches each over an outbound connection, so no port has to be opened on your network.

Part of the Priority AI-Tools suite

The node is one caller of the Priority Gateway. The same gateway and the same revocable token serve the rest of the family, and one registration provisions all of it.

Priority Console BI Generator Licensing portal This node on npm