PortForm
All use cases

Run a survey without a survey tool.

Every question is a named field; the whole thing posts as one submission. PortForm stores each response and hands you a CSV to analyse in whatever you already use.

Your form

Plain HTML on your site

PortForm

Stored · spam filtered · emailed

Your inbox

Every submission, with Reply-To set

Dashboard

Searchable, exportable to CSV

Integrations

Slack, Sheets, CRM, webhooks

The problem

Survey platforms lock your responses behind their dashboard and their pricing. For a handful of questions you want the raw answers, in a spreadsheet, that you own.

How PortForm solves it

Build the survey as ordinary form fields — short answers, long answers, multiple choice, even one-question-per-screen. It posts as a single submission, gets stored, and exports to a CSV or a Google Sheet you control.

A form you can copy

Point this at PortForm and it works.

Replace YOUR_ACCESS_KEY with the access key from your dashboard. Create one free. The endpoint and the honeypot are already wired in.

What you get

The features this use case leans on.

Any question type

Text, textarea, select, radio, checkbox — all standard inputs, all stored under the names you give them.

One submission per response

Every field posts together, so a response is one row, not scattered events.

Own your data

Pro

Export to CSV or sync to Google Sheets and analyse it anywhere — the responses are yours.

Multi-step if you want

One-question-per-screen still posts as a single submission — see the copyable template.

Route it onward

Integrations that fit this use case.

Google SheetsAirtableNotionWebhooks

Integrations are a Pro feature. On any plan, every submission still reaches your inbox and dashboard. See plans.

Why PortForm

Why it fits survey forms.

  • Raw responses in a spreadsheet you own, not a locked dashboard.
  • Any mix of question types, no builder to learn.
  • One submission per respondent, clean to analyse.

Run a survey without a survey tool.