How does n8n read and write in Priority through the API?
Priority’s REST API is built on OData: every form is exposed as a resource you can read, filter, create in and update, subforms included. In n8n’s HTTP Request node you set the form’s address, the request method and the credentials, and n8n makes the call every time the workflow runs.
What you need: an API user in Priority with the right permissions, and the server’s address. Keep the credentials in n8n’s Credentials, not inside the node. When Priority is installed on your premises behind a firewall, allow access from the addresses your n8n connects from.
And when the workflow runs an AI agent?
n8n’s AI Agent node uses an MCP server’s tools through the MCP Client Tool node. n8n has a dedicated endpoint in MCP for Priority, so the agent in the workflow gets the same tools for reading, analytics and writing that AI assistants such as Claude and ChatGPT get, without writing API calls.
The agent works against your own Priority’s forms and fields, custom fields included, and sees only what your organization’s API user may see in Priority.
What stops an n8n workflow from writing something you did not intend?
In MCP for Priority, writing is off by default, and in a conversation every write operation is shown for approval first. An automation that runs with no person in front of it, such as n8n, skips the approval step only with an API key that was given write access and explicit permission to skip it, and that is off by default. The server has no ERP delete tool at all.
And when do you need a Priority node of your own?
When the same action in Priority repeats across many workflows, a dedicated node saves setting the address, fields and credentials again each time. Our Expert Services built a ready-made Priority node for n8n that reads and writes any Priority form from an n8n workflow.
Which fits what?
| HTTP Request | MCP for Priority | Priority node | |
|---|---|---|---|
| What it does | Reads and writes form records | Tools for an AI agent in a workflow | Reads and writes any form, as a ready node |
| What you need | An API user and form addresses | An MCP for Priority plan | Built by our Expert Services |
| Writing | What the API user may write | Off by default | What the API user may write |
| Fits | A fixed, defined action | A workflow that has to read, decide and act | An action that repeats across many workflows |
How it works
- HTTP RequestReads and writes form records
- Priority ERPCustomers, orders, invoices, items
And if you work in Make?
In Make, LeonAI Priority adds ready-made modules that read, create, update and delete in Priority, subforms up to three levels included, plus running procedures and producing printed documents through EProg. The tool follows what the workflow needs, not the other way round.
Common questions
- How do you connect n8n to Priority ERP?
- With the HTTP Request node against Priority’s REST API, through the n8n endpoint of MCP for Priority when the workflow runs an AI agent, or with a dedicated Priority node for n8n that reads and writes any form.
- Can an AI agent in n8n work with Priority?
- Yes. n8n has a dedicated endpoint in MCP for Priority, so the same tools an agent uses are available to an automation scenario too. The agent sees only what your organization’s API user may see in Priority.
- Can an n8n workflow write to Priority without approval?
- Only if you allowed it explicitly. In MCP for Priority, an automation that runs with no person in front of it, such as n8n, skips the approval step only with an API key that was given write access and explicit permission to skip it, and that is off by default. The server has no ERP delete tool.
- Does it work with on-premises Priority?
- Yes. MCP for Priority connects to Priority's REST API in the cloud or on a local server reachable over HTTPS, and nothing is installed inside Priority. An on-premises server behind a firewall allows the service's fixed egress addresses.
- n8n or Make?
- Both connect to Priority. Make has LeonAI Priority, a connector with ready-made modules. In n8n you connect with the HTTP Request node, through MCP for Priority or with a dedicated Priority node. The tool follows what the workflow needs.