Build the portal, the mobile app, the AI assistant, the nightly automation. One gateway and they all reach Priority the same way.
One gateway, four ways in. Read, write, run procedures, query across forms — over plain HTTPS.
Running a procedure or a report means using Priority's own SDK. If your app is Python, .NET or mobile, it cannot get there at all.
Connecting Lovable, Base44 or any AI model to Priority needs a layer that Priority doesn't ship.
One gateway opens both.
One gateway sits between your customer's apps and their Priority. Nothing to install on their side, no driver on anyone's laptop, and no language you are locked into.
One way in for your code, one for questions that span forms, one for AI tools. The same sign-in behind all three.
The portal, the mobile app, the n8n flow, a Python script: they all call the same address. Records, procedures, reports, documents, file uploads. The gateway works out how to fetch each one.
POST /api/v1/query/form { "form": "ORDERS", "filter": { "STATDES": "Open" } }
Real SQL against Priority's own engine, with no driver on anyone's machine. It can only read: anything that would write is rejected before the call leaves the gateway. Dates, decimals and Hebrew come back readable rather than as raw Priority numbers.
POST /api/v1/sqli/query SELECT ORDERS.ORDNAME, CUSTOMERS.CUSTDES FROM ORDERS, CUSTOMERS WHERE ORDERS.CUST = CUSTOMERS.CUST FORMAT;
Connect Claude.ai or Claude Desktop, and your customer's IT manager can ask their own Priority a question and get a real answer. Or build them an assistant of their own on the same footing.
▸ You Show open orders for ACME. Claude priority_action(query, ORDERS, { CUSTNAME: "ACME" })
A server signs in once and gets back a token that expires on its own. A browser app opens our sign-in window instead: the person logs into Priority inside it, and the app receives a token you can revoke whenever you like. The password never reaches the page.
POST /api/v1/auth/login → { "token": "gws_…", "expiresAt": "2026-08-08T18:20:00Z" }
Added since the gateway's first release.
Before the model writes a line of SQL, the gateway hands it a map of the part of Priority the question actually touches. So "how much did we sell last month" comes back right the first time, instead of plausibly wrong. Off by default.
Priority's SDK allows one login per process, so calls used to queue up behind each other. Switch on the worker pool and they run side by side instead.
The gateway explains itself on request: which query dialect to use, which approach fits a given job, how to build an n8n workflow. A model looks that up mid-conversation instead of guessing.
Shopify orders into Priority. Nightly invoice exports out. Approvals routed through Slack. Drag the n8n-nodes-priority-gateway node onto the canvas and connect it. No glue code, and nothing to build per customer.
v3.17.1 · 61 releases · MIT licensed
You describe what the customer needs. It reads their forms, builds the app, tests it in a real browser, and hands back a zip you can deliver.
Three questions settle the shape, the form and how people sign in.
It reads the real form out of the customer's Priority.
Builder agent scaffolds the app on disk under generated-apps/.
It runs the app in a real browser and fixes what breaks.
Changes go back in at the right step, so nothing is rebuilt from scratch.
Pick the shape and the stack. It picks the template.
| React | HTML | Python CLI | |
|---|---|---|---|
| Web app | forms & auth | single-file | — |
| Dashboard | KPIs & filters | read-only | — |
| Mobile-first | responsive | PWA, offline-resilient | — |
| Automation | — | — | cron-friendly |
The orchestrator dispatches one of these per phase.
| Agent | Responsibility |
|---|---|
| Researcher | Pulls live form metadata from the Gateway |
| Designer | Maps forms and subforms to UI patterns |
| Builder | Scaffolds files under generated-apps/ |
| Tester | Walks the scenario in real Chrome (≤3 retries) |
Reference apps the generator copies and customizes. New patterns ship in every release.
orders-dashboard-react
Read-only orders dashboard with KPIs, search, and status filter.
stock-count-mobile-html
Mobile PWA stock count with subform writes and a finalize activation.
invoice-export-python
A scheduled export of invoices to CSV.
employee-order-react
Order entry for your own staff.
auth-contact-react
A form your customers' own contacts sign in to.
auth-priority-user-react
A starting point for Priority sign-in.
contacts-list-session-react
A searchable list that keeps its place as you scroll.
+ more coming
New patterns ship in every release.
Your customer wants AI that knows their Priority. Connect Claude.ai or Claude Desktop and they have it, in their own words.
The model learns your forms and fields as it needs them.
➔"Show open orders for ACME from this month." Natural language in, structured rows out.
➔Create records, run procedures, produce reports and upload files, all in one conversation.
Works with
Chat with live Priority data — ask, query, create.
Generate web apps that read and write Priority through the gateway.
Internal dashboards on top of Priority — no backend code.
AI judgement inside a workflow: routing, alerts and triage.
Any MCP client connects. The gateway handles the sign-in and the routing. Full MCP details →
Real customer asks already running on the gateway.
Orders arrive from a webshop, EDI or email and land in Priority, checked and booked.
One HTML file on the warehouse phones, built from a single prompt. It survives a closed tab.
"Which orders shipped late this month?" Claude reads live Priority data and answers — no custom report.
Orders, invoices, and delivery status — built in Lovable or Base44, served by the gateway.
A scheduled job pulls invoices to CSV and drops them on S3, SFTP or FileSmile. Built from one sentence.
Account ledgers and statements, triggered from an outside system over HTTP.
Hosted for you on Amazon Web Services with Cloudflare in front. There is no gateway for you to install, patch or keep running.
The hosted gateway runs in Amazon's Tel Aviv region. Passwords and keys are kept in Amazon's encrypted store, never in a config file.
Every request comes through Cloudflare first. It encrypts the traffic, absorbs attacks and filters out bots, and it shortens the trip from wherever your callers are.
The servers accept no incoming connections at all. They dial out to Cloudflare, and traffic comes back down that same line, so there is no public door to find. Admin screens sit behind a second lock.
Running Priority on your own servers? That is fine — the gateway reaches it from here over an outbound connection you approve, so nothing has to be installed and no port has to be opened on your network.
Part of the Priority AI-Tools suite
Sign up once. After that your team reaches Priority from Claude, ChatGPT, Gemini, n8n or a live dashboard.