OData
AI-generatedSummary
Query, create, update, delete, or upload files to records in a Priority entity through OData. Choose an entity, then configure filters, record data, keys, or file input for the selected action.
Inputs
- Action (required) — Choose Query, Create, Update, Delete, or Upload File. Query builds an OData read; Create inserts a record and can include subform rows; Update and Delete identify records by key or filter; Upload File attaches a file to records identified by key or filter.
- Entity Name (required) — Select or enter the Priority entity/form name, such as ORDERS or SUPPLIERS.
- Query filters and options — For Query, use the visual filter builder or enter raw OData $filter syntax. Select parent columns, optionally expand subforms and sub-subforms with their own fields, filters, limits, and sort order, and set parent order, limit, and offset. The
inoperator is unsupported in raw filters. Wildcard filters are translated to OData functions. - Record data — For Create or Update, provide field values as a JSON object or key-value pairs. Create can also add subform rows as JSON. Numeric values must be numbers in JSON mode.
- Record lookup — For Update, Delete, or Upload File, identify records by primary key or filter conditions. By Filter affects every match. Bulk Update and Delete do not support wildcard/LIKE conditions and fail rather than applying a broader filter.
- File input and attachment settings — For Upload File, provide a binary property (default
data) or a direct URL, choose the attachment subform (defaultEXTFILES), and optionally set a file description or extension. URL downloads do not support authentication. - Connection overrides — Optionally override connection settings such as Priority URL, company, credentials, language, or Priority token for this node.
Output shape
A list of n8n items containing the operation response data.
Query returns matching records, including requested expansions. Create, Update, Delete, and Upload File return the Gateway response; bulk actions may affect multiple records when using filters. Exact response fields depend on the action and Gateway response.