Automation in Priority ERP: what it does on its own, and what needs a connection

What does Priority do on its own?

Priority ERP has tools for automation inside the system. According to Priority Software, BPM sets up process flows and triggers actions such as reminders and notifications, and business rules show a warning or an error, or send an email, when a condition is met.

These tools fit what happens inside the ERP: approving a purchase order before it goes out, moving a document between statuses, alerting a manager when an invoice passes an amount. They are usually set up by whoever runs Priority in the organization, or by the partner who implemented it.

Priority can also tell another system that something happened: a webhook defined on a BPM status or a business rule sends the record's details to an outside address. That needs Priority's Webhooks module.

Where does built-in automation stop?

Most of the time lost is not inside Priority but at the seams between it and other systems:

• An order from the online store that someone types into Priority by hand.
• A lead from a website form that arrives by email, and someone opens a customer from it.
• A morning report someone builds in Excel and sends on WhatsApp.
• A document signed in a signature system that someone attaches back to the record.
• A manager's question, "how much did we sell to customer X this month?", waiting for whoever knows how to run the report.

In each case, something outside Priority has to read from it or write to it.

What are the ways to connect automation to Priority?

Most organizations start with one fixed scenario that saves the most typing, and add an agent when work arrives that has no fixed rule.

Example: a store order that enters itself

1. 1

   An order comes into the store

   A Make scenario runs when a new order arrives in the online store.

2. 2

   The customer is found or opened

   The scenario looks for the customer in Priority, and opens a new one if none exists.

3. 3

   The order opens with its lines

   LeonAI Priority writes the order together with its lines in one operation: a form and its subforms, up to three levels.

4. 4

   The update goes back

   The Priority order number is written back to the store, so both sides stay in sync.

No code, and no one types the order twice.

And when there is no fixed rule?

Classic automation follows a rule: if X happens, do Y. Some work does not look like that. A collection reminder has to fit the customer's history, a quote starts as a voice note from the car, and an installation depends on a free technician and parts in stock.

That is where an AI agent comes in. It gets a goal, reads current data from Priority through MCP for Priority, prepares the work, and records it in Priority only after a person approves. Every tool call is written to an audit log.

Where do you start?

• List the five actions that repeat most often each week, and who does them.
• Mark each one: is it inside Priority, or between Priority and another system?
• Inside Priority: check with whoever runs the system whether a BPM flow or a business rule solves it.
• Between systems: that is the place for a Make scenario or an agent.
• Start with one process, measure the time it saved, and only then add the next.

Common questions

What is automation in Priority ERP?

Any process that happens in Priority ERP without someone doing it by hand: an approval that moves between statuses by itself, an alert sent when a condition is met, or an online-store order that opens in Priority without typing. Part of it runs on Priority's built-in tools, and part needs a connection to other systems.

Do you need a developer to automate Priority?

Not necessarily. A Make.com scenario with the LeonAI Priority connector is built by drag and drop, and reads and writes in Priority without code. Direct development against the API is only needed for a unique need that no product covers.

What is the difference between automation and an AI agent?

Automation runs a fixed rule: if X happens, do Y. An AI agent gets a goal, reads current data and prepares the work, and a person approves before anything is recorded in Priority.

Can automation write to Priority?

Yes. LeonAI Priority creates and updates records, including a document with its lines in one operation. In MCP for Priority, writing is off by default, and once it is turned on every 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.