Every Workflow Node, Explained

Data Source: Rows from a database table, an Excel or CSV file, a webhook, or a table typed into the node. Each row becomes one record. It can watch a database for new rows, watch a folder for new files, or watch one growing spreadsheet for added rows.
Example: New rows in the orders table print a label each; files dropped into a hot folder print automatically.

Marketplace: Pulls orders from a connected marketplace integration. One order per run.
Example: A new Shopify or Trendyol order prints its shipping and product labels.

Scheduler: Fires the workflow on a schedule you set, in your time zone.
Example: Every morning at 6:00, print the day's expiry labels for the kitchen.

Event: Fires when something happens inside LabelInn: a print job stops for ribbon, labels or a jam, fails or times out, supplies run low, a printer comes back online, a design is published.
Example: The ribbon runs out mid-job, the shift lead gets an email.

HTTP Fetcher (polling): With polling switched on and nothing wired into it, the Fetcher calls an external API on a timer and starts one run per new item it finds.
Example: Poll a supplier API and print a goods-in label for each new delivery.

Transform: Rename, cast, drop, merge, split, concatenate, extract with a regular expression, or build a field from a template.
Example: Split a scanned GS1 string into GTIN, lot and expiry.

Lookup: Finds the matching row in another source, by a key from the record, and merges it in. A miss can be branched on, or made to fail the run.
Example: A webhook sends only a GTIN; Lookup fetches the product name and price from your Excel catalogue.

HTTP Fetcher: Calls an external HTTP API in the middle of a run and adds the response to the record.
Example: Fetch today's exchange rate before printing a price label.

AI: Sends a prompt and the record to an AI model and merges structured JSON back. Modes: transform to JSON, classify into one of your labels, extract fields from free text, or read text from an image. Uses your company's AI credits; a bad answer fails the node instead of slipping through.
Example: Classify a free-text product description into the right hazard category.

Compliance Pack: Derives regulated label content. Today this is GHS / CLP: pictograms, signal word, hazard and precautionary statements in 25 languages, and the required label and pictogram size.
Example: Turn H and P codes from your database into a complete chemical label. See GHS label software.

Design: Fills a label design with the record. Fields bind by name automatically, or you map them by hand. Uses one of your designs or a ready-made template.
Example: The record's sku fills the label's sku barcode.

Cargo: Creates a shipment with a connected carrier integration and returns the tracking number and the carrier's label.
Example: Create the shipment, then print the carrier label at the pack bench.

Print: Sends the filled design to a printer. The printer is chosen by hand, taken from a field in the record, or picked automatically. The job goes to the online device that owns that printer.
Example: Route each warehouse's labels to its own printer using a printer column.

Order to shipped label. Marketplace → Cargo → Design → Print → Write-back. The order arrives, a shipment is created, the label prints at the pack bench and the order is marked as printed.

File drop to labels. Data Source (watched folder) → Router → Design → Print → File Op. Each row of a dropped spreadsheet prints on the right design, then the file is archived.

One label per line, one summary. Marketplace → For Each → Design → Print, then Notify on the summary. Every line of the order gets a label, and one email reports how many printed.