How can we help you?

View Categories

Priority ERP

7 min read

Engini’s Priority ERP activities allow you to create and modify records, activate form activations, and make API calls from your Priority ERP using Priority’s Webhooks module.

Getting Started with Priority ERP #

Prerequisites #

  • Priority API License.
  • Open access to Priority via port 443. If you can’t open this access, you can also just whitelist our IP (see below).
    • 34.159.217.185
    • 34.141.24.31
  • Optional – Dictionary Module: To enable language-specific operations for both CRUD operations (Create, Read, Update, Delete) and procedures, ensure that the dictionary module is activated in your Priority ERP system. By default, the API will operate according to the system language unless specified otherwise.

Connecting Engini to Priority ERP #

  1. Enter your Engini account at https://app.help.engini.io.
  2. Navigate to Connections page by clicking on the Connections on the left sidebar or by clicking here.
  3. Click on the Add connection option located at the topbar.
  1. Choose Priority’s option from the available applications.
  1. Enter the following details in the “Edit Connection” form:
    1. Connection name
    2. API Url including the tabula.ini. for example https://erp.help.engini.io/odata/Priority/tabula.ini.
    3. Database name (company id in companies form)
    4. API Username (Companies that use Priority identity management module should place their personal access token)
    5. API Password (Companies that use Priority identity management module should place “PAT” in all caps)
    6. X-App-Id & X-App-Key (Optional. used when using a dedicated priority connector)
    7. WebSDK Username & WebSDK Password (Optional. used when using a Priority’s form activations, for example, for printing a Price quotation document)
    8. Communication Channel
      Choose the appropriate connection type based on your setup:
      • Cloud- If you are connecting to a database hosted in a cloud environment, select “Cloud”.
      • OPA- If your database is on-premises and you are using an On-Premises Agent (OPA) for the connection, select “OPA”.
        In this case, an additional field will appear:
        On-Prem Agent- Choose the specific On-Premises Agent that you want to use for this connection if you have multiple agents configured.
  2. Click on the Save button located at the bottom of the form.

Triggers #

Record Updated #

This action triggers when a record is updated and sends the updated data to a specified webhook URL for further processing.

  1. URL – The webhook endpoint where the updated record data will be sent. This is the destination that receives the event.
  2. Object Type – Defines which type of record or entity you want to monitor for updates (e.g., item, order, contact).
  3. Add Conditions – Allows you to set specific rules or filters so the action will trigger only when certain criteria are met.
  1. Select from the drop down the field you want to add the condition on.
  2. Select the condition you want the record to meet.
  3. Click on the empty field and the tooltip will pop up showing the options you can choose.
  4. You can populate the field in one of the following options:
    • Static value – number / string. when using strings, you need to surround them with single quotes (‘).
    • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
    • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).
  5. Repeat steps 1-4 for all the fields you want to populate.

Actions #

Create Records #

This action creates a new record in the selected object type with the data you provide in the fields.

  1. Object Type – Specifies the type of record you want to create (e.g., customer order, contact, item).
  2. Add Field – Allows you to define and map the fields and values that will be included in the new record.

  1. Click on the empty field to the right of the dropdown to see a tooltip with all the available options you can use to fill the field.
  2. You can populate the field in one of the following options:
    • Static value – number / string. when using strings, you need to surround them with single quotes (‘).
    • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
    • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).
  3. Repeat steps 1-2 for all the fields you want to populate.

Update Record #

This action updates an existing record in the selected object type using the data provided in the fields.

This action updates an existing record in the selected object type using the data provided in the fields.

  1. Object Type – Specifies the type of record you want to update (e.g., customer order, contact, item).
  2. Record (Customer Order) – A required field that identifies the specific record to update. For each object type, this field will dynamically match the relevant entity (e.g., order ID, contact ID) that was connected or selected.
  3. Add Field – Allows you to define which fields will be updated and assign new values to them.

  1. Click on the empty field to the right of the dropdown to see a tooltip with all the available options you can use to fill the field.
  2. You can populate the field in one of the following options:
    • Static value – number / string. when using strings, you need to surround them with single quotes (‘).
    • Property value from a previous activity (Using the tooltip that opens when clicking on the field).
    • Expression – using functions and/or Previous activity properties and/or static values (Using the tooltip that opens when clicking on the field).
  3. Repeat steps 1-2 for all the fields you want to populate.

