Operating import templates

Every time you import a file, Assemblified needs to know which column of your file feeds which field: which one is the SKU, which one the quantity, how the numbers and dates in it are written. When you save that answer, you get an import template — the mapping the next file of that kind is read with. A connected assistant can list your templates, explain them, and with write access correct and delete them.

What it takes

Listing and reading templates needs nothing beyond a connection. Changing or deleting one needs write access: either an API key created with read & write scope or a web-chat connection granted read & write when it was linked. See API keys and Connect claude.ai or ChatGPT.

Import templates are not part of the Enhanced plan gate. Every store on every plan can read and change them.

What an import template is

Three things, and the assistant sees all three:

A name, which is how you pick it in the import dialog.
An upload type — the import flow the template belongs to. A template saved for raw materials is only ever offered when you import raw materials.
A mapping and format settings — one entry per field you mapped, each naming the column header in your file (and any alternative spellings of that header), plus how numbers and dates in that file are to be read: US style (1,234.56) or EU style (1.234,56), and which date order.

Only the fields you actually mapped are stored. A field that is missing from the template is a field you left unmapped, not a field with an empty column.

Reading your templates

Ask for all of them, or just the ones for one import flow. Each answer carries the whole template, so the assistant can tell you what a template does without a second look:

“Which import templates do I have for raw materials, and which column does each one read the SKU from?”

“My supplier renamed a column in their export. Which of my templates still point at the old name?”

That second question is the one this surface is really for: you know the file changed, and finding which saved mappings are now wrong is tedious by hand.

Correcting one

With write access, the assistant can rename a template, re-point its columns, or change how its files’ numbers and dates are read.

“In my Acme template, the SKU now comes from the column ‘Artikelnummer’ — fix it.”

Two things to know before you ask for a change.

Each part you change is replaced whole. If the assistant changes the mapping, it sends the complete list of mapped fields, not just the one you mentioned. A well-behaved assistant reads the template first and sends it back with your one change applied — if you want to be sure, ask it to tell you the full mapping it is about to save.
What you do not mention is left alone. Changing the name does not touch the mapping, and changing the mapping does not touch the format settings.

Deleting one

The assistant can delete a template you no longer use. This is immediate and there is no undo: what is lost is the mapping itself, which you would have to rebuild by walking the import dialog again with a file in front of you. Nothing else in Assemblified refers to a template, so nothing else breaks.

Ask it to name the template it is about to delete, and confirm it is the right one.

What it cannot do

It cannot create a template, and this is on purpose. A template is what comes out of walking an import dialog with a real file open: the field names have to match the flow you are importing, and the column headers have to match a file only you have. An assistant inventing one would be guessing at both halves, and you would find out on your next import. Save the template from the import dialog once; from then on the assistant can keep it correct.

It cannot move a template to another import flow. The upload type is fixed when the template is saved. To use the same mapping for a different flow, save a new template from that flow’s import dialog.