Skip to main content

Mass Upload records (CSV)

The Mass Upload feature lets you create many text records from one CSV file. Each row represents one record. This is useful for importing interview transcripts, research notes, call transcripts, and other text-based source material.

The importer supports text records only. It does not download audio, video, or files from URLs. NEXT uploads the contents of each text cell as a text/plain record and also preserves the content as Markdown.

Supported columns

ColumnDescription
text (required)Record content. Markdown formatting is supported. Rows without text are ignored.
title (optional)Record title.
recordedAt (optional)Full ISO 8601 timestamp, such as 2026-07-01T09:00:00.000Z. The import time is used when omitted.
tags (optional)Record labels. Separate multiple labels with line breaks inside the same cell.
source (optional)Where the record came from, such as Customer interview or Research repository.
contact (optional)Person associated with the record.
context (optional)Additional source context.
record_type (optional)Semantic record type used for analyzer routing, such as survey_response or product_review.
account_id (optional)External account ID. NEXT converts it to an internal Teamspace-specific ID before linking it.
account_name (optional)Account name used to create and link an account when account_id is not provided.
account_industry (optional)Industry for the created or updated account.
account_region (optional)Region for the created or updated account.
account_segment (optional)Segment for the created or updated account.
account_employee_size (optional)Employee-size value for the created or updated account.
account_status (optional)Status for the created or updated account.
account_account_type (optional)Account type for the created or updated account.
account_arr (optional)Numeric ARR for the created or updated account.

Unknown populated columns are reported as errors. URL, duration, and MIME-type columns are not supported. The MIME type is always text/plain.

Example CSV

recordedAt,title,text,tags,source,contact,record_type,account_name,account_region
2026-07-01T09:00:00.000Z,"Onboarding interview","# Interview transcript

The customer found the setup **easy**, but wanted clearer reporting.","Interview
Onboarding","Customer interview","alex@example.com","survey_response","Acme Inc","EMEA"

Account linking

Account linking behaves the same as the highlight CSV import:

  • When account_id is present, NEXT treats it as an external source ID, derives the internal Teamspace-specific account ID, and links the record. It does not create an account from the other account_* columns.
  • When account_id is omitted and account_name is present, NEXT creates or updates the account and links it to the record.
  • Repeated rows with the same account share the same generated account.
  • Empty account fields do not clear values already stored on an account.

Duplicate records

NEXT derives a stable record ID from the Teamspace, text, labels, and record timestamp. Uploading the same row again produces the same ID, so the duplicate record is ignored rather than updated. Changing one of those values creates a different record.

When recordedAt is omitted, NEXT uses the import time. Re-uploading that row later can therefore create another record. Include a stable recordedAt value when repeatable duplicate detection matters.

Record-minute allowance

The import is accepted when the Teamspace has more than zero imported-record minutes remaining. The CSV does not require or calculate record duration. When no imported-record minutes remain, NEXT rejects the complete file before creating records or accounts.

After the import

NEXT sends a completion email showing how many records and accounts were created and how many duplicate records were ignored. The record content is processed asynchronously, so a newly created record may take a short time to become available.

Troubleshooting

  • A row was not imported: Ensure its text cell is not empty.
  • The timestamp was rejected: Use a complete ISO timestamp such as 2026-07-01T09:00:00.000Z.
  • Labels did not split correctly: Put each label on a separate line within the same CSV cell.
  • Unexpected field errors: Remove unsupported columns or make sure the supported header names match exactly.
  • The complete file was rejected: Check that the Teamspace has imported-record minutes remaining.