A chat tab that turns plain words into a working n8n workflow — in your own n8n. It looks up your real Priority screens and fields first, wires the Priority node for you, and has n8n check the workflow before anything is created.
It builds drafts; you decide what runs. A test run, a live run and going live each stop for your approval, one at a time — and nothing ever goes live unless you asked for that in so many words.
Abridged from a real session — including the part where it holds the write-back until you say go.
Read our customer list, find a website for each customer that has none, and write it back to Priority.
Before it builds anything, it resolves the real target. Not “a website field, probably” — the field:
| Screen | CUSTOMERS |
| Field | HOSTNAME — “Web Site” |
| Shape | free text, 48 characters, writable |
It also decides how to search: the customer’s Latin name where one exists, the Hebrew name where not, with the country added so common names don’t collide.
Eight steps, checked with n8n before they were created:
Addresses that come back are trimmed to the field’s 48 characters — and flagged when they had to be cut.
The last step — the only one that writes to Priority — arrives switched off, so the first run shows you real results without touching a record. And it says so, in its own words:
“The write step is off — that was my call, not yours. Say the word and I’ll switch it on.”
Run it.
Running is a decision, so it raises a card. Nothing runs until you press the button.
Running, testing and going live each ask on their own, every time. There is no “approve everything” anywhere on this tab.
After the run it reads the execution back step by step and reports what each customer got. When the write step is on, it goes one further: it reads Priority back and gives you the record — not a promise that the write probably worked.
It also says what it has not verified. In the session this page is drawn from, one outside service name could not be confirmed in advance — it flagged that before the test run, rather than letting the run discover it.
The difference between a workflow that runs and one that fails on the first record is whether the names in it are real.
Before a single step is wired, it reads your Priority through the gateway — the same live screen-and-field lookup the rest of the suite uses. The customer screen, the exact field a website belongs in, how long it is, whether it can be written to: looked up, not assumed. When a question needs your data map — which table, which join — it asks the same map of your own installation that Chat and the BI product answer from.
It builds with the Priority node for n8n — the same node your team could wire by hand, installed from the n8n community registry — working from the node’s own published spec, so the parameters it writes are the parameters the node takes. And it holds itself to your n8n’s rules too: every workflow is validated by n8n before it is created, and edits read the workflow’s current state first, so nothing is overwritten blind.
What lands on your canvas is an ordinary n8n workflow. Open it, edit it, run it, keep it — nothing proprietary is baked in, and nothing about it needs us at runtime.
From the first draft to the evidence that it worked — the whole loop happens in one conversation.
Describe the job. It designs the steps, wires the Priority actions, and creates the workflow in your n8n as a draft.
Point it at a workflow it built — or one it didn’t. It reads the current state from your n8n first, proposes the change, and updates only after the same validation pass.
Trust arrives with evidence. It test-runs on sample data, runs once for real when you approve, and reads the execution back step by step.
Not policy, not a prompt asking it nicely. Each of these is a limit in the software: the capability is absent, so there is nothing to talk it out of.
Creating or editing a workflow raises a card of its own. Anything that runs — a test, a live run, publishing, unpublishing — asks per run, every time, and cannot be bundled into any blanket approval. Changes to Priority records ask one at a time here exactly as they do on the Chat tab. And before an approved run is dispatched, it re-checks that the workflow is still the one you approved — if someone changed it in between, it stops and asks again.
The key you paste in Settings is stored encrypted and used only on the wire, on our servers. It is never placed in the model’s context, never shown on the page, and never written into logs. It works the other way too: the platform never writes secrets into your n8n — workflows point at the Priority credential you already keep there, by name.
No new screens, fields, tables, business rules or code — the development tools are never loaded into this tab at all, exactly as on Chat. Ask for one and it says so in a line and points you at the Dev tab, which is a separate, separately licensed product.
Replies from your n8n come back through a fixed, size-capped channel, checked against what each reply is allowed to contain. Text inside them — names, descriptions, logs — is never treated as instructions, and a reply that looks like an attempt to steer the assistant makes every following n8n call ask you first, for the rest of the turn. Tighter under pressure, never looser.
Automation is a tab in Priority Console, next to Chat. What it needs from you is one address and one key.
Automation is in early access — ask and we switch it on for your account. It appears as a tab in the same console your team already signs into, next to Chat.
In Settings you paste your n8n address and an API key from your own n8n user. A Test button tells you on the spot whether the address answers, the key works, and the version is recent enough — n8n 2.18 or later is recommended.
It needs an address reachable over HTTPS. A free Cloudflare Tunnel gives your n8n one without opening a port on your network — the setup form links a short how-to right where you’d need it.
Each person’s n8n key is theirs: stored encrypted per user, replaceable any time, and everything built through it lands under that person’s n8n account — visible in n8n’s own history like any other change.