Get Record #

This action retrieves a specific record from the selected object type and returns the requested data fields.

  1. Object Type – Specifies the type of record you want to retrieve (e.g., customer order, contact, item).
  2. Record (Customer Order) – A required field that identifies the specific record to retrieve. For each object type, this field dynamically represents the relevant entity (e.g., order ID, contact ID) that was connected or selected.
  3. Output Fields – Allows you to choose which fields from the record will be returned in the response.

Get Records #

This action retrieves a list of records from the selected object type, with options to filter, sort, and limit the results.

  1. Object Type – Specifies the type of records you want to retrieve (e.g., customer orders, contacts, items).
  2. Output Fields – Allows you to select which fields will be returned for each record in the response.
  3. Top N – You can set the maximum number of Sales Order records Engini will return during one workflow cycle (default = all records).
    • If you set Top N = 1, a single record will be returned instead of an array. If no record is found, the action will fail, allowing you to implement an IF condition within the workflow. This can be useful for processes where the existence of a record determines the next steps in the workflow.
  4. Offset – The offset parameter allows you to skip a certain number of records from the beginning of the result set (default = 0 records).
  5. Add Filters – You can add filters to query the Sales Orders and retrieve only the records that met the conditions.
  6. Add Sorting – You can sort the retrieved list by multiple Sales Order fields either Ascending or Descending.

Delete Record #

This action deletes a specific record from the selected object type.

  1. Object Type – Specifies the type of record you want to delete (e.g., customer order, contact, item).
  2. Record (ID) – A required field that represents the unique identifier of the record you want to delete. This value corresponds to the specific object selected (e.g., order ID, contact ID).

Form Activation #

  1. Add the “Form Activation” activity of Priority.
  2. Choose the Form name from the drop down menu. The available forms are the open parent screens and child screens from your Priority account.
  3. Choose the Activation from the drop down menu.
  4. According to the Form name, an identifier field will appear. Enter a static value as you can see at the image below:
  5. Press Run. Each Run can add new fields to fill in.
  6. Repeat steps 4-5 until all required fields are filled up and “Ran successfully” message will appear.
  7. Now you can replace the static value (step 4) with dynamic value from previous activities.

Run Procedure Activity #

Prerequisites:

  1. EPROG form is accessible to API in FORMLIMITED form.
  2. The user used for the integration should have at least read privileges to EPROG form.
  3. The user used for the integration should have privileges to execute the relevant procedure.

To use Priority’s run procedure, follow the following steps:

  1. Add the “Run Procedure” activity of Priority.
  2. Choose the procedure name from the field options tab in the tooltip menu. All the available procedures.
  3. Fill in the required fields with static values first to setup the activity.

  1. Press Run. Each Run can add new fields to fill in. When you need to reset the values you can press the “Reset” button.
  2. Repeat steps 3-4 until all required fields are filled up and “Ran successfully” message will appear.
  3. After the procedure ran successfully, you can now change the relevant static values to parameters to allow the workflow to run using dynamic values.

Send API Request #

This action sends a custom API request to an external service, allowing you to interact with endpoints using different methods, headers, and payloads.

  1. Base URL – The main endpoint of the API you want to call (e.g., the server or service URL).
  2. Relative URL The specific path or resource you want to access, appended to the Base URL.
  3. Method – Defines the HTTP method used for the request (e.g., GET, POST, PUT, DELETE).
  4. Body Type – Specifies the format of the request body (e.g., JSON, form-data).
  5. Body – The payload sent with the request, usually required for methods like POST or PUT.
  6. Add Headers – Allows you to include additional headers (e.g., Authorization, Content-Type) required by the API.
  7. Add Queries – Allows you to add query parameters to the request URL (e.g., filters, pagination).
What are your Feelings

LET’S ENGINE WORK PROCESS

Over 500+ people trusted

© Engini.io 2026 All rights reserved