Help Center menu

Using CSV export programmatically

In this article

Until the REST API ships, CSV export is the best way to get response data out of NodumForms for downstream use.

Workflow

  1. Open the form → Responses → Export CSV.
  2. Pick which columns and whether to include metadata.
  3. Download the file.
  4. Pipe it into whatever you need — Pandas, dbt, BigQuery, etc.

File format

  • UTF-8 encoded.
  • First row is the question text.
  • One row per response.
  • Multi-select answers are comma-separated within the cell, quoted.
  • File-upload answers export as the public URL of the uploaded file.

Automating

CSV export is manual today — there's no scheduled or scripted export endpoint. As a workaround:

  • Email yourself a reminder to export weekly/monthly.
  • Use a browser-automation tool (Playwright, Puppeteer) to log in and trigger the export. Brittle but works.
  • Wait for the public API — it'll include a programmatic export endpoint.

Tips for analytics use

  • Include the Submitted at column so you can join with time-series data.
  • Include the Response ID column so you have a stable primary key across exports.
  • Re-exporting overwrites local files — keep a date-stamped copy if you want a snapshot trail.

Give feedback

Was this resource helpful?

|
Previous: Public API status

FAQs

Not yet — a public REST API is on the roadmap. Today the only outbound integration point is the webhook on each form, which fires on every submission with the full response payload. If you need read access to forms or responses programmatically before the API ships, email support@nodumforms.com.

No SDK yet — the planned TypeScript / Python / Go libraries are blocked on shipping the public REST API. Watch the roadmap for announcements.

Webhook signing isn't available yet — the request has no signature header. As a workaround, protect the endpoint by using a hard-to-guess URL path. Signing is on the roadmap.