Bulk import overview

Bulk import creates or updates many records at once from JSON files. Find it under Tools → Octa Editor → Add content.

The flow

1. Upload one or more .json files. One file is one document, a post or a term. File names don’t matter, and are only used in the preview.
2. Dry-run preview. The importer resolves every file and shows, per file, exactly what will happen, such as CREATE or UPDATE → ID 123 → /path/, plus all warnings. Nothing is written yet.
3. Confirm. Only now are the changes applied.
4. Report. You get a per-file result of what was created or updated.

It sorts the batch for you

You don’t need to order the files. The importer processes them in dependency order, terms first, then parent posts, then children. References within the batch are allowed. A parent in one file, a term in another, and a relation to a third all resolve against the same batch, matched by slug.

• Mutual relations (A to B and back) are fine. Relations are wired up in a second pass after all records are saved.
• The one unrecoverable error is a parent cycle, where A is B’s parent and B is A’s. It rejects the whole batch.
• The same (parent, slug) in two files of one batch is a duplicate, and both are flagged.

Additive only

Bulk import only creates and updates. It never deletes, and a trash status is rejected.

Pattern exporter

Use the exporter to download an existing record as a JSON template. Copy its shape, change the values, and you have a valid import file. This is the surest way to get fields names right.

Working with AI agents

The page includes a downloadable agent guide (plain text) that documents the exact rules an AI agent needs to produce valid files. The typical flow is to export a pattern record, hand it plus the guide to an agent, and let it produce import-ready JSON.

Next, see Preparing JSON files.