On scan or row events you can notify, email, POST a webhook, block save, change field values, update or adjust matching rows, and control form field visibility—subject to the trigger builder in Cloud.
Inventory automation on shared Cloud sheets
WiScanner Cloud sheet triggers run when barcodes are scanned or rows change. Attach conditions, then notify your team, call a webhook, send email, block a bad save, or adjust a matching row—so routine inventory reactions do not depend on someone watching the grid.
Who it’s for
Teams that already scan into Cloud sheets and want rules for low-stock alerts, validation and downstream HTTP hooks—without building a custom middleware app first.
The problem
Manual follow-ups after every scan do not scale. Spreadsheets do not email you when quantity crosses a threshold or POST to your ERP helper URL.
How it works
- Design the sheet — Columns for barcode, quantity, location and any status fields your rule needs.
- Add a trigger — Pick an event (e.g. barcode scanned, record updated, quantity changed, stock in/out) and optional conditions.
- Choose actions — Notify, play sound, webhook, send email, block save, update/adjust matching rows, or form field show/hide and set value.
- Scale with API when needed — On Team and Business, use API keys / MCP so external tools can read and update stock under the same permissions.
Example sheet fields
| Field | Purpose |
|---|---|
Events | barcodeScanned, recordCreated/Updated, fieldChanged, quantityChanged, stockIn/Out/Count, before/after save, form opened |
Conditions | Compare fields (numeric, text, barcode, dates) before actions fire |
In-sheet actions | set/clear/copy value, increment/decrement, calculate, GS1 extract, lookup from another sheet |
Side effects | notify, email, webhook (HTTP/HTTPS), blockSave, updateMatchingRow, adjustMatchingRow |
Policy | everyTime, onBecomeTrue, oncePerRecord, cooldown |
What you get
- Rules live with the sheet your phones already scan into
- Webhooks for your own integrations—no claim of full ERP sync
- Validation via blockSave and form field rules
- MCP/API on higher plans for agent and script access
Cloud vs local PC scanning
Cloud triggers automate shared online sheets. Classic WiScanner mobile webhooks/Google Drive destinations are a different product path for phone→PC or export flows. Neither replaces a full WMS or guarantees real-time multi-channel store sync unless you build that on your webhook.
Related guides
FAQ
No. Webhooks let you connect your own endpoint. Channel sync is not implied unless you implement it.
Sheet triggers are part of Cloud sheet workflows. API keys and hosted MCP for external agents require Team or Business.
Wisy is an on-demand AI assistant. Triggers are deterministic rules that fire on sheet events without you asking each time.
Cloud triggers run on Cloud sheet saves/scans into Cloud. Local Wi‑Fi typing into Excel on a PC does not execute Cloud sheet triggers.
Start with a live Cloud sheet
Open cloud.wiscanner.com, create a sheet, and scan from the WiScanner mobile app with the same account.