CHATBOTS

Move-a-SKU Bot: Update Bin Location from Teams

Lets a floor worker tell the Teams bot they moved stock to a new bin; the bot confirms the SKU, writes the new location to Airtable, and logs the move for the audit trail.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerchat
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWorker sends a move instruction in TeamsMicrosoft Teams
  • ActionExtract SKU and target bin from textOpenAI
  • LogicValidate SKU exists and bin is well-formed
  • ActionUpdate bin-location field in AirtableAirtableAirtable
  • OutputConfirm old and new bin in TeamsMicrosoft Teams

What it does

Turns the inventory lookup bot into a two-way tool. A worker types something like "moved SKU 4471 to bin C-12" and the bot updates the bin field in Airtable, then confirms back in chat. Every move is written so locations stay accurate without a trip to a terminal.

When to use it

Use it when stock gets relocated during slotting, consolidation, or cycle counts and the system-of-record goes stale because nobody walks back to update it. This captures the change at the moment it happens, from the worker's phone in Teams.

How it works

  1. 1A worker sends a move instruction to the bot in Teams.
  2. 2An OpenAI step extracts the SKU and the target bin from the free-text message.
  3. 3A logic step validates the SKU exists and the bin code is well-formed; ambiguous input bounces back for clarification.
  4. 4The flow updates the bin-location field on the matching Airtable record.
  5. 5The bot replies in Teams confirming the old and new bin, closing the loop with the worker.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Microsoft TeamsChannels, chats, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AirtableBases, tables, views, automations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.