NBForms

Submissions

Browse, read, filter, and export form submissions from your dashboard.

Every POST to your form endpoint creates a submission visible in the Submissions tab.

Tabs

The submissions view has three tabs:

TabContents
InboxNormal submissions
SpamSubmissions you have manually marked as spam
ExceededSubmissions blocked because the account has hit its quota limit

Reading submissions

Click any row to open the detail panel. The panel shows:

  • All submitted field values
  • Any attached files (with download links)
  • Submission metadata: IP address, referrer URL, user agent, timestamp

Unread submissions are highlighted in the list. Opening a submission marks it as read.

Spam

Mark a submission as spam from the detail panel. It moves to the Spam tab and no longer triggers notifications or integrations for future spam from the same source. You can unmark it at any time.

Exceeded submissions

If your account has consumed its free monthly quota and has no credit balance, incoming submissions are stored but marked as locked (exceeded). They appear in the Exceeded tab.

Buying credits unlocks the quota immediately — exceeded submissions become visible in Inbox automatically.

Exporting submissions

Use the Export CSV button (top-right of the Submissions card) to download all inbox submissions as a comma-separated file. Each row contains all field keys as columns plus the submission timestamp.

How submissions are processed

Submissions go through the following pipeline before appearing in the inbox:

  1. Token validation — the _token field must match a known, active form.
  2. CAPTCHA verification — if configured, the CAPTCHA token is verified server-side with Google or Cloudflare before the submission is accepted.
  3. Quota check — if the free monthly quota is exhausted and the credit balance is zero, the submission is stored as locked.
  4. File handling — uploaded files are saved to the server. Storage is deducted from the allocated storage quota.
  5. Worker delivery — a background worker picks up the submission and fans it out to configured integrations and notification emails.

The endpoint always responds promptly with 202 Accepted (or a redirect if configured) — delivery to integrations is asynchronous.

Special field names

Certain name attributes affect submission behaviour:

NameEffect
_tokenRequired. Identifies and authenticates the form.
_subjectOverrides the email notification subject line.
_redirectOverrides the redirect URL set in Settings (useful for per-page custom redirects).
g-recaptcha-responsereCAPTCHA v2 token — added automatically by the Google widget.
cf-turnstile-responseCloudflare Turnstile token — added automatically by the Turnstile widget.

All other field names are stored as-is and shown in the dashboard.

On this page