ProGlove documentation

The MAI screens are chosen to mirror the simplicity and legibility emphasized inProGlove’s UX guidelines. The Work3 layout provides structured data entry with two action buttons, while the T1 notification keeps follow-up messages short and unambiguous. Together, they create a natural, glanceable workflow that requires minimal cognitive effort.

This creates a closed feedback loop between worker, device, and system - every scan, input, and response travels through MQTT, while n8n orchestrates the logic and updates the shared Google Sheet.

1. The worker scans an article barcode with their ProGlove MAI.

2. The MAI displays aWork3 T3 screen, showing key information: product code, expected quantity, and storage location - this is ourChoose Item Flow.

3. The worker can use thenum wheel inputto edit the quantity or use on-screen buttons to confirm or mark as unavailable.

4. Once an action is taken, the devices sends an MQTT update that triggers the Confirm Quantity Flow in n8n.

5. The MAI then provides immediatevisual and haptic feedbackand transitions to aNotification T1 screen, guiding the worker to the next item.

1. TheMQTT Triggerreceives an event withevent_type = scan.

2. Theswitch noderoutes it to theChoose Itemlogic.

3. n8n queries the Google Sheet for a matching product ID.

4. Based on the result, we send one of several responses back to the MAI (via MQTT):

   • Product found:display aWork3 T3template - a structured layout optimized for short on-wrist reading. It contains fields forProduct,Location, andQuantity, with input enabled on the quantity field.

   • Already picked:issue anErrorFeedback(sound, LED, vibration) followed by aNOTIFICATION_ALREADY_DONEmessage using the T1 Notification template.

   • Not found:show a warningNOTIFICATION_NOT_FOUNDmessage with theWARNINGicon, also via the T1 Notification template.

1. TheMQTT Triggerreceives the event, which includes ascreen_context.ref_ididentifying which screen (and therefore which inventory row) the user interacted with. We use thisref_idto determine which product entry in the sheet to update:

   const screen_ref_id = $('MQTT Trigger').first().json.message.screen_context.ref_id
   const row_number = screen_ref_id.replace("INVENTORY_ROW_", "")
   return_values['row_number'] = row_number

   This mapping makes the flow stateful - no external session storage is needed. Theref_iddirectly encodes which inventory line the user is confirming.

2. TheCode nodeextracts the confirmed quantity from the message payload:

   varconfirmed_qty=$input.first().json.message.screen_context.screen_views_contexts[0].workflow.fields_contexts[1].text.content

   var confirmed_qty = $input.first().json.message.screen_context.screen_views_contexts[0].workflow.fields_contexts[1].text.content

   If the “Unavailable” button is pressed, quantity is set to0.

3. TheGoogle Sheetsnode then updates the corresponding row using therow_numberas a key:

   "columns": {  "row_number": "={{ $json.row_number }}",  "Quantity_Present": "={{ $json.confirmed_quantity }}",  "Date": "={{ $json.date }}" }, "matchingColumns": ["row_number"]

   "columns": {
     "row_number": "={{ $json.row_number }}",
     "Quantity_Present": "={{ $json.confirmed_quantity }}",
     "Date": "={{ $json.date }}"
   },
   "matchingColumns": ["row_number"]

4. Once the update is complete, the workflow providespositive feedbackvia MQTT:

   "feedback_action_id": "FEEDBACK_POSITIVE"

   "feedback_action_id": "FEEDBACK_POSITIVE"

   followed by aNOTIFICATION_NEXTmessage to guide the user to the next location:

   "pg_ntf_t1": {  "message": "Proceed to {{ $json['Storage Location'] }}",  "tagline": "Article Updated",  "icon": "SUCCESS" }

   "pg_ntf_t1": {
     "message": "Proceed to {{ $json['Storage Location'] }}",
     "tagline": "Article Updated",
     "icon": "SUCCESS"
   }