Orders.xlsx + Customers.csv
Files remain in the desktop app and their schema is inspected before execution.
Short answer: Add files, select join keys and duplicate policy, map output fields, then review unmatched rows before writing a new workbook.
Files remain in the desktop app and their schema is inspected before execution.
The final output comes from the same reviewed preview result.
Join Orders with Customers by customer_id. Keep every order, add customer_name and region, and flag unmatched IDs.
You can add more conditions. Each message updates the active plan instead of creating an unrelated result.
Confirm files, sheets, schema, and workbook features that need preservation.
The planner selects constrained actions from the current instruction, schema, and approved samples.
Edit steps and inspect Result, Diff, Issues, and the effect of each action.
Create a new file by default; source replacement requires a verified backup.
join_sourcesselect_columnsrename_columnsvalidate_requiredColumn references and parameters validate against the current schema; a plan that cannot compile safely does not execute.
No. Transformation runs locally. The planner receives only the current instruction, schema, and small samples you approve.
Excel is not required to process supported CSV and XLSX files. You can use Excel or another compatible app to open the finished result.
Tablyra asks for clarification or creates an Issue instead of guessing a field or silently running a high-risk operation.
Yes. Additional messages update the same validated plan and local preview until you choose to save the final output.
Download the desktop app, open an Excel or CSV file locally, and build a reviewable result through conversation.