InvenTree

The InvenTree integration writes TofuPilot test data into your InvenTree instance, so build outputs, stock items, and test reports stay in sync with what happens on the factory floor.

Connect InvenTree

You connect InvenTree once per instance using an API token that inherits the permissions of the user that generated it.

Actions

The integration exposes six actions that cover the most common workflow patterns for production data.

Every picker in these actions reads live from your instance — locations, parts, build orders, build outputs, test templates, and label templates — and all six are searched against InvenTree as you type, so a large catalogue is never dumped to the browser. Any of these fields can also take a {{variable}} instead, in which case the value is resolved when the workflow runs.

Identifying the stock item

Upload test result, Update stock status, Transfer stock, and Print label all act on an existing stock item, and share the same Stock Item field with a Serial number / ID switch next to it. New nodes start in Serial number mode.

In ID mode the value must be digits only. A value like 12-A is refused instead of being read as 12, so a malformed variable can never send the write to a different record. The same rule applies to every other ID field in the integration.

Serial numbers are only unique per part in InvenTree, so Serial number mode adds an optional Part IPN field. Leave it empty to search across all parts — if the serial then matches items on more than one part, the action fails and asks you to set it. Fill it, from the part picker or from a variable such as {{part.number}}, to scope the lookup to that part.

If a variable in the Stock Item or Part IPN field does not resolve, the action fails rather than falling back to a wider search.

Create stock item

Pick the part by IPN or by numeric ID, using the same switch as above. In IPN mode the value is resolved against InvenTree at execution time, so you can pass the trigger's part number variable (for example {{part.number}}) instead of a fixed part.

The find-or-create behavior on the serial number keeps re-runs idempotent, so a workflow that fires on unit_created can safely be retried without leaving duplicate items behind.

Reuse does not write to the item it found: Location, Status, Batch, and Notes apply only when a new item is created. Any field you configured that was not written is listed under fieldsNotApplied in the step result, so a re-run that quietly ignored them is visible instead of just reporting success.

The action exposes three output variables that downstream nodes can reference:

The step result also carries partId, the resolved part primary key, and fieldsNotApplied on the reuse path.

A common pattern is to chain Create stock item with Upload test result and pass {{<nodeId>.stockItemId}} as the stock item of the second node.

Upload test result

InvenTree records test results against a test template defined on a part, not against a free-text name. Pick the template from the list — entries are labelled test name — part (IPN), since the same test name usually exists on several parts. If the Stock Item field is in serial mode and Part IPN holds a fixed value, the list is narrowed to that part. The search matches the test name and its description, not the part — to narrow by part, set a fixed value in Part IPN.

Choosing From run outcome on a workflow that is not run-triggered leaves nothing to read, and the action fails with that message rather than silently recording a fail.

The action posts the stock item, the template, the result, and the optional value and notes. It does not upload attachments, and it does not send a timestamp — InvenTree stamps the result itself.

The action exposes three output variables that downstream nodes can reference:

Update stock status

Identify the stock item, then pick the new status. The action writes the status straight onto the stock item record.

The action exposes two output variables that downstream nodes can reference:

Stock statuses

The status dropdown offers InvenTree's built-in stock status codes:

Instances that define custom status codes are not listed here.

Transfer stock

Identify the stock item, then set the destination.

The transfer moves the item's whole quantity, which the action reads from InvenTree rather than asking you for it.

The action exposes two output variables that downstream nodes can reference:

Complete build output

This action completes one specific output of one build order, so it needs both — there is no inference from the build alone.

The action exposes three output variables that downstream nodes can reference:

Print label

The action exposes three output variables that downstream nodes can reference:

Limits

The InvenTree action inherits TofuPilot's HTTP caps and the per-token throttles your InvenTree instance applies.

• InvenTree's own per-token rate limits apply.
• Picker lists are capped, so a large catalogue is never fetched whole. Narrow with the search box, or pass the ID or IPN directly if what you want is not offered.
• Action runtime and retries match the HTTP action.