Documentation Data Import Upload Import File
Detailed guide

Upload Import File

The upload and preview step for validating and committing one prepared CSV file into the workspace.

This sub-workflow separates file preparation from file execution. Preview validates without saving so bulk updates stay controlled and reversible-by-threshold.

Open demo page Back to overview
Quick summary Step by step Guardrails Troubleshooting Related workflows

Quick summary

  • Run Test changes before every real import so errors surface without touching live data.
  • Read the first validation error carefully before editing the CSV again.

Put it into practice

  1. Confirm the selected entity tab matches the file content you prepared before touching the file chooser.

    InteractionsData Import page: verify the active tab before selecting a file.
    Open workflow: Data Import

  2. Choose the intended CSV file, then set the import mode and rollback threshold consciously. Overwrite deletes existing records, so treat it as a deliberate replace.

    InteractionsUpload card: select the CSV, choose Update or Overwrite, and set the rollback threshold.

  3. Run Test changes to preview. Review the validation output and resolve the first blocking issue before reattempting.

    InteractionsUpload card: click Test changes and inspect the reported row errors.

  4. Re-run Test changes on the corrected file until the preview is clean, then run Import Data to commit and confirm any Overwrite warning.

    InteractionsUpload card: click Test changes again, then Import Data when clean.

  5. Confirm the import history status and then verify imported rows in their destination views before closing the task.

    InteractionsImport history: check the Status badge and errors, then open the relevant destination pages.
    Open workflow: Projects

What to review

CSV file chooser

Select the exact CSV you intend to import; wrong-file mistakes usually start here, so double-check the filename.

Import mode selector

Update refreshes existing records matched by name and adds new ones; Overwrite deletes existing records for the entity first. Overwrite prompts for confirmation.

Rollback threshold input

Sets the percentage of row errors tolerated before the import rolls back. Preview ignores this and never saves.

Test changes action

Runs a preview that validates the file and reports row errors without writing any data.

Import Data action

Commits the import once the preview is clean, applying mode and rollback-threshold rules.

Import history and errors

Shows the outcome (Success, Test, Partial, or Failed) with an expandable list of per-row errors so failures are explainable.

Guardrails

  • The selected tab and uploaded file structure must match for the import to succeed cleanly.
  • Preview never saves, so a clean Test changes result is the safe gate before committing with Import Data.
  • Overwrite removes existing records before import, so confirm the file is complete and correct before running it.
  • Only administrators allowed to perform bulk data changes should use this workflow.
  • Overwrite imports are the most destructive action here and should be limited to trusted operators.

If it starts drifting

  • If the file keeps failing, re-download the template and compare headers directly instead of guessing.
  • If the status is Partial, expand the error list to see exactly which rows were rejected and why.
  • If Import Data is blocked, re-run Test changes first, since committing usually requires a clean or within-threshold preview.