Plan which CSV columns to send,
and how to handle empty cells.

Skipping a source field can leave a required database column without a value. Enter the database definitions you have confirmed, map all CSV headers, then uncheck the fields you do not intend to send. The tool flags conflicting declarations before you save a planning note.

Free planning tool · 1–5 CSV columns · 1–20 database columns. No file upload, database connection or SQL execution. The JSON is a planning note, not an n8n workflow.

Build a column-selection plan

Do not enter CSV data, credentials or connection URLs. Enter only headers and database definitions you have confirmed. No names or values are inferred.

Destination table namePlanned CSV encoding

1. Record the actual database definitions

Do not check nullable, default or generated merely to pass. If the schema is unknown, ask its owner before saving. integer_text means integer text syntax, not database type/range validation.

DB column 1

DB column nameValue review rule

NullableHas defaultAuto-generated

2. Enter all CSV headers in their original order

Include skipped columns and their destinations, then uncheck them. Preserve spaces and leading zeroes. This screen does not check the actual CSV file.

CSV column 1

CSV headerDestination DB column

Include in importCompletely empty cell policy

3. Review and save the plan

Plan needs attention: 3

TABLE — Table: use 1–64 letters, digits or _, starting with a letter or _. Table name
SOURCE_NAME — A CSV column is empty, duplicated or exceeds 100 characters. (empty)
TARGET_NAME — A database column is empty, duplicated or not a simple identifier. (empty)

View current JSON plan

{
  "schema": 1,
  "encoding": "utf-8-sig",
  "table": "",
  "expected_headers": [
    ""
  ],
  "database_columns": [
    {
      "name": "",
      "nullable": false,
      "has_default": false,
      "auto_generated": false,
      "value_rule": "text"
    }
  ],
  "mapping": [
    {
      "source": "",
      "target": "",
      "enabled": true,
      "blank_policy": "reject"
    }
  ]
}

The saved file contains headers, DB names and settings. Check whether they can be shared. No CSV values, account or connection information is collected. These inputs are not sent to a server or persisted; refreshing clears them.

Next, check the actual values and import results.

This screen checks only the declarations you enter. It does not inspect CSV rows, quoting or encoding, database type ranges and lengths, keys, default expressions, privileges or a running n8n installation. Do not mark a column nullable or generated just to pass the check. Confirm the real schema with its owner.

For a product file containing SKU, name, integer price, stock and an image URL, try the existing 20-row product CSV check. Read the KRW 14,900 offline download contents and purchase conditions before buying. This free planning note is separate: database import, n8n installation and custom mapping delivery are not included in that ZIP.

If you have already run an import, use the import-result review guide to compare source and result evidence. For contact files, use the separate contact CSV trial and its stated limits.