Salaxy Import
Manage payroll data imports by asking: source files, transformations, converted datasets, import plans and import runs.
Manage your payroll data imports by asking. Salaxy Import lets your AI assistant work with the data you bring into Salaxy from other systems: the uploaded source files, the transformations that map them to Salaxy’s structures, the converted datasets waiting for import, reusable import plans and the record of every import run.
“Which source files have we uploaded for Kahvila Aurinko, and which transformation maps the employee list?”
The assistant reads and maintains the definitions. Salaxy does the parsing, validation and the import.
What you can do
See what is there. List the uploaded source datasets of a company, look at their columns and a sample of the rows, and find the transformations and import plans that use them.
“Show me the columns of the latest salary file and the first rows.”
Author and maintain transformations. Describe how a source column maps to a Salaxy field and let the assistant write or revise the JSONata transformation, versioned, with notes on why it changed.
“Map ‘Tuntipalkka’ to the hourly salary and ‘Henkilönumero’ to the employee number, and save it as a new version.”
Keep track of imports. Browse the converted datasets with their validation counts, see which rows failed and why, and read the outcome of past import runs.
“How many rows failed in yesterday’s employee import, and what were the errors?”
Organize re-runnable imports. Save a named import plan that binds a target schema and a transformation, in folders per customer or per year.
“Save this as the plan ‘Kahvila Aurinko / palkat 2026’.”
Work for many companies. Accounting offices choose the customer company first; everything the assistant saves belongs to that company.
Built to be trusted with your data
- Nothing runs by itself. The assistant saves definitions and records, and may try a transformation on a sample of rows to show you what it produces. It cannot transform a whole dataset, validate it or start an import: those happen in Salaxy, when you do them.
- Your login, your permissions. You sign in with your own Salaxy account. The assistant sees only the companies you already have access to, and a company chosen by its Business ID is checked against them.
- Whole datasets stay in Salaxy. The assistant reads rows as clearly marked samples and never replaces a dataset with a sample.
- Deleting needs your word. The assistant deletes a dataset, transformation, plan or run record only when you ask for that object to be deleted.
- One source of truth. Everything is stored in the Salaxy API. The connector keeps no data of its own.
What it does not do
Salaxy Import does not receive files from the chat, convert files, run transformations, schedule imports or import anything. Upload source files in Salaxy; use the assistant to understand, author and organize.
Works with your assistant
Salaxy Import is an MCP connector: add it to an assistant that supports MCP, such as Claude Desktop, and sign in with your Salaxy account. Ask in Finnish or English.
Availability
Finland. In development against the Salaxy test environment; see DEVELOPMENT.md for the current status.
Ready to start with plugins?
Find all our plugins in Quartal Hub. Open now for registrations to Early adopters.
If you want to create your own plugin, get started for free at plugin.quartal.com.