Every month-end

Every month-end I type eighty rows of an Excel sheet into our sales system from 2005, because it has no import and no API.

How it goes now

Read the next row.Switch to Depot.New order.Type the customer.Tab. The item.Tab. The quantity.Save.Copy the order number.Back to Excel. Paste it. Next row.

Eighty rows, one field at a time.

Tell Kitewell once

You

For each row of month-end.xlsx, enter the order in Depot and write the order number Depot gives it back beside the row.

That's the whole setup. Kitewell lays out every step for you to check, and nothing is saved until you apply it.

Then it runs on its own

month-end.xlsxRunning on this computer

Read the rows to runFrom the workbook you link. Before anything runs, you see which rows will run, and why any other row won't.Done
Enter one orderFor each row: opens Depot, enters the customer, item, and quantity, saves, and reads the order number Depot shows.Done
Write the order number backEach order number goes into the workbook beside its row, with the row's status.Done

What you get instead

month-end.xlsx

79 orders entered. 1 row failed and is marked in the workbook.

month-end.xlsx

Customer	Item	Qty	Order No	Status
Alder & Co.	A4 paper	5	SO-11842	Done
Brightline Labs	Toner T-20	2	SO-11843	Done
Cobalt Freight	Label rolls	10		Failed
Dunmore Clinic	A4 paper	3	SO-11844	Done

Sample data

Good to know

The model works out the first order. Later rows replay what worked with their own values: on Windows by Depot's own fields and buttons, on macOS from the screen. Where a screen no longer matches, the model takes over from there.
Try a few rows first. Each row is its own run with screenshots, and a row that failed can run again on its own.
Desktop steps use this computer's screen, unlocked, one row at a time. They wait until nobody has touched the mouse or keyboard for five seconds, and pause when you do.

What it needs