PortForm
All use cases

Take RSVPs without an events platform.

For a meetup, a webinar or a launch, you need names and emails and a way to reach them again. PortForm collects each RSVP, stores it, and can email the attendee a confirmation on the spot.

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

Event platforms are built for ticketing and priced for it. A free meetup just needs a signup form, a stored list, and a confirmation email — not a checkout.

How PortForm solves it

A registration form posts to PortForm. Each RSVP is stored and emailed to you, an autoresponder can send the attendee their confirmation and the details, and the full list exports to CSV for your check-in sheet.

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.

Collect what you need

Name, email, guest count, dietary notes, session choice — any field, stored and forwarded.

Confirmation email

Pro

The autoresponder emails each attendee their confirmation and the event details automatically.

Guest list export

Pro

Export every RSVP to CSV for your door list, or sync to a sheet the team shares.

Spam-free list

Honeypot and CAPTCHA keep bot registrations out of your headcount.

Route it onward

Integrations that fit this use case.

Google SheetsSlackNotionWebhooks

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

Why PortForm

Why it fits event registration.

  • A signup form, not a ticketing checkout.
  • Attendees get an instant confirmation email.
  • One CSV for the door on the day.

Other use cases

Take RSVPs without an events platform.

Start freeRead the docs