Exports

Nelkap keeps your runs for as long as your plan’s history: 1, 7, or 15 days. An export gives you a copy to keep, to analyze in a spreadsheet, or to load into your own database. Admins and the owner can request exports.

​

Request an export

Go to Exports and choose what to export: An export covers every project of the workspace, with everything Nelkap still keeps. Nelkap builds the archive in the background. Its status goes from pending to processing, then to ready. A workspace builds one export at a time: request the next one once the last is ready.

​

Download it

Once the export is ready, download it from the list. It’s a zip archive, available for 7 days.

​

Read the files

Each file starts with a row of column names, then one row per workflow, run, step, or event. The columns cover everything Nelkap keeps: IDs, names, statuses, payloads, results, errors, and dates. Rows link to each other by ID, like a step to its run, and a run to its workflow and its event.

• Dates are in UTC, in ISO 8601, like 2026-10-24T09:30:00.000Z.
• Payloads, results, scores, and tags are written as JSON.
• A value that a spreadsheet could take for a formula is escaped, so the files open safely in Excel or Google Sheets.

​

Keep a longer history

To keep your runs longer than your plan does, export them at least as often as your history lasts: every day with 1 day of history, every week with 7 days. A run still going when you export it shows with its status at that moment, and again in the next export. Each row keeps its ID from one export to the next, so merge them by ID.

​

When an export fails

An export that can’t be built shows as failed. Request it again.