Import
Bring a CSV into a table. Appenda scans the file, lets you map columns to fields, then adds every row in one job.
Appenda scans the file and reads sample values from each CSV column.
Before you start
- A workspace table to import into, or use Import CSV when creating a new table from the sidebar + menu.
- A
.csvor.tsvfile with a header row, up to 100,000 rows and 256 columns. - Know which fields you need. See Fields for types.
Appenda works out the separator (comma, semicolon, tab, or pipe) and the text
encoding, including files saved from older versions of Excel. A blank header
becomes Column 1, Column 2, and so on. A repeated header gets a number.
Steps
Open import
Into an existing table: click Import in the table toolbar (right cluster, next to Export).
Into a new table: sidebar + → Import CSV → name the table → pick the file.
Scan and map
Appenda reads your CSV and proposes a field for each column. Pick or change each mapping, then import.
| Suggestion | When you see it |
|---|---|
| Existing field | The header matches a field already on the table. |
| Matched alias | A common export header maps to a known field. Amber hint text shows what matched. |
| Create "…" | Appenda creates a new field, typed from the values it scanned. |
| Create "…" as number | You want the new field as a different type than Appenda picked. Each type has its own option. |
| Skip column | You do not need that column in the table. |
- Open your file. Appenda shows how many rows it found.
- Review each column. Sample values from the file appear underneath so you can confirm the mapping before you import.
- Change any dropdown. Appenda treats spaces, dashes, and capitalization in headers as equivalent.
- On a table with enrichment columns, tick Run enrichment columns on the new rows to run them on the imported rows once the import lands. It is off by default and available on local workspaces.
- Click Import N rows when at least one column is mapped.
Common export headers such as Primary Email, Company Name, and work_email
usually map without manual edits. You can override any suggestion.
Values that don't fit
Appenda checks every value against the type of the field it maps to. When some values don't fit, a line under that column says how many, for example "3 values don't fit Number and will be left empty."
- For a new field, pick the as text option to keep those values.
- For an existing field, change the field's type first if you need them. See Fields.
One bad value never stops the import. Values that don't fit are left empty, and the version history entry for the import says how many.
If the import fails
The dialog stays open with your mappings, and the reason shows in the footer. Fix the cause, then click Import N rows again. You do not need to pick the file or map the columns a second time.
Problems with the file itself name the line, for example "Line 12 has 5 values, but the header has 4 columns." Fix the file and open it again.
Check that it worked
- Rows appear in the grid.
- The status bar shows an updated
visible/totalcount. - Version control records one import summary for the job, not one entry per row.
Tips
- Map required identity columns first (name, email, domain) before optional enrichment fields.
- Run enrichments from the toolbar after the import finishes, or tick Run enrichment columns on the new rows before you import. See Run a column.
- Large files scan before import applies. Wait for rows scanned before clicking Import.