Actions206
- Accessory Actions
- Actual Content Actions
- Alternative Actions
- Appointment Actions
- Appointment Crew Actions
- Contact Actions
- Contact Person Actions
- Contract Actions
- Cost Actions
- Crew Actions
- Crew Availability Actions
- Crew Rate Actions
- Equipment Actions
- Equipment Assigned Serial Actions
- Equipment Sets Content Actions
- Extra Input Field Actions
- Factor Actions
- Factor Group Actions
- File Actions
- File Folder Actions
- Folder Actions
- Invitation Actions
- Invoice Actions
- Invoice Line Actions
- Leave Mutation Actions
- Leave Request Actions
- Leave Type Actions
- Ledger Code Actions
- Payment Actions
- Project Actions
- Project Crew Actions
- Project Equipment Actions
- Project Equipment Group Actions
- Project Function Actions
- Project Function Group Actions
- Project Request Actions
- Project Request Equipment Actions
- Project Type Actions
- Project Vehicle Actions
- Purchase Order Actions
- Purchase Order Cost Actions
- Purchase Order Global Cost Actions
- Quote Actions
- Rate Actions
- Rate Factor Actions
- Repair Actions
- Serial Number Actions
- Status Actions
- Stock Location Actions
- Stock Movement Actions
- Sub Rental Actions
- Sub Rental Equipment Actions
- Sub Rental Equipment Group Actions
- Subproject Actions
- Subtask Actions
- Supplier Actions
- Task Actions
- Task Assignment Actions
- Task Status Actions
- Tax Class Actions
- Time Registration Actions
- Time Registration Activity Actions
- Vehicle Actions
Equipment → Create
AI-generatedSummary
Creates a new equipment item in Rentman by sending the chosen Additional Fields as the JSON body of a create request to the equipment endpoint.
Inputs
- Additional Fields — Collection of optional fields sent in the request body. Only fields you add are sent. Options: Name, Code, Unit, Type (normal/set/consumable), Is Physical (Physical equipment/Virtual package), Is Combination, Rental / Sales (Rental/Sale), Price (default rental price per period), List Price, Critical Stock Level, Stock Management (Track stock/Exclude from stock tracking), Strict Container Content (Unrestricted/Strict), In Planner, In Shop, Internal Remark (shown on packing lists), External Remark (shown on financial documents). Linked records are given as API paths: Folder (/folders/0), Factor Group (/factorgroups/0), Image (/files/0), Ledger (/ledgercodes/0), Tax Class (/taxclasses/0).
- Request Options — Node-level HTTP settings: batching (items per batch, default 50; interval between batches, default 1000 ms), ignore SSL certificate issues, proxy URL, and timeout (default 10000 ms).
Output shape
One item per input item, containing the equipment record returned by the Rentman API for the newly created equipment.
The source pack contains only stubs, so the exact response shape is not visible. The fields are routed declaratively in the request body. The Additional Fields collection is shared with the Update operation. Rentman's own required-field validation (for example, a name) is not enforced by the node, so the API may reject a request that lacks the fields it needs.
Examples
Example 1: Add a new rental light fixture to the catalog
Additional Fields: Name = 'LED Par 64', Code = 'LED-064', Type = normal, Rental / Sales = Rental, Price = 15, Stock Management = Track stock, In Planner = true.
Example 2: Create a sellable consumable placed in a folder with tax class
Additional Fields: Name = 'Gaffer Tape', Type = consumable, Rental / Sales = Sale, List Price = 12.5, Folder = /folders/12, Taxclass = /taxclasses/1, In Shop = true.