LeonAI Priority ERP Make integrationAutomate LeonAI Priority ERP with Make.

Adds a new SKU, the item code your catalog relies on, to LeonAI Priority ERP without anyone keying it into the ERP.

Keeps an older way of launching a procedure tied to a form, so scenarios built with it go on running as before.

Starts a procedure in LeonAI Priority ERP from your scenario, so a routine someone would launch from the ERP menu runs on its own.

Runs a procedure at sub-form level, on a line nested under a parent record rather than on the record as a whole.

Writes a block of text into a sub-form, which keeps remarks and notes right next to the record they describe.

Goes one level deeper than Add a Text to a Sub-Form: your text lands in a grandchild form, the level that sits under a sub-form line.

Groups several changes to the ERP into a single step, instead of chaining one module for each change.

As its name says, it clears the stored metadata of an entity in LeonAI Priority ERP, a maintenance module rather than a business one.

Opens a new customer record in LeonAI Priority ERP from data captured elsewhere, so sales and accounting work from the same file.

Produces a file inside the ERP, useful when a scenario generates a document that belongs with a customer or an order.

Adds a new record to a form you pick from the list, the general-purpose writing module when no dedicated one such as Create a Customer fits.

Drafts a new invoice in LeonAI Priority ERP from an order or a payment recorded in another app, so billing no longer depends on retyping.

Builds a new price offer, the quote your client receives, directly in the ERP from the request that triggered it.

Adds a line under an existing record, at sub-form level, rather than creating a separate record.

Creates an entry in a grandchild form, the level below a sub-form line, where a line carries its own details.

Removes a record from the form you choose, which keeps the ERP in step when something disappears in another tool.

Takes one line out from under a record while leaving the record itself in place.

Clears a single entry at grandchild level, the deepest of the three form levels these modules name, and leaves the line above it untouched.

Reads a few sub-forms at once, an older module Make still offers for scenarios built before it was flagged Deprecated.

Fetches files or documents held in the ERP so the next module can send, store or archive them wherever your team works.

Pulls the records of the form you select, the simplest way to bring ERP data into a scenario.

Reads the same kind of records as Get Items Of Selected Form, in an advanced version worth opening when the plain module returns more than you need.

Lists the lines that sit under a record, one bundle per line, ready for the next module to use one by one.

Offers the sub-form reading with more control, handy once the plain version brings back lines you then have to sort through.

Reads entries at grandchild level, under a given sub-form line, for flows that need the finest detail of a record.

Brings back the details of one order so the rest of the scenario can reuse them without a manual lookup.

Reads one price offer from the ERP, so you can follow a quote once it has left sales.

Lists the lines of a price offer, one bundle per line, for when the detail matters more than the summary.

Reads back the text stored under a record at sub-form level, the counterpart of Add a Text to a Sub-Form.

Pulls the text written at grandchild level, two steps below the main record, and hands it to the next module.

Downloads a file from a web address into the scenario, turning a plain link into a file the next module can handle.

Returns the SKUs of your catalog as a stream of bundles, one per item; as a search module, it can bring back none, one or many.

Reaches any endpoint of the LeonAI Priority ERP API with the connection you already set up, to cover what the listed modules leave out.

Finds the customers that match what you give it and returns none, one or several of them as bundles.

Looks up invoices in LeonAI Priority ERP and hands back what the ERP holds about them.

Goes down to the lines of invoices, so you can work product by product instead of invoice by invoice.

Finds the orders matching your criteria, the entry point when you do not yet know which order a scenario should handle.

Checks whether an item code exists in the ERP and returns what it finds, so later modules work on a real item.

Searches any form you choose, the generic search for everything that has no dedicated one like customers, orders, invoices or SKUs.

Changes an existing record in the form you select, so a correction made elsewhere reaches the ERP without anyone reopening it.

A second route for changing an existing ERP record: as its name says, this module goes through the WebSDK, while Update a Form takes the standard route.

Corrects one line inside an ERP record without touching the rest: judging by the module names, a sub-form is the level that sits under a form.

Rewrites one entry in a grandchild form, the deepest of the three form levels these modules name, sitting under a sub-form line.

Stores a file picked up elsewhere in your scenario in LeonAI Priority ERP, so the paperwork sits next to the record your team already works on.