Sometimes you just need the orders in a spreadsheet: to reconcile against payouts, to hand your accountant a quarter, or to slice the data a way WooCommerce will not. The built-in export plugins want their own setup, and you only need this once in a while. This prompt reads the orders and formats them as CSV text right in the chat, so you copy the block out and paste it into a spreadsheet. No file ever touches your server, because the agent has no way to write one.
Build me a CSV of orders. Read only. Pull every order from [1 January] to[31 March] with status [completed or processing], then read each one for thesecolumns: order number, date, status, customer name, email, order total, andcurrency. Lay it out as proper CSV, one header row then one row per order,commas between fields and quotes around anything that contains a comma. Justgive me the CSV in a code block so I can copy the whole thing. If any order ismissing a field, leave that cell blank rather than guessing, and tell meafterwards which ones had gaps.Why this is safe to run
Both abilities are reads: one lists the orders in your range, the other reads each order for its detail. Neither can change an order, and the agent cannot save a file anywhere, so the “export” is just text it prints for you to copy. That also means the customer data in the CSV, including the email and phone that a single-order read returns under the Integrations security disclaimer, only ever lives where you paste it. Handle the copied block like any other customer export.
Already connected? Skip the paste. Ask your agent for the “export orders to CSV” recipe, name your date range and columns, and it formats the same CSV from your own store